You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the GTFS format is the only possibility of importing PT definitions, routes and timetables.
NeTEx is the official european standard to exchange public transport information, most eurpean pt authorities are also officially adopting this standard.
It defines the network, routes, lines and timetable in a single xml file.
NeTEx has a general european definition including xsd files: https://github.com/NeTEx-CEN/NeTEx
My suggestion would be a conversion script for netex2pt (which are quite close in format) with file input --netex and with an optional dialect flag --netex-dialect [NL|NORD|FR]which can deal with the dialect specific (XSD) parsing.
The text was updated successfully, but these errors were encountered:
Currently the GTFS format is the only possibility of importing PT definitions, routes and timetables.
NeTEx is the official european standard to exchange public transport information, most eurpean pt authorities are also officially adopting this standard.
It defines the network, routes, lines and timetable in a single xml file.
NeTEx has a general european definition including xsd files: https://github.com/NeTEx-CEN/NeTEx
And also country or region specific dialects of NeTex exist:
The Netherlands: https://github.com/BISONNL/NeTEx-NL
Nordics: https://github.com/entur/profile-examples/tree/master
My suggestion would be a conversion script for netex2pt (which are quite close in format) with file input
--netex
and with an optional dialect flag--netex-dialect [NL|NORD|FR]
which can deal with the dialect specific (XSD) parsing.The text was updated successfully, but these errors were encountered: