NeTEX: Difference between revisions

From DATA4PT WIKI
Jump to navigation Jump to search
← Older edit
VisualWikitext
Anasfou (talk | contribs)
Expert, MemberState, Bureaucrats, Page Ownership admin, Administrators
291 edits
 
(84 intermediate revisions by 5 users not shown)
Line 1: Line 1:
= NeTEx overview =
[[File:NeTEx.png|250px|right|link=http://netex-cen.eu/|alt=]]


'''NeTEx''' has been developed under the aegis of CEN (Comité Européen de Normalisation) and is the most recent development stage in over fifteen years work to systemise and harmonize European passenger information data.
= NeTEx overview 🔍 =
== What is NeTEx? ==


NeTEx provides a means to exchange data for passenger information such as stops, routes timetables and fares, among different computer systems, together with related operational data. It can be used to collect and integrate date from many different stakeholders, and to reintegrate it as it evolves through successive versions.
[[File:NeTEx.png|250px|right|]]


NeTEx is intended to be a general purpose XML format, designed for the efficient, updateable exchange of complex transport data among distributed systems. This allows the data to be used in modern web services architectures and to support a wide range of passenger information and operational applications.
NeTEx (Network Exchange format) is a standard for exchanging public transport network, schedules, and related data. It is a general-purpose XML format designed for the efficient exchange of complex transport data among distributed systems.


To find out more about the '''NeTEX data model''', visit the [http://netex-cen.eu/ NeTEX website].
It has been developed under the aegis of CEN (Comité Européen de Normalisation) and is the most recent development stage in over fifteen years work to systemise and harmonize European passenger information data.


=NeTEx-Light  =
NeTEx can be used to collect and integrate data from many different stakeholders, and to reintegrate it as it evolves through successive versions. It is used by public transport operators and IT providers across Europe to support a wide range of passenger information and operational applications.
[[File:NeTEx EPIP reduced XSD.png|right|thumb|link=https://data4pt.org/NeTEx/GraphicKit/Documention_of_reduced_XSD.html|Graphic and interactive technical presentation reduced XSD]]The normative NeTEx schema could be considered very big and extensive. Code generation tools for C# have difficulties with processing it. In order to use NeTEx within C# this derived XSD was created. This schema should be used informative, for application development, but not for validation purposes. This schema has been reduced to only match the scope of the EPIP Profile (European Passenger Information Profile) but remains compliant with the main NeTEx Schema.


The '''graphic interactive technical presentation''' and the technical artefacts are available [https://data4pt.org/NeTEx/GraphicKit/Documention_of_reduced_XSD.html here].
== Benefits of using NeTEx ==


=NeTEx EPIP =
NeTEx offers a number of benefits, including:
[[File:NeTEx EPIP XSD.png|right|thumb|link=https://data4pt.org/NeTEx/GraphicKit/Documention_of_XSD_for_EPIP.html|Graphic and interactive technical presentation]]
Ideally, all member states will provide NeTEx files according to the European Passenger Information Profile (EPIP) on their respective National Access Point. Data4PT provides some artefacts to '''simplify''' producing and quality assure such information.
EPIP-adapted version of the full NeTEx XML schema has been produced.
* Browse the '''graphic and interactive''' technical presentation and download the relevant artefacts and available example [https://data4pt.org/NeTEx/GraphicKit/Documention_of_XSD_for_EPIP.html here].


= National profiles =
* '''Flexibility''': NeTEx can be used to represent a wide range of public transport data, including networks, schedules, fares, and real-time information.
A number of National and international profiles have already been defined for different European countries and more are under development. In the following table, DATA4PT provides an overview of the key characteristics of the national profiles per country, including the data categories that are currently covered by each one of the profiles. The table will be continuously update following new implementations.
* '''Extensibility''': NeTEx can be extended to support new types of data and functionality.
* '''Interoperability''': NeTEx is a standard format, which means that data can be exchanged between different systems without the need for custom development.
* '''Support for modern web services architectures''' : NeTEx can be used to develop modern, web-based passenger information and operational applications.


''*Data categories are identified based on MMTIS EU Regulation 1926/2017''
== Examples of NeTEx in use ==


<nowiki>**</nowiki> European Passenger Information Profile
NeTEx is used in a variety of ways across the public transport industry. For example:


<nowiki>***</nowiki> European Passenger Information Accessibility Profile   
*'''Passenger information''': NeTEx can be used to provide real-time arrival and departure information to passengers, generate timetables and journey planners, and develop mobile apps for passengers.
*'''Operational applications''': NeTEx can be used to manage fleet operations, integrate public transport data with other systems, such as traffic management systems and navigation apps, and support planning and analysis.


{| class="wikitable sortable zebra" style="padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;border-spacing:0;text-align:center; "
 
|-
ℹ️ To find out more about the NeTEX data model, visit the [https://transmodel-cen.eu/ Transmodel website].
! colspan="2" style="text-align:center; min-width: 100px; max-width: 150px;" |PROFILES
 
! style="width: 80px;" |Full NeTEx format
= NeTEx European Passenger Information Profile 🇪🇺 =
! style="width: 80px;" |EPIP**
 
! style="width: 80px;" |EPIAP***
{| class="wikitable"
! style="width: 80px;" |Austria
! style="width: 80px;" |Croatia
! style="width: 80px;" |Czech Republic
! style="width: 80px;" |Denmark
! style="width: 80px;" |France
! style="width: 80px;" |Italy
! style="width: 80px;" | Netherlands
! style="width: 80px;" |Nordic <small><small>(Norway, Sweden, Finland, Denmark currently)</small></small>
! style="width: 80px;" |Portugal
! style="width: 80px;" |Slovenija
! style="width: 80px;" |Switzerland
! style="width: 80px;" |UK
! style="width: 80px;" |Irish
! style="width: 80px;" | German<br> VDV
|-
| colspan="2" |Availability of NeTEx national profile
!
!
!
! Description
!under development
! Documentation
|Specified but  not yet in operation
| not yet specified
|not yet specified
|not yet specified
|Specified and partially in operation
|Specified but not yet in operation
| specified but not yet in  operation
|Specified and in use
| Specified and in use
|specified but not yet in operation
|in progress
|Specified and in use
| specified
|
|-
|-
| colspan="2" |NeTEx EPIP based
|width="150px" style="text-align:center |'''NeTEx EPIP'''|| Ideally, all member states will provide NeTEx files according to the European Passenger Information Profile (EPIP) on their respective National Access Point. Data4PT provides some artefacts to simplify producing and quality assure such information. EPIP-adapted version of the full NeTEx XML schema has been produced.
!
Moreover, since the official NeTEx schema is too large and complex for C# code generation tools to handle, a simplified version was created for application development. This schema has been reduced to only match the scope of the EPIP Profile (European Passenger Information Profile). It is compliant with the main NeTEx schema, but does not contain constraint checks and should not be used for validation.
!
| The documentation is available at the NeTEx GitHub repository [https://github.com/NeTEx-CEN/NeTEx-Profile-EPIP here]
!
|}
|[[File:compliant.png|15px|link=]]
 
|
 
|
= Software & tools 🧰 =
|
 
|
An ecosystem of NeTEx XML tools is under development, including both open-source and commercial products.
|[[File:compliant.png|15px|link=]]
 
|
The following list of software is known to support NeTEx. We distinguish between different categories that may later receive a list of key performance indicators.
|
 
|
== XML tools ==
|
General purpose XML tools can be used to work with the NeTEx XML schema and XML documents that conform to it.
|
 
|[[File:compliant.png|15px|link=]]
{| class="wikitable" style="width : 10%"
|
|
|-
|-
| colspan="2" |NeTEx EPIP compatible
!  width="80px"|XML tools
!
! width="80px"|Description
!
!
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|
|
|-
|-
| colspan="2" |Available mappings with full NeTEx profile
|[http://www.altova.com/xmlspy.html XML SPY] || commercial
!
!
!
|
|
|
|
|
|
|
|
|
|
|
|
|
|[https://www.vdv.de/netex.aspx VDV NeTEx page]
|-
|-
| colspan="2" |Available mappings with EPIP profile
|[http://www.oxygenxml.com/ Oxygen]|| commercial
!
!
!
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
|-
! colspan="2" |Functional scope based on MMTIS EU Regulation  1926/2017
|[http://www.garshol.priv.no/download/xmltools/ List of tools] || open-source
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
|-
|-
| style="font-weight:bold; background-color:#efefef;" |LOS 1
{| class="wikitable"
| style="font-weight:bold; background-color:#efefef;" |Static data -  Level of service 1
 
!
== Conversion tools ==
!
 
!
{| class="wikitable" style="width:80%"
!
! colspan="1" | Name
!
! Availability
!
! width="40%" | |Description
!
! colspan="1" |Profile
!
!width="20%"| License
!
!
!
!
!
!
!
!
!
|-
|-
|LOS 1-1
| style="text-align:center |'''[https://github.com/entur/netex-protobuf netex-protobuf]''' ||style="text-align:center |✅ || NeTEx to protobuf converter || All ||EUPL
| Address identifiers (building  number, street name, postcode)
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|-
|-
|LOS 1-2
|style="text-align:center | '''[https://github.com/CanalTP/transit_model/tree/master/gtfs2netexfr gtfs2netexfr]''' || style="text-align:center |✅ ||Export GTFS data to NeTEx. ||French    ||  
|Topographic places (city, town,  village, suburb, administrative unit)
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|
|
|-
|-
|LOS 1-3
| style="text-align:center |'''[https://github.com/skinkie/hastus hastus]''' || style="text-align:center |✅ ||Giro Hastus OIG script to export NeTEx from a system, in addition can export crew operations. ||Dutch, Nordic(?) || AGPL-3.0
|Points of interest (related to transport information) to which  people may wish to travel
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|-
|-
|LOS 1-4
| style="text-align:center |'''[https://gitlab.com/labiangashi/josm-plugin-netex-converter/ josm-plugin-netex-converter]''' ||style="text-align:center |✅ || Export OpenStreetMap pedestrian routing information into NeTEx.||   || GPL 2.0 
|Operational Calendar, mapping  day types to calendar dates
|[[File:compliant.png|15px|link=]]
|
|
|[[File:compliant.png|15px|link=]]
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|
|
|-
|-
|LOS 1-5
| style="text-align:center |'''[https://github.com/entur/netex-gtfs-converter-java netex-gtfs-converter-java]''' ||style="text-align:center |✅ || Export NeTEx data to GTFS ||Nordic ||EUPL
|Identified access nodes (all  scheduled modes)
|[[File:compliant.png|15px|link=]]
|
|
|[[File:compliant.png|15px|link=]]
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|-
|-
|LOS 1-6
|style="text-align:center |'''[https://github.com/cefriel/chimera Chimera]''' ||style="text-align:center |✅ || Chimera is a framework for semantic data transformation pipelines. A converter between GTFS and NeTEx has been implemented adopting an intermediate Transmodel representation. ||Nordic (ready), EPIP/Italian (ongoing) || Framework – Apache License 2.0, Mapping GTFS-NeTEx – Proprietary license
|Geometry/map layout structure of  access nodes (all scheduled modes)
|[[File:compliant.png|15px|link=]]
|
|
|[[File:compliant.png|15px|link=]]
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|-
|-
|LOS 1-7
|style="text-align:center |'''[https://www.openmove.com/ OpenMove ATLAS]''' || style="text-align:center |✅ || The management platform OpenMove ATLAS allows import and editing of data in GTFS format and export also in GTFS or NeTEx format (currently the Italian Profile is supported, other profiles can be implemented on request). || EPIP Italian ||Proprietary license
|Connection links where  interchanges may be made, default transfer times between modes at  interchanges
|[[File:compliant.png|15px|link=]]
|
|
|[[File:compliant.png|15px|link=]]
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|
|
|-
|-
|LOS 1-8
|style="text-align:center |'''[https://developers.italia.it/it/software/a4c48ddf-7156-4327-a62b-66fc15f1c6f3 GTFS2NeTEx-converter]''' ||style="text-align:center |✅ || Converts GTFS data in NeTEx Italian Profile. || EPIP Italian Profile  ||EUPL 1.2
|Network topology and  routes/lines (topology)
|}
|[[File:compliant.png|15px|link=]]
 
|[[File:compliant.png|15px|link=]]
== Data validation tools ==
|
 
|[[File:compliant.png|15px|link=]]
{| class="wikitable" style="width:40%;"
|
! width="25%" | Name
|
!width="10%" | Availability
|
! width="40%"| Description
|[[File:compliant.png|15px|link=]]
!width="10%" | Profile
|[[File:compliant.png|15px|link=]]
!width="10%" | License
|[[File:compliant.png|15px|link=]]
|[[File:compliant.png|15px|link=]]
|[[File:compliant.png|15px|link=]]
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|
|
|-
|-
|LOS 1-9
| style="text-align:center |'''[http://www.xmlsoft.org/ XMLlint]''' || style="text-align:center |✅ ||XML syntax validation, XSD schema validation and constraint checking. ||All ||MIT 
|Transport operators
|[[File:compliant.png|15px|link=]]
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|
|
|
|[[File:compliant.png|15px|link=]]
|[[File:compliant.png|15px|link=]]
|[[File:compliant.png|15px|link=]]
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|
|
|-
|-
|LOS 1-10
|style="text-align:center | ''' The Data4PT Validation tool''' ||style="text-align:center |✅||The tool is under maintenance in the framework of [https://napcore.eu/ NAPCORE]. ||All ||
|Timetables
|[[File:compliant.png|15px|link=]]
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|
|
|
|[[File:compliant.png|15px|link=]]
|[[File:compliant.png|15px|link=]]
|[[File:compliant.png|15px|link=]]
|[[File:compliant.png|15px|link=]]
|[[File:compliant.png|15px|link=]]
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|
|
|-
|-
|LOS 1-11
| style="text-align:center |'''[https://github.com/entur/netex-validator-java NeTEx validator java]''' ||style="text-align:center |✅|| Validation library for NeTEx data, analyzing and reporting schema compliance. ||Nordic ||
|Planned interchanges between  guaranteed scheduled services
|[[File:compliant.png|15px|link=]]
|
|
|[[File:compliant.png|15px|link=]]
|
|
|
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|For connection links we use  journeyplanner based on OSM map data, road, cycle and pedestrian network is  based on OpenStreetMap
|
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|
|
|-
|-
|LOS 1-12
| style="text-align:center |'''[https://github.com/entur/antu Antu]''' ||style="text-align:center |✅|| Validate NeTEx datasets against the Nordic NeTEx Profile. ||Nordic ||
|Hours of operation
|}
|[[File:compliant.png|15px|link=]]
 
|
== Language bindings ==
|
{| class="wikitable" style="width: 45%;"
|[[File:compliant.png|15px|link=]]
! Name
|
! Availability
|
! Description
|
! Profile
|[[File:compliant.png|15px|link=]]
! License
|
|
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|-
|-
|LOS 1-13
| style="text-align:center |'''[https://github.com/entur/netex-java-model netex-java-model]''' || style="text-align:center |✅ ||NeTEx XML bindings for Java, with additions to map temporal types to native objects. ||All ||EUPL
|Vehicles (low floor; wheelchair  accessible.)
|[[File:compliant.png|15px|link=]]
|
|
|[[File:compliant.png|15px|link=]]
|
|
|
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|-
|-
|LOS 1-14
|style="text-align:center | '''netex-csharp-model''' ||style="text-align:center |❌ || NeTEx XML bindings for C#. Currently being researched with a variety of tools.<br>Contact DATA4PT if you have questions or have found the golden egg. ||All ||
|Accessibility of access nodes,  and paths within an interchange (such as existence of lifts, escalators)
|[[File:compliant.png|15px|link=]]
|
|
|[[File:compliant.png|15px|link=]]
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|-
|-
|LOS 1-15
|style="text-align:center | '''[https://github.com/entur/netex-parser-java netex-parser-java]''' ||style="text-align:center |✅||Parse NeTEx files and lookup entities in an index ||Nordic ||EUPL
|Existence of assistance services  (such as existence of on-site assistance)
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|-
|-
|LOS 1-16
|}
|Road network
 
|[[File:compliant.png|15px|link=]]
== Editing /Management & visualisation tools ==
|
 
|
{| class="wikitable" style="width: 75%;"
|
! Name
|
! Availability
|
! Description
|
! Profile
|[[File:compliant.png|15px|link=]]
! License
|
! URL
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|-
|-
|LOS 1-17
| style="text-align:center | '''Nplan''' ||style="text-align:center | ✅|| Java backend / TypeScript frontend for create/edit/export of NeTEx data (Support both Timetable based and On-demand polygon based services) ||Nordic ||EUPL ||backend - https://github.com/entur/uttu <br> frontend - https://github.com/entur/enki
|Cycle network (segregated cycle  lanes, on-road shared with vehicles, on-path shared with pedestrians)
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|-
|-
|LOS 1-18
|style="text-align:center |'''NSR''' ||style="text-align:center | ✅|| Java backend / JavaScript frontend for import/creation/edit/export for NeTEx stops data. (Act as a National Stops Register for the whole of Norway) || Nordic ||EUPL ||backend - https://github.com/entur/tiamat <br> frontend - https://github.com/entur/abzu
|Pedestrian network and  accessibility facilities
|[[File:compliant.png|15px|link=]]
|
|
|  
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|-
|-
|
| style="text-align:center |'''Chouette'''|| style="text-align:center |✅|| Java backend / Ruby frontend for import/validation/edit/export of NeTEx data. Highly modified version of the old AFIMB version of Chouette. NOTE: Legacy software not recommended for new implemetations ||Nordic ||CeCILL-B ||backend - https://github.com/entur/chouette <br> frontend -  https://github.com/entur/chouette2
|Framework data
|[[File:compliant.png|15px|link=]]
|
|
|
|
|  
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|-
|-
| style="font-weight:bold; background-color:#efefef;" |LOS 2
|style="text-align:center |'''[https://enroute.mobi/produits/chouette/ Chouette]''' ||style="text-align:center | ✅|| Java based NeTEx tools, transforms between profiles and standards (NeTEx, GTFS, Neptune). ||EPIP ||Apache 2.0 ||
! style="font-weight:bold; background-color:#efefef;" |Static data - Level of service  2
!
!
!
!in progress
!
!
!
!
!
!
!
!
!
!
!
!
!
|-
|-
|LOS 2-1
|style="text-align:center |'''[https://mobilitx.diginext.fr/ mobilitx]''' || style="text-align:center |✅|| || || ||
| Park & Ride stops
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|-
|-
|LOS 2-2
|style="text-align:center |'''[https://www.lumiplan.com/produit/mobiref/ mobiref]''' ||style="text-align:center | ✅ || || || ||
| Bike sharing stations
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|-
|-
|LOS 2-3
|style="text-align:center |'''NeTEx Reader''' ||style="text-align:center | ⏳ ||C# based XML tool based on Giro Hastus XSD || Dutch || ||https://www.youtube.com/watch?v=mpb_1Y9uR5k
|Car-sharing stations
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|-
|-
|LOS 2-4
|style="text-align:center |'''netexconv2''' || style="text-align:center |⏳ ||Java based NeTEx tools, transforms between profiles and standards (NeTEx, DINO, HAFAS, KV1, GTFS). || Dutch, EPIP, Nordic, VDV462 || ||
|Publicly accessible refuelling  stations for petrol, diesel, CNG/LNG, hydrogen powered vehicles, charging  stations for electric vehicles
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|
|
|
|Only charging stations for  electric vehicles
|
|[[File:compliant.png|15px|link=]]
|
|
|
|  
|-
|-
|LOS 2-5
|style="text-align:center | '''[https://www.ivu.com/news/news/article/delfi-successfully-migrates-to-ivucloud.html IVU.cloud]''' || style="text-align:center |✅|| ||EPIP || ||
|Secure bike parking (such as  locked bike garages)
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|
|
|  
|  
|-
|-
| LOS 2-6
|style="text-align:center |'''[https://www.pluservice.net/it/soluzioni/gestione-rete-e-turni Motus]''' ||style="text-align:center | ✅|| 4Motus is the Fleet Scheduling Management System provided by Pluservice. The application is designed by independent and integrated modules which can be activated according to specific operational needs. <br> One of the latest module created and already available is the generation of NeTEx datasets starting from the operational data collected by public transport operators. For this purpose, Motus receives the input data starting from a GTFS and it is able to enrich  these data with further relevant information such as contracts, vehicles. Then Motus transforms these data into the NeTEx Italian profile.<br> '''Data model:''' the database is designed according to Transmodel specifications, European reference standard (EN12896) for public  transport. ||Italian || ||
|Information service
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|
|
|
|  
|-
|-
|LOS 2-7
|}
| Where and how to buy tickets for  scheduled modes, demand responsive modes and car parking (all scheduled modes  and demand-responsive incl. retail channels, fulfilment methods, payment  methods)
 
|[[File:compliant.png|15px|link=]]
== Journey planning engine ==
|
 
|
{| class="wikitable" style="width: 60%;"
|
!  Name
|
! Availability
|
! Description
|
! Profile
|[[File:compliant.png|15px|link=]]
! License
|
|
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|-
|-
|LOS 2-8
| style="text-align:center | '''[http://docs.opentripplanner.org/en/dev-2.x/Netex-Norway/ OpenTripPlanner]''' || style="text-align:center |✅||Timetable and shortest path journey planner supporting reading various input formats including GTFS and NeTEx. || Nordic || Apache 2.0
|Trip plans, auxiliary  information, availability check
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|-
|-
|LOS 2-9
| style="text-align:center | '''[https://openmove.com/technology/trip-planning/ OpenMove]''' ||style="text-align:center | ✅ ||Multimodal, intermodal trip planner with real-time capabilities, step-by-step instructions, fare system, and compatibility with market standards. || ||
|Basic common standard fares (all  scheduled modes)
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|
|
|-
|-
|LOS 2-10
|}
|Fare network data (fare  zones/stops and fare stages)
 
|[[File:compliant.png|15px|link=]]
==Planning system supporting native NeTEx export ==
|
 
|
{| class="wikitable" style="width: 25%;"
|
!Name
|
!Availability
|
!Developped by
|
!Profile
|[[File:compliant.png|15px|link=]]
!Additional documentation
|
|
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|
|
|-
|LOS 2-11
|Standard fare structures (point  to point including daily and weekly fares, zonal fares, flat fares)
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|
|
|-
|LOS 2-12
|Vehicle facilities such as  classes of carriage, on-board Wi-Fi.
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|
|
|-
| style="font-weight:bold; background-color:#efefef;" | LOS 3
! style="font-weight:bold; background-color:#efefef;" |Static data - Level of service  3
!
!
!
!
!  
!
!
!
!
!
!
!
!
!
!
!
!
|-
|LOS 3-1
|Passenger classes (classes of  user such as adult, child, student, veteran, impaired access and qualifying  conditions and classes of travel such as 1st, 2nd.)
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|[[File:compliant.png|15px|link=]]
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|-
|LOS 3-2
| Common fare products (access  rights such as zone/point-to-point including daily and weekly  tickets/single/return, eligibility of access, basic usage conditions such as  validity period/operator/time of travel/interchanging, standard point to  point fares prices for different point to point pairs including daily and  weekly fares/zonal fare prices/flat fare prices)
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|[[File:compliant.png|15px|link=]]
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|-
|LOS 3-3
| Special Fare Products: offers  with additional special conditions such as promotional fares, group fares,  season passes, aggregated products combining different products and add on  products such as parking and travel, minimum stay
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|[[File:compliant.png|15px|link=]]
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|-
|-
|LOS 3-4
|style="text-align:center | [https://www.giro.ca/en-ca/our-solutions/segments/public-transport/ Hastus] || style="text-align:center |✅ || Giro || Nordic <br> Dutch || Dutch patch: https://github.com/skinkie/hastus
|Basic commercial conditions such  as refunding/replacing/exchanging/transferring and basic booking conditions  such as purchase windows, validity periods, routing restrictions zonal  sequence fares, minimum stay.
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|-
|-
|LOS 3-5
|style="text-align:center | [https://www.trapezegroup.com.au/solutions/intelligent-transport-systems-bus Intelligent Transport Systems (ITS) for Bus]  || style="text-align:center |✅|| Trapeze  ||EPIP Nordic  || Blog post: https://www.trapezegroup.com.au/blog/its-netex-bus-data-transfer-exchange
|How to pay tolls (incl. retail  channels, fulfilment methods, payment methods)
|[[File:compliant.png|15px|link=]]
|
|
|  
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|
|
|
|-
|-
|LOS 3-6
| style="text-align:center | [https://www.datagrafikk.no/?tag=dgbuss  DG Buss] || style="text-align:center |✅ || Datagrafikk  || Nordic ||  
| How to book car sharing, taxis,  cycle hire etc. (incl. retail channels, fulfilment methods, payment methods)
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|
|
|
|
|  
|
|
|
|
|
|-
|-
|LOS 3-7
| style="text-align:center | [https://www.trapezegroup.com.au/solutions/planning-and-scheduling-rail  Planning & Scheduling for Train]  ||style="text-align:center |✅ || Trapeze ||Nordic ||
|Where how to pay for car  parking, public charging stations for electric vehicles and refuelling points  for CNG/LNG, hydrogen, petrol and diesel powered vehicles (incl. retail  channels, fulfilment methods, payment methods)
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|
|
|
|-
|-
|LOS 3-8
| style="text-align:center | [https://www.ivu.com/solutions#c4826  IVU.suite] || style="text-align:center |⏳ || IVU for public transport ||Nordic ||Blog post: https://www.ivu.com/all-references/references/delfi-migrates-to-ivucloud
| Detailed cycle network  attributes (surface quality, side-by-side cycling, shared surface, on/off  road, scenic route, ‘walk only’, turn or access restrictions (e.g. against  flow of traffic)
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|-
|-
|LOS 3-9
| style="text-align:center | [https://turnit.com/ Turnit Ride] ||style="text-align:center |✅ ||Turnit for public transport ||Nordic ||
|Parameters needed to calculate  an environmental factor such as carbon per vehicle type or passenger mile or  per distance walked
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|-
|-
|LOS 3-10
|style="text-align:center | Nplan ||style="text-align:center |✅ ||Entur for public transport ||Nordic || backend: https://github.com/entur/uttu  <br> frontend: https://github.com/entur/enki
|Parameters such as fuel  consumption needed to calculate cost
|[[File:compliant.png|15px|link=]]
|
|
|
|  
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|-
|-
|LOS 3-11
| style="text-align:center | [https://www.hacon.de/en/portfolio/timetable-construction-disposition/  TPs Suite] ||style="text-align:center | ✅ ||Hacon ||Nordic ||
|Estimated travel times by day  type and time-band by transport mode/combination of transport modes
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|}
|}


= NeTEx part 5 for 🆕 modes =


If you believe that your use cases are resolved in an existing profile, it is highly recommended to adopt an existing solution and cooperate with the corresponding entity. You will save resources while you will ensure that your profile is interoperable. It follows a list with links to the relevant documentation for each one the available profiles <ref>https://github.com/nick-knowles/NeTEx/wiki/NationalProfiles</ref>, where you can also find contact details for some of the entities responsible for the profiles. Otherwise you can contact us in [https://data4pt-project.eu/requests-requirements/ DATA4PT].  
NeTEx Part 5 is an extension to the NeTEx data exchange format that is specifically designed for publishing data about "alternative modes" of transportation, such as car sharing, cycle sharing, carpooling, and car/cycle rental. It is primarily oriented towards static data, such as the service that is offered and the associated infrastructure.


*ch : [https://transportdatamanagement.ch/en/standards/ Swiss profile - Work In progress.]
''NeTEx Part 5 is now available as '''CEN/TS 16614-5:2022 (E)'''''
**[https://transportdatamanagement.ch/content/uploads/2020/11/NeTEx_Core-Realisation_Guide_TP_Suisse-v0.8.8.4.pdf Realisation directive]
[[File:NeTEx-part5.png|400px|right|]]
*de : [https://www.vdv.de/oepnv-datenmodell.en.aspx German Profile].
**[https://www.vdv.de/vdv-462-netex-recommendation-v00-22-english.pdfx VDV462].
*dk : Denmark implements [https://enturas.atlassian.net/wiki/spaces/PUBLIC/pages/728891481/Nordic+NeTEx+Profile Nordic Profile] and the EU profiles.
*eu : Europe - Passenger Information Profile (Timetables) ([[NeTEX#NeTEx-Light and NeTEx EPIP|above]]). There is work in progress on European Accessibility Profile (EPIAP) lead by DATA4PT project. To be delivered in the 1st quarter of 2022.
*fi : Finland - [https://enturas.atlassian.net/wiki/spaces/PUBLIC/pages/728891481/Nordic+NeTEx+Profile Nordic Profile] .
*fr : [http://www.normes-donnees-tc.org/format-dechange/donnees-theoriques/netex/ French Profile].
**[http://www.normes-donnees-tc.org/wp-content/uploads/2021/01/Profil-NeTEx-elements-communsF-v2.2.pdf Common Profile specification].
**[http://www.normes-donnees-tc.org/wp-content/uploads/2014/05/NF_Profil_NeTEx_pour_les_arrets-_F-_-_v2.pdf Stop Profile specification].
**[http://www.normes-donnees-tc.org/wp-content/uploads/2019/11/NF_Profil-NeTEx-pour-les-R%C3%A9seauxF-v2.1.pdf Network Profile specification].
**[http://www.normes-donnees-tc.org/wp-content/uploads/2019/11/NF_Profil-NeTEx-pour-les-HorairesF-v2.1.pdf Timetable Profile specification].
**[http://www.normes-donnees-tc.org/wp-content/uploads/2021/11/NF_Profil-NeTEx-pour-les-TarifsF-v1.2.pdf Fare Profile].
**[http://www.normes-donnees-tc.org/wp-content/uploads/2021/10/NF_Profil-NeTEx-pour-les-ParkingsF-v1.2a.pdf Parking Profile].
**[http://www.normes-donnees-tc.org/wp-content/uploads/2021/01/Profil-NeTEx-pour-laccessibiliteF-v2.2.pdf Accessibility Profile].
*ie : [http://netex.ie/ Irish Profile].
**[http://netex.uk/netexie/doc/EIRE_NP/NTA-NeTEx-1-Spec-2020.08.12-v0.22.pdf Profile Elements].
**[http://netex.uk/netexie/doc/EIRE_NP/NTA-NeTEx-2-Mappings-2020.08.06-v0.22.pdf Profile Data Mappings]
*it  : [http://netex-cen.eu/?page_id=237 Italian Profile]
*nl : [https://bison.dova.nu/standaarden/nederlands-netex-profiel Netherlands profile].
**Profile specification.
**[https://bison.dova.nu/sites/default/files/bison_prijzen_producten_en_tarieven_v8.1.3.0_release.pdf Bison Fares].
*no : [https://enturas.atlassian.net/wiki/spaces/PUBLIC/pages/728891481/Nordic+NeTEx+Profile Norway - Nordic Profile].
* pt  : [https://ptprofiles.azurewebsites.net/netex-profile Portuguese Profile]
*se : [https://enturas.atlassian.net/wiki/spaces/PUBLIC/pages/728891481/Nordic+NeTEx+Profile Sweden - Nordic Profile].
*si  : [https://www.nap.si/_resources/profiles/NeTEx_SI_Profile_v2.pdf Slovenian Profile]
*uk : [http://netex.uk/farexchange/ UK Profile (FareExchange].
**[http://netex.uk/farexchange/doc/uk_profile/DfT-NeTEx-1-Fares-Intro-2019.06.17-v0.09.pdf Introduction].
**[http://netex.uk/farexchange/doc/uk_profile/DfT-NeTEx-2-Base_Spec-2019.06.30-v0.14.pdf Stops and Timetables].
**[http://netex.uk/farexchange/doc/uk_profile/DfT-NeTEx-3-Fares_Spec-2019.06.17-v0.17.pdf Fares].
 
=NeTEx software / tools=
General purpose XML tools can be used to work with the NeTEx XML schema and XML documents that conform to it, for example either the proprietary [http://www.altova.com/xmlspy.html XML SPY] , or [http://www.oxygenxml.com/ Oxygen] or see free tools at http://www.garshol.priv.no/download/xmltools/. A wide variety of mainstream XML tools are available to validate XML and to create bindings to specific programming languages (.NET, Java, PHP, C++).<ref>http://netex-cen.eu/?page_id=258</ref>
 
To look at the design models, an interactive UML viewer such as [http://www.sparxsystems.com/ Enterprise Architect] is extremely helpful, although a set of static web pages is also available. Sample mappings to a variety of national formats (VDV, BISON, etc) as well as GTFS have been developed and are included in the NeTEx standard.<ref>http://netex-cen.eu/?page_id=258</ref>
 
The following list of software is known to support NeTEx. We distinguish between different categories that may later receive a list of key performance indicators.


==Conversion of NeTEx between other formats==
{| class="wikitable" style="width: 50%;"
{| class="wikitable"
! colspan="1" | Name
! colspan="1" |Availability
! colspan="1" |Description
! colspan="1" |Profile
! colspan="1" |License
! colspan="1" |URL
|-
|-
! rowspan="1" style="text-align:left;" |[[netex-protobuf]]
!
|Available
!Description
|NeTEx to protobuf converter
|all
|EUPL
|https://github.com/entur/netex-protobuf
|-
! rowspan="1" style="text-align:left;" |[[gtfs2netexfr]]
|Available
| Export GTFS data to NeTEx.
|French
|
|https://github.com/CanalTP/transit_model/tree/master/gtfs2netexfr
|-
! rowspan="1" style="text-align:left;" |[[hastus]]
|Available
|Giro Hastus OIG script to export NeTEx from a system, in addition can export crew operations.
|Dutch, Nordic(?)
|AGPL-3.0
|https://github.com/skinkie/hastus
|-
! rowspan="1" style="text-align:left;" |[[josm-plugin-netex-converter]]
|Available
|Export OpenStreetMap pedestrian routing information into NeTEx.
|
| GPL 2.0
|https://gitlab.com/labiangashi/josm-plugin-netex-converter/
|-
|}
 
==Data Validation tools==
{| class="wikitable"
! colspan="1" |Name
! colspan="1" |Availability
! colspan="1" | Description
! colspan="1" |Profile
! colspan="1" |License
! colspan="1" |URL
|-
! rowspan="1" style="text-align:left;" |[[XMLlint]]
|Available
|XML syntax validation, XSD schema validation and constraint checking.
|All
|MIT
|http://www.xmlsoft.org/
|-
|}
 
==Language bindings and software development aids==
{| class="wikitable"
! colspan="6" |NeTEx XML bindings
|-
|-
! colspan="1" |Name
| '''[https://github.com/NeTEx-CEN/NeTEx/tree/master/xsd/netex_part_5 Technical artefacts]''' || The XML schema (XSD) for NeTEx Part 5 New Modes. Examples are also provided, along with other useful documentation.
! colspan="1" |Availability
! colspan="1" |Description
! colspan="1" | Profile
! colspan="1" |License
! colspan="1" |URL
|-
|-
! rowspan="1" style="text-align:left;" |[[netex-java-model]]
| '''[https://data4pt.org/w/images/5/5b/Canonical_mapping_-_NeTEx_and_SIRI_new_modes_with_GBFS.pdf Canonical mapping with GBFS]'''
| Available
| The EU-funded project DATA4PT and MobilityData experts have released a high-level mapping between the General Bikeshare Feed Specification (GBFS) and Transmodel to support better interoperability of shared mobility data feeds.
|NeTEx XML bindings for Java, with additions to map temporal types to native objects.
|Any
|EUPL
|https://github.com/entur/netex-java-model
|-
! rowspan="1" style="text-align:left;" |[[netex-csharp-model]]
|Not Available
|NeTEx XML bindings for C#. Currently being researched with a variety of tools.<br>Contact DATA4PT if you have questions or have found the golden egg.
|Any
|
|
|-
|-
|}
|}


==Editing /Management  & visualisation tools for  NeTEx data==
= References =
{| class="wikitable"
! colspan="1" |Name
! colspan="1" |Availability
! colspan="1" |Description
! colspan="1" |Profile
! colspan="1" |License
! colspan="1" | URL
|-
! rowspan="1" style="text-align:left;" |[[Chouette|Nplan]]
|Available
|Java backend / TypeScript frontend for create/edit/export of NeTEx data (Support both Timetable based and On-demand polygon based services)
|Nordic
|EUPL
|backend - https://github.com/entur/uttu
frontend - https://github.com/entur/enki
|-
! rowspan="1" style="text-align:left;" |[[NSR]]
| Available
|Java backend / JavaScript frontend for import/creation/edit/export for NeTEx stops data. (Act as a National Stops Register for the whole of Norway)
|Nordic
|EUPL
|backend - https://github.com/entur/tiamat
frontend - https://github.com/entur/abzu
|-
! rowspan="1" style="text-align:left;" |[[Chouette]]
|Available
|Java backend / Ruby frontend for import/validation/edit/export of NeTEx data. Highly modified version of the old AFIMB version of Chouette. NOTE: Legacy software not recommended for new implemetations
|Nordic
|CeCILL-B
|backend - https://github.com/entur/chouette
frontend -  https://github.com/entur/chouette2
|-
! rowspan="1" style="text-align:left;" |[[Chouette]]
|Available
|Java based NeTEx tools, transforms between profiles and standards (NeTEx, GTFS, Neptune).
|EPIP
|Apache 2.0
|https://enroute.mobi/produits/chouette/
|-
! rowspan="1" style="text-align:left;" |[[mobilitx]]
| Available
|
|
|
|https://mobilitx.diginext.fr/
|-
! rowspan="1" style="text-align:left;" |[[mobiref]]
|Available
|
|
|
|https://www.lumiplan.com/produit/mobiref/
|-
! rowspan="1" style="text-align:left;" |[[NeTEx Reader]]
| In Development
|C# based XML tool, based on Giro Hastus XSD.
|Dutch
|
|https://www.youtube.com/watch?v=mpb_1Y9uR5k
|-
! rowspan="1" style="text-align:left;" |[[netexconv2]]
|In Development
|Java based NeTEx tools, transforms between profiles and standards (NeTEx, DINO, HAFAS, KV1, GTFS).
|Dutch, EPIP, Nordic, VDV462
|
|
|-
! rowspan="1" style="text-align:left;" |[[IVU.cloud]]
|Available
|
|EPIP
|
|https://www.ivu.com/news/news/article/delfi-successfully-migrates-to-ivucloud.html
|-
|'''Motus'''
|Available
|Motus is the Fleet Scheduling Management System provided by Pluservice. The application is designed by independent and integrated modules which can be activated according to specific operational needs.
 
One of the latest module created and already available is the generation of NeTEx datasets starting from the operational data collected by public transport operators. For this purpose, Motus receives the input data starting from a GTFS and it is able to enrich  these data with further relevant information such as contracts, vehicles. Then Motus transforms these data into the NeTEx Italian profile.
 
'''Data model:''' the database is designed according to Transmodel specifications, European reference standard (EN12896) for public  transport.
|Italian
|
|https://www.pluservice.net/it/soluzioni/gestione-rete-e-turni
|-
|}


==NeTEx data enabled==
{| class="wikitable" style="width: 35%;"
{| class="wikitable"
! colspan="1" |Name
! colspan="1" |Availability
! colspan="1" | Description
! colspan="1" |Profile
! colspan="1" |License
! colspan="1" |URL
|-
|-
! rowspan="1" style="text-align:left;" |[[OpenTripPlanner]]
| Available
|Timetable and shortest path journey planner supporting reading various input formats including GTFS and NeTEx.
| Nordic
| Apache 2.0
|http://docs.opentripplanner.org/en/dev-2.x/Netex-Norway/
|-
|}
==Planning system supporting native NeTEx export ==
{| class="wikitable"
!Name
!Name
!Availability
!Description
!Description
!Profile
|-
! rowspan="1" style="text-align:left;" |[[Hastus]]
|Available
|Planning system from Giro for public transport
| Nordic
|-
! rowspan="1" style="text-align:left;" |[[Trapeze Cloud TP10|Trapeze]]
|Available
|Planning system from Trapeze for public transport
|Nordic
|-
|-
! rowspan="1" style="text-align:left;" |[[DG Buss]]
| '''[https://github.com/NeTEx-CEN/NeTEx NeTEx-CEN GitHub]'''
|Available
| Find xsd, examples and relevant documentation on NeTEx schema
|Planning system from Datagrafikk for public transport
|Nordic
|-
|-
! rowspan="1" style="text-align:left;" |[[Train Plan]]
| '''[https://github.com/NeTEx-CEN/NeTEx-Profile-EPIP NeTEx EPIP profile GitHub]'''
|Available
| Find xsd and relevant documentation dedicated on NeTEx EPIP schema
|Planning system from Trapeze for railway
|Nordic
|-
|-
! rowspan="1" style="text-align:left;" |[[IVU]]
| '''[https://netex-cen.eu/ NeTEx Website]'''
|In development
| Find general information on NeTEx project
|Planning system from IVU for public transport
|Nordic
|-
|-
! rowspan="1" style="text-align:left;" |[[IVU]]
|In development
|Planning system from IVU for railway
|Nordic
|-
! rowspan="1" style="text-align:left;" |[[Turnit]]
|Available
|Planning system from Turnit for public transport
|Nordic
|-
! rowspan="1" style="text-align:left;" |[[Nplan]]
|Available
|Planning system from Entur for public transport
|Nordic
|-
! rowspan="1" style="text-align:left;" |[[TPSI]]
|Available
|Planning system from HaCon for railway
|Nordic
|}
|}
<references />

Latest revision as of 15:19, 23 March 2026

NeTEx overview 🔍

What is NeTEx?

NeTEx (Network Exchange format) is a standard for exchanging public transport network, schedules, and related data. It is a general-purpose XML format designed for the efficient exchange of complex transport data among distributed systems.

It has been developed under the aegis of CEN (Comité Européen de Normalisation) and is the most recent development stage in over fifteen years work to systemise and harmonize European passenger information data.

NeTEx can be used to collect and integrate data from many different stakeholders, and to reintegrate it as it evolves through successive versions. It is used by public transport operators and IT providers across Europe to support a wide range of passenger information and operational applications.

Benefits of using NeTEx

NeTEx offers a number of benefits, including:

  • Flexibility: NeTEx can be used to represent a wide range of public transport data, including networks, schedules, fares, and real-time information.
  • Extensibility: NeTEx can be extended to support new types of data and functionality.
  • Interoperability: NeTEx is a standard format, which means that data can be exchanged between different systems without the need for custom development.
  • Support for modern web services architectures : NeTEx can be used to develop modern, web-based passenger information and operational applications.

Examples of NeTEx in use

NeTEx is used in a variety of ways across the public transport industry. For example:

  • Passenger information: NeTEx can be used to provide real-time arrival and departure information to passengers, generate timetables and journey planners, and develop mobile apps for passengers.
  • Operational applications: NeTEx can be used to manage fleet operations, integrate public transport data with other systems, such as traffic management systems and navigation apps, and support planning and analysis.


ℹ️ To find out more about the NeTEX data model, visit the Transmodel website.

NeTEx European Passenger Information Profile 🇪🇺

Description Documentation
NeTEx EPIP Ideally, all member states will provide NeTEx files according to the European Passenger Information Profile (EPIP) on their respective National Access Point. Data4PT provides some artefacts to simplify producing and quality assure such information. EPIP-adapted version of the full NeTEx XML schema has been produced.

Moreover, since the official NeTEx schema is too large and complex for C# code generation tools to handle, a simplified version was created for application development. This schema has been reduced to only match the scope of the EPIP Profile (European Passenger Information Profile). It is compliant with the main NeTEx schema, but does not contain constraint checks and should not be used for validation.

The documentation is available at the NeTEx GitHub repository here


Software & tools 🧰

An ecosystem of NeTEx XML tools is under development, including both open-source and commercial products.

The following list of software is known to support NeTEx. We distinguish between different categories that may later receive a list of key performance indicators.

XML tools

General purpose XML tools can be used to work with the NeTEx XML schema and XML documents that conform to it.

XML tools Description
XML SPY commercial
Oxygen commercial
List of tools open-source

Conversion tools

Name Availability |Description Profile License
netex-protobuf ✅ NeTEx to protobuf converter All EUPL
gtfs2netexfr ✅ Export GTFS data to NeTEx. French
hastus ✅ Giro Hastus OIG script to export NeTEx from a system, in addition can export crew operations. Dutch, Nordic(?) AGPL-3.0
josm-plugin-netex-converter ✅ Export OpenStreetMap pedestrian routing information into NeTEx. GPL 2.0
netex-gtfs-converter-java ✅ Export NeTEx data to GTFS Nordic EUPL
Chimera ✅ Chimera is a framework for semantic data transformation pipelines. A converter between GTFS and NeTEx has been implemented adopting an intermediate Transmodel representation. Nordic (ready), EPIP/Italian (ongoing) Framework – Apache License 2.0, Mapping GTFS-NeTEx – Proprietary license
OpenMove ATLAS ✅ The management platform OpenMove ATLAS allows import and editing of data in GTFS format and export also in GTFS or NeTEx format (currently the Italian Profile is supported, other profiles can be implemented on request). EPIP Italian Proprietary license
GTFS2NeTEx-converter ✅ Converts GTFS data in NeTEx Italian Profile. EPIP Italian Profile EUPL 1.2

Data validation tools

Name Availability Description Profile License
XMLlint ✅ XML syntax validation, XSD schema validation and constraint checking. All MIT
The Data4PT Validation tool ✅ The tool is under maintenance in the framework of NAPCORE. All
NeTEx validator java ✅ Validation library for NeTEx data, analyzing and reporting schema compliance. Nordic
Antu ✅ Validate NeTEx datasets against the Nordic NeTEx Profile. Nordic

Language bindings

Name Availability Description Profile License
netex-java-model ✅ NeTEx XML bindings for Java, with additions to map temporal types to native objects. All EUPL
netex-csharp-model ❌ NeTEx XML bindings for C#. Currently being researched with a variety of tools.
Contact DATA4PT if you have questions or have found the golden egg.		 All
netex-parser-java ✅ Parse NeTEx files and lookup entities in an index Nordic EUPL

Editing /Management & visualisation tools

Name Availability Description Profile License URL
Nplan ✅ Java backend / TypeScript frontend for create/edit/export of NeTEx data (Support both Timetable based and On-demand polygon based services) Nordic EUPL backend - https://github.com/entur/uttu
frontend - https://github.com/entur/enki
NSR ✅ Java backend / JavaScript frontend for import/creation/edit/export for NeTEx stops data. (Act as a National Stops Register for the whole of Norway) Nordic EUPL backend - https://github.com/entur/tiamat
frontend - https://github.com/entur/abzu
Chouette ✅ Java backend / Ruby frontend for import/validation/edit/export of NeTEx data. Highly modified version of the old AFIMB version of Chouette. NOTE: Legacy software not recommended for new implemetations Nordic CeCILL-B backend - https://github.com/entur/chouette
frontend - https://github.com/entur/chouette2
Chouette ✅ Java based NeTEx tools, transforms between profiles and standards (NeTEx, GTFS, Neptune). EPIP Apache 2.0
mobilitx ✅
mobiref ✅
NeTEx Reader ⏳ C# based XML tool based on Giro Hastus XSD Dutch https://www.youtube.com/watch?v=mpb_1Y9uR5k
netexconv2 ⏳ Java based NeTEx tools, transforms between profiles and standards (NeTEx, DINO, HAFAS, KV1, GTFS). Dutch, EPIP, Nordic, VDV462
IVU.cloud ✅ EPIP
Motus ✅ 4Motus is the Fleet Scheduling Management System provided by Pluservice. The application is designed by independent and integrated modules which can be activated according to specific operational needs.
One of the latest module created and already available is the generation of NeTEx datasets starting from the operational data collected by public transport operators. For this purpose, Motus receives the input data starting from a GTFS and it is able to enrich these data with further relevant information such as contracts, vehicles. Then Motus transforms these data into the NeTEx Italian profile.
Data model: the database is designed according to Transmodel specifications, European reference standard (EN12896) for public transport.		 Italian

Journey planning engine

Name Availability Description Profile License
OpenTripPlanner ✅ Timetable and shortest path journey planner supporting reading various input formats including GTFS and NeTEx. Nordic Apache 2.0
OpenMove ✅ Multimodal, intermodal trip planner with real-time capabilities, step-by-step instructions, fare system, and compatibility with market standards.

Planning system supporting native NeTEx export

Name Availability Developped by Profile Additional documentation
Hastus ✅ Giro Nordic
Dutch		 Dutch patch: https://github.com/skinkie/hastus
Intelligent Transport Systems (ITS) for Bus ✅ Trapeze EPIP Nordic Blog post: https://www.trapezegroup.com.au/blog/its-netex-bus-data-transfer-exchange
DG Buss ✅ Datagrafikk Nordic
Planning & Scheduling for Train ✅ Trapeze Nordic
IVU.suite ⏳ IVU for public transport Nordic Blog post: https://www.ivu.com/all-references/references/delfi-migrates-to-ivucloud
Turnit Ride ✅ Turnit for public transport Nordic
Nplan ✅ Entur for public transport Nordic backend: https://github.com/entur/uttu
frontend: https://github.com/entur/enki
TPs Suite ✅ Hacon Nordic

NeTEx part 5 for 🆕 modes

NeTEx Part 5 is an extension to the NeTEx data exchange format that is specifically designed for publishing data about "alternative modes" of transportation, such as car sharing, cycle sharing, carpooling, and car/cycle rental. It is primarily oriented towards static data, such as the service that is offered and the associated infrastructure.

NeTEx Part 5 is now available as CEN/TS 16614-5:2022 (E)

Description
Technical artefacts The XML schema (XSD) for NeTEx Part 5 New Modes. Examples are also provided, along with other useful documentation.
Canonical mapping with GBFS The EU-funded project DATA4PT and MobilityData experts have released a high-level mapping between the General Bikeshare Feed Specification (GBFS) and Transmodel to support better interoperability of shared mobility data feeds.

References

Name Description
NeTEx-CEN GitHub Find xsd, examples and relevant documentation on NeTEx schema
NeTEx EPIP profile GitHub Find xsd and relevant documentation dedicated on NeTEx EPIP schema
NeTEx Website Find general information on NeTEx project
Retrieved from "https://data4pt.org/w/index.php?title=NeTEX&oldid=728"