DATA4PT WIKI - User contributions [en]

NeTEX

2025-08-11T12:06:29Z

Admin: /* Data validation tools */

= NeTEx overview 🔍 =
== What is NeTEx? ==

[[File:NeTEx.png|250px|right|]]

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 [https://netex-cen.eu/ NeTEX website].

⚙️ To verify your NeTEx data, use our '''[https://greenlight.atomite.io free validation tool]'''.

= NeTEx European Passenger Information Profile 🇪🇺 =

{| class="wikitable"
!
! Description
! Documentation
|-
|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. || 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].
|-
|width="150px" style="text-align:center |'''NeTEx EPIP Light''' || The official NeTEx schema is too large and complex for C# code generation tools to handle, so 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 '''graphic interactive technical presentation''' and the technical artefacts are available [https://data4pt.org/NeTEx/GraphicKit/Documention_of_reduced_XSD.html 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.

{| class="wikitable" style="width : 10%"
|-
! width="80px"|XML tools
! width="80px"|Description
|-
|[http://www.altova.com/xmlspy.html XML SPY] || commercial
|-
|[http://www.oxygenxml.com/ Oxygen]|| commercial
|-
|[http://www.garshol.priv.no/download/xmltools/ List of tools] || open-source
|-
{| class="wikitable"

== Conversion tools ==

{| class="wikitable" style="width:80%"
! colspan="1" | Name
! Availability
! width="40%" | |Description
! colspan="1" |Profile
!width="20%"| License
|-
| style="text-align:center |'''[https://github.com/entur/netex-protobuf netex-protobuf]''' ||style="text-align:center |✅ || NeTEx to protobuf converter || All ||EUPL
|-
|style="text-align:center | '''[https://github.com/CanalTP/transit_model/tree/master/gtfs2netexfr gtfs2netexfr]''' || style="text-align:center |✅ ||Export GTFS data to NeTEx. ||French ||
|-
| 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
|-
| 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
|-
| 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
|-
|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
|-
|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
|-
|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
|}

== Data validation tools ==

{| class="wikitable" style="width:40%;"
! width="25%" | Name
!width="10%" | Availability
! width="40%"| Description
!width="10%" | Profile
!width="10%" | License
|-
| style="text-align:center |'''[http://www.xmlsoft.org/ XMLlint]''' || style="text-align:center |✅ ||XML syntax validation, XSD schema validation and constraint checking. ||All ||MIT
|-
|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 ||
|-
| 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 ||
|-
| style="text-align:center |'''[https://github.com/entur/antu Antu]''' ||style="text-align:center |✅|| Validate NeTEx datasets against the Nordic NeTEx Profile. ||Nordic ||
|}

== Language bindings ==
{| class="wikitable" style="width: 45%;"
! Name
! Availability
! Description
! Profile
! License
|-
| 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
|-
|style="text-align:center | '''netex-csharp-model''' ||style="text-align:center |❌ || 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 ||
|-
|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
|-
|}

== Editing /Management & visualisation tools ==

{| class="wikitable" style="width: 75%;"
! Name
! Availability
! Description
! Profile
! License
! URL
|-
| 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 frontend - https://github.com/entur/enki
|-
|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 frontend - https://github.com/entur/abzu
|-
| 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 frontend - https://github.com/entur/chouette2
|-
|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="text-align:center |'''[https://mobilitx.diginext.fr/ mobilitx]''' || style="text-align:center |✅|| || || ||
|-
|style="text-align:center |'''[https://www.lumiplan.com/produit/mobiref/ mobiref]''' ||style="text-align:center | ✅ || || || ||
|-
|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
|-
|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 || ||
|-
|style="text-align:center | '''[https://www.ivu.com/news/news/article/delfi-successfully-migrates-to-ivucloud.html IVU.cloud]''' || style="text-align:center |✅|| ||EPIP || ||
|-
|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. 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 ==

{| class="wikitable" style="width: 60%;"
! Name
! Availability
! Description
! Profile
! License
|-
| 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
|-
| 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. || ||
|-
|}

==Planning system supporting native NeTEx export ==

{| class="wikitable" style="width: 25%;"
!Name
!Availability
!Developped by
!Profile
!Additional documentation
|-
|style="text-align:center | [https://www.giro.ca/en-ca/our-solutions/segments/public-transport/ Hastus] || style="text-align:center |✅ || Giro || Nordic Dutch || Dutch patch: https://github.com/skinkie/hastus
|-
|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
|-
| style="text-align:center | [https://www.datagrafikk.no/?tag=dgbuss DG Buss] || style="text-align:center |✅ || Datagrafikk || Nordic ||
|-
| style="text-align:center | [https://www.trapezegroup.com.au/solutions/planning-and-scheduling-rail Planning & Scheduling for Train] ||style="text-align:center |✅ || Trapeze ||Nordic ||
|-
| 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
|-
| style="text-align:center | [https://turnit.com/ Turnit Ride] ||style="text-align:center |✅ ||Turnit for public transport ||Nordic ||
|-
|style="text-align:center | Nplan ||style="text-align:center |✅ ||Entur for public transport ||Nordic || backend: https://github.com/entur/uttu frontend: https://github.com/entur/enki
|-
| style="text-align:center | [https://www.hacon.de/en/portfolio/timetable-construction-disposition/ TPs Suite] ||style="text-align:center | ✅ ||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)'''''
[[File:NeTEx-part5.png|400px|right|]]

{| class="wikitable" style="width: 50%;"
|-
!
!Description
|-
| '''[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.
|-
| '''[https://data4pt.org/w/images/5/5b/Canonical_mapping_-_NeTEx_and_SIRI_new_modes_with_GBFS.pdf 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 =

{| class="wikitable" style="width: 35%;"
|-
!Name
!Description
|-
| '''[https://github.com/NeTEx-CEN/NeTEx NeTEx-CEN GitHub]'''
| Find xsd, examples and relevant documentation on NeTEx schema
|-
| '''[https://github.com/NeTEx-CEN/NeTEx-Profile-EPIP NeTEx EPIP profile GitHub]'''
| Find xsd and relevant documentation dedicated on NeTEx EPIP schema
|-
| '''[https://netex-cen.eu/ NeTEx Website]'''
| Find general information on NeTEx project
|-
|}

NeTEX

2025-08-11T12:05:13Z

Admin: /* Data validation tools */

= NeTEx overview 🔍 =
== What is NeTEx? ==

[[File:NeTEx.png|250px|right|]]

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 [https://netex-cen.eu/ NeTEX website].

⚙️ To verify your NeTEx data, use our '''[https://greenlight.atomite.io free validation tool]'''.

= NeTEx European Passenger Information Profile 🇪🇺 =

{| class="wikitable"
!
! Description
! Documentation
|-
|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. || 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].
|-
|width="150px" style="text-align:center |'''NeTEx EPIP Light''' || The official NeTEx schema is too large and complex for C# code generation tools to handle, so 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 '''graphic interactive technical presentation''' and the technical artefacts are available [https://data4pt.org/NeTEx/GraphicKit/Documention_of_reduced_XSD.html 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.

{| class="wikitable" style="width : 10%"
|-
! width="80px"|XML tools
! width="80px"|Description
|-
|[http://www.altova.com/xmlspy.html XML SPY] || commercial
|-
|[http://www.oxygenxml.com/ Oxygen]|| commercial
|-
|[http://www.garshol.priv.no/download/xmltools/ List of tools] || open-source
|-
{| class="wikitable"

== Conversion tools ==

{| class="wikitable" style="width:80%"
! colspan="1" | Name
! Availability
! width="40%" | |Description
! colspan="1" |Profile
!width="20%"| License
|-
| style="text-align:center |'''[https://github.com/entur/netex-protobuf netex-protobuf]''' ||style="text-align:center |✅ || NeTEx to protobuf converter || All ||EUPL
|-
|style="text-align:center | '''[https://github.com/CanalTP/transit_model/tree/master/gtfs2netexfr gtfs2netexfr]''' || style="text-align:center |✅ ||Export GTFS data to NeTEx. ||French ||
|-
| 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
|-
| 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
|-
| 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
|-
|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
|-
|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
|-
|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
|}

== Data validation tools ==

{| class="wikitable" style="width:40%;"
! width="25%" | Name
!width="10%" | Availability
! width="40%"| Description
!width="10%" | Profile
!width="10%" | License
|-
| style="text-align:center |'''[http://www.xmlsoft.org/ XMLlint]''' || style="text-align:center |✅ ||XML syntax validation, XSD schema validation and constraint checking. ||All ||MIT
|-
|style="text-align:center | ''' The Data4PT Validation tool''' ||style="text-align:center |✅||Validating NeTEx data. ||All ||
|-
| 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 ||
|-
| style="text-align:center |'''[https://github.com/entur/antu Antu]''' ||style="text-align:center |✅|| Validate NeTEx datasets against the Nordic NeTEx Profile. ||Nordic ||
|}

== Language bindings ==
{| class="wikitable" style="width: 45%;"
! Name
! Availability
! Description
! Profile
! License
|-
| 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
|-
|style="text-align:center | '''netex-csharp-model''' ||style="text-align:center |❌ || 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 ||
|-
|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
|-
|}

== Editing /Management & visualisation tools ==

{| class="wikitable" style="width: 75%;"
! Name
! Availability
! Description
! Profile
! License
! URL
|-
| 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 frontend - https://github.com/entur/enki
|-
|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 frontend - https://github.com/entur/abzu
|-
| 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 frontend - https://github.com/entur/chouette2
|-
|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="text-align:center |'''[https://mobilitx.diginext.fr/ mobilitx]''' || style="text-align:center |✅|| || || ||
|-
|style="text-align:center |'''[https://www.lumiplan.com/produit/mobiref/ mobiref]''' ||style="text-align:center | ✅ || || || ||
|-
|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
|-
|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 || ||
|-
|style="text-align:center | '''[https://www.ivu.com/news/news/article/delfi-successfully-migrates-to-ivucloud.html IVU.cloud]''' || style="text-align:center |✅|| ||EPIP || ||
|-
|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. 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 ==

{| class="wikitable" style="width: 60%;"
! Name
! Availability
! Description
! Profile
! License
|-
| 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
|-
| 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. || ||
|-
|}

==Planning system supporting native NeTEx export ==

{| class="wikitable" style="width: 25%;"
!Name
!Availability
!Developped by
!Profile
!Additional documentation
|-
|style="text-align:center | [https://www.giro.ca/en-ca/our-solutions/segments/public-transport/ Hastus] || style="text-align:center |✅ || Giro || Nordic Dutch || Dutch patch: https://github.com/skinkie/hastus
|-
|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
|-
| style="text-align:center | [https://www.datagrafikk.no/?tag=dgbuss DG Buss] || style="text-align:center |✅ || Datagrafikk || Nordic ||
|-
| style="text-align:center | [https://www.trapezegroup.com.au/solutions/planning-and-scheduling-rail Planning & Scheduling for Train] ||style="text-align:center |✅ || Trapeze ||Nordic ||
|-
| 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
|-
| style="text-align:center | [https://turnit.com/ Turnit Ride] ||style="text-align:center |✅ ||Turnit for public transport ||Nordic ||
|-
|style="text-align:center | Nplan ||style="text-align:center |✅ ||Entur for public transport ||Nordic || backend: https://github.com/entur/uttu frontend: https://github.com/entur/enki
|-
| style="text-align:center | [https://www.hacon.de/en/portfolio/timetable-construction-disposition/ TPs Suite] ||style="text-align:center | ✅ ||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)'''''
[[File:NeTEx-part5.png|400px|right|]]

{| class="wikitable" style="width: 50%;"
|-
!
!Description
|-
| '''[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.
|-
| '''[https://data4pt.org/w/images/5/5b/Canonical_mapping_-_NeTEx_and_SIRI_new_modes_with_GBFS.pdf 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 =

{| class="wikitable" style="width: 35%;"
|-
!Name
!Description
|-
| '''[https://github.com/NeTEx-CEN/NeTEx NeTEx-CEN GitHub]'''
| Find xsd, examples and relevant documentation on NeTEx schema
|-
| '''[https://github.com/NeTEx-CEN/NeTEx-Profile-EPIP NeTEx EPIP profile GitHub]'''
| Find xsd and relevant documentation dedicated on NeTEx EPIP schema
|-
| '''[https://netex-cen.eu/ NeTEx Website]'''
| Find general information on NeTEx project
|-
|}

Main Page

2025-08-05T14:23:46Z

Admin: /* Discover, Verify, Connect */

[[File:Data4PT logo flat.jpg|center|600px]]
<big>
= '''Welcome to the DATA4PT Wiki''' =
[[File:People Collaborating.png|right|400px]]

==Discover, Verify, Connect==
 
*'''Want to become aware of NAP and related standards?'''
[https://data4pt-project.eu/ Explore the DATA4PT project pages] and enjoy a wealth of knowledge!

*'''Need to verify your NeTEx data?'''
A NeTEx validation tool is planned to be delivered in the frame of the NAPCORE project. Meanwhile, [mailto:technical.support@itxpt.org?subject=NeTEx%20validation%20tool%20(from%20DATA4PT%20wiki) contact us here] for any questions or requests about this topic.

*'''Require support?'''
Don't hesitate! [https://docs.google.com/forms/d/1xQD5pPrxOFvoQrheQ0jpnFtWR3oWdCy5DyUZBRvWr0c/viewform?edit_requested=true Fill in a support request], and we're here to help.

*'''Like to comment on the available pages in the "Discussion" tab?'''
We value your input! [https://docs.google.com/forms/d/1xQD5pPrxOFvoQrheQ0jpnFtWR3oWdCy5DyUZBRvWr0c/viewform?edit_requested=true Contact us] and share your thoughts.

*'''Wish to contribute and create new pages?'''
[https://docs.google.com/forms/d/1xQD5pPrxOFvoQrheQ0jpnFtWR3oWdCy5DyUZBRvWr0c/viewform?edit_requested=true Join our expert community] and be part of something great!

==Why DATA4PT?==

DATA4PT is your one-stop destination for public transportation data, standards, and collaboration. Whether you're a newcomer or an expert, we're here to support your journey.

Join us in shaping the future of public transportation data together!
</big>

Main Page

2025-08-05T14:12:44Z

Admin: /* Welcome to the DATA4PT Wiki */

[[File:Data4PT logo flat.jpg|center|600px]]
<big>
= '''Welcome to the DATA4PT Wiki''' =
[[File:People Collaborating.png|right|400px]]

==Discover, Verify, Connect==
 
*'''Want to become aware of NAP and related standards?'''
[https://data4pt-project.eu/ Explore the DATA4PT project pages] and enjoy a wealth of knowledge!

*'''Need to verify your NeTEx data?'''
A validation tool is planned to be delivered in the frame of the NAPCORE project. Meanwhile, send us your questions and requests for such a tool
[mailto:technical.support@itxpt.org?subject=NeTEx%20validation%20tool%20DATA4PT%20wiki here].

*'''Require support?'''
Don't hesitate! [https://docs.google.com/forms/d/1xQD5pPrxOFvoQrheQ0jpnFtWR3oWdCy5DyUZBRvWr0c/viewform?edit_requested=true Fill in a support request], and we're here to help.

*'''Like to comment on the available pages in the "Discussion" tab?'''
We value your input! [https://docs.google.com/forms/d/1xQD5pPrxOFvoQrheQ0jpnFtWR3oWdCy5DyUZBRvWr0c/viewform?edit_requested=true Contact us] and share your thoughts.

*'''Wish to contribute and create new pages?'''
[https://docs.google.com/forms/d/1xQD5pPrxOFvoQrheQ0jpnFtWR3oWdCy5DyUZBRvWr0c/viewform?edit_requested=true Join our expert community] and be part of something great!

==Why DATA4PT?==

DATA4PT is your one-stop destination for public transportation data, standards, and collaboration. Whether you're a newcomer or an expert, we're here to support your journey.

Join us in shaping the future of public transportation data together!
</big>

Main Page

2025-08-05T14:12:14Z

Admin:

[[File:Data4PT logo flat.jpg|center|600px]]
<big>
= '''Welcome to the DATA4PT Wiki''' =
[[File:People Collaborating.png|right|400px]]

==Discover, Verify, Connect==
 
*'''Want to become aware of NAP and related standards?'''
[https://data4pt-project.eu/ Explore the DATA4PT project pages] and enjoy a wealth of knowledge!

*'''Need to verify your NeTEx data?'''
A validation tool is planned to be delivered in the frame of the NAPCORE X project. Meanwhile, send us your questions and requests for such a tool
[mailto:technical.support@itxpt.org?subject=NeTEx%20validation%20tool%20DATA4PT%20wiki here].

*'''Require support?'''
Don't hesitate! [https://docs.google.com/forms/d/1xQD5pPrxOFvoQrheQ0jpnFtWR3oWdCy5DyUZBRvWr0c/viewform?edit_requested=true Fill in a support request], and we're here to help.

*'''Like to comment on the available pages in the "Discussion" tab?'''
We value your input! [https://docs.google.com/forms/d/1xQD5pPrxOFvoQrheQ0jpnFtWR3oWdCy5DyUZBRvWr0c/viewform?edit_requested=true Contact us] and share your thoughts.

*'''Wish to contribute and create new pages?'''
[https://docs.google.com/forms/d/1xQD5pPrxOFvoQrheQ0jpnFtWR3oWdCy5DyUZBRvWr0c/viewform?edit_requested=true Join our expert community] and be part of something great!

==Why DATA4PT?==

DATA4PT is your one-stop destination for public transportation data, standards, and collaboration. Whether you're a newcomer or an expert, we're here to support your journey.

Join us in shaping the future of public transportation data together!
</big>

NeTEX

2025-07-30T21:02:01Z

Admin: /* Data validation tools */

= NeTEx overview 🔍 =
== What is NeTEx? ==

[[File:NeTEx.png|250px|right|]]

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 [https://netex-cen.eu/ NeTEX website].

⚙️ To verify your NeTEx data, use our '''[https://greenlight.atomite.io free validation tool]'''.

= NeTEx European Passenger Information Profile 🇪🇺 =

{| class="wikitable"
!
! Description
! Documentation
|-
|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. || 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].
|-
|width="150px" style="text-align:center |'''NeTEx EPIP Light''' || The official NeTEx schema is too large and complex for C# code generation tools to handle, so 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 '''graphic interactive technical presentation''' and the technical artefacts are available [https://data4pt.org/NeTEx/GraphicKit/Documention_of_reduced_XSD.html 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.

{| class="wikitable" style="width : 10%"
|-
! width="80px"|XML tools
! width="80px"|Description
|-
|[http://www.altova.com/xmlspy.html XML SPY] || commercial
|-
|[http://www.oxygenxml.com/ Oxygen]|| commercial
|-
|[http://www.garshol.priv.no/download/xmltools/ List of tools] || open-source
|-
{| class="wikitable"

== Conversion tools ==

{| class="wikitable" style="width:80%"
! colspan="1" | Name
! Availability
! width="40%" | |Description
! colspan="1" |Profile
!width="20%"| License
|-
| style="text-align:center |'''[https://github.com/entur/netex-protobuf netex-protobuf]''' ||style="text-align:center |✅ || NeTEx to protobuf converter || All ||EUPL
|-
|style="text-align:center | '''[https://github.com/CanalTP/transit_model/tree/master/gtfs2netexfr gtfs2netexfr]''' || style="text-align:center |✅ ||Export GTFS data to NeTEx. ||French ||
|-
| 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
|-
| 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
|-
| 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
|-
|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
|-
|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
|-
|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
|}

== Data validation tools ==

{| class="wikitable" style="width:40%;"
! width="25%" | Name
!width="10%" | Availability
! width="40%"| Description
!width="10%" | Profile
!width="10%" | License
|-
| style="text-align:center |'''[http://www.xmlsoft.org/ XMLlint]''' || style="text-align:center |✅ ||XML syntax validation, XSD schema validation and constraint checking. ||All ||MIT
|-
|style="text-align:center | '''[mailto:technical.support@itxpt.org?subject=Request%20for%20the%20Greenligt%20validation%20tool%20(DATA4PT%20wiki) The Data4PT Validation tool]''' ||style="text-align:center |✅||Validating NeTEx data. ||All ||
|-
| 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 ||
|-
| style="text-align:center |'''[https://github.com/entur/antu Antu]''' ||style="text-align:center |✅|| Validate NeTEx datasets against the Nordic NeTEx Profile. ||Nordic ||
|}

== Language bindings ==
{| class="wikitable" style="width: 45%;"
! Name
! Availability
! Description
! Profile
! License
|-
| 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
|-
|style="text-align:center | '''netex-csharp-model''' ||style="text-align:center |❌ || 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 ||
|-
|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
|-
|}

== Editing /Management & visualisation tools ==

{| class="wikitable" style="width: 75%;"
! Name
! Availability
! Description
! Profile
! License
! URL
|-
| 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 frontend - https://github.com/entur/enki
|-
|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 frontend - https://github.com/entur/abzu
|-
| 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 frontend - https://github.com/entur/chouette2
|-
|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="text-align:center |'''[https://mobilitx.diginext.fr/ mobilitx]''' || style="text-align:center |✅|| || || ||
|-
|style="text-align:center |'''[https://www.lumiplan.com/produit/mobiref/ mobiref]''' ||style="text-align:center | ✅ || || || ||
|-
|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
|-
|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 || ||
|-
|style="text-align:center | '''[https://www.ivu.com/news/news/article/delfi-successfully-migrates-to-ivucloud.html IVU.cloud]''' || style="text-align:center |✅|| ||EPIP || ||
|-
|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. 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 ==

{| class="wikitable" style="width: 60%;"
! Name
! Availability
! Description
! Profile
! License
|-
| 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
|-
| 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. || ||
|-
|}

==Planning system supporting native NeTEx export ==

{| class="wikitable" style="width: 25%;"
!Name
!Availability
!Developped by
!Profile
!Additional documentation
|-
|style="text-align:center | [https://www.giro.ca/en-ca/our-solutions/segments/public-transport/ Hastus] || style="text-align:center |✅ || Giro || Nordic Dutch || Dutch patch: https://github.com/skinkie/hastus
|-
|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
|-
| style="text-align:center | [https://www.datagrafikk.no/?tag=dgbuss DG Buss] || style="text-align:center |✅ || Datagrafikk || Nordic ||
|-
| style="text-align:center | [https://www.trapezegroup.com.au/solutions/planning-and-scheduling-rail Planning & Scheduling for Train] ||style="text-align:center |✅ || Trapeze ||Nordic ||
|-
| 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
|-
| style="text-align:center | [https://turnit.com/ Turnit Ride] ||style="text-align:center |✅ ||Turnit for public transport ||Nordic ||
|-
|style="text-align:center | Nplan ||style="text-align:center |✅ ||Entur for public transport ||Nordic || backend: https://github.com/entur/uttu frontend: https://github.com/entur/enki
|-
| style="text-align:center | [https://www.hacon.de/en/portfolio/timetable-construction-disposition/ TPs Suite] ||style="text-align:center | ✅ ||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)'''''
[[File:NeTEx-part5.png|400px|right|]]

{| class="wikitable" style="width: 50%;"
|-
!
!Description
|-
| '''[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.
|-
| '''[https://data4pt.org/w/images/5/5b/Canonical_mapping_-_NeTEx_and_SIRI_new_modes_with_GBFS.pdf 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 =

{| class="wikitable" style="width: 35%;"
|-
!Name
!Description
|-
| '''[https://github.com/NeTEx-CEN/NeTEx NeTEx-CEN GitHub]'''
| Find xsd, examples and relevant documentation on NeTEx schema
|-
| '''[https://github.com/NeTEx-CEN/NeTEx-Profile-EPIP NeTEx EPIP profile GitHub]'''
| Find xsd and relevant documentation dedicated on NeTEx EPIP schema
|-
| '''[https://netex-cen.eu/ NeTEx Website]'''
| Find general information on NeTEx project
|-
|}

FAQ NeTEX

2025-07-30T20:58:54Z

Admin:

== How do you create C# classes from the NeTEx XSD? ==

It is possible to create C# classes in different ways.

There are many tools out there, but for instance, you could use the Microsoft xsd.exe tool or the mganss/XMLSchemaClassGenerator tool available on Github at https://github.com/mganss/XmlSchemaClassGenerator

Currently there are some issues if you try to use the official NeTEx XSD as a starting point with either of these tools.

However, the above-mentioned tools work fine if you use them together with an adapted set of XSD-files available from Data4PT. The file set is designed to be compatible with the official NeTEx XSD and to cover many important use cases. It does however not cover all use cases possible with the official schema. There is an interactive graphical presentation of the adapted and reduced XSD available at https://data4pt.org/NeTEx/GraphicKit/Documention_of_reduced_XSD.html

If you wish to try out this reduced XSD, you can download it at https://data4pt.org/NeTEx/GraphicKit/XSD_reduced.zip

The work steps if you are using the Microsoft tool are:

Get the zipped XSD. Extract the ZIP to a folder.
Make sure that you have a recent version of the xsd.exe. It is part of the .NET Framework Developer Pack and can be downloaded from https://dotnet.microsoft.com/download/dotnet-framework
Install the developer pack. The xsd.exe will be placed in a folder with a path similar to C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.8 Tools
Open a command prompt in the same folder as where the NeTEx_publication_reduced-NoConstraint.xsd resides.
Execute the following command (you may have to adapt the path to xsd.exe): "C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.8 Tools\xsd.exe"/c/language:C# gml_combo_v3_2_1_simplified.xsd NeTEx_publication_reduced-NoConstraint.xsd
The work steps if you are using the MGANSS tool are:

* Get the zipped XSD. Extract the ZIP to a folder.
* Download and extract the binary from https://github.com/mganss/XmlSchemaClassGenerator/releases to a separate folder e.g. C:\MGANSS.
* Open a command prompt in the same folder as where the NeTEx_publication_reduced-NoConstraint.xsd resides.
* Execute the following command (you may have to adapt the path to the exe):
C:\MGANSS\XmlSchemaClassGenerator.Console.exe NeTEx_publication_reduced-NoConstraint.xsd -n http://www.opengis.net/gml/3.2=gml-v

--[[User:Anasfou|DATA4PT Team]] ([[User talk:Anasfou|talk]]) 19:41, 19 May 2022 (CEST)

== Is it possible to get access to the fares/schedule data? ==

Yes, the part 3 of NeTEx is fully dedicated to fares and works for all modes of public transport (bus, trains, trams, flexible modes, etc.).

There is a set of white papers describing NeTEx (http://netex-cen.eu/?page_id=14) and one is dedicated to fares:
http://netex-cen.eu/wp-content/uploads/2015/12/10.NeTEx-Fare-WhitePaper_1.04.pdf

Fares can be quite big topic and people defining them have a lot of imagination. This resulted in NeTex Part 3 being quite big and it is strongly advised to use only a small subset of it which is relevant to your needs. This what we call a Profile. France, Nordic countries, and UK have a fares national profiles. Information about current national profiles is about existing profiles is available [https://data4pt.org/w/index.php?title=NeTEX#Published_profiles here]. A minimum European profile is currently under specification with the support of DATA4PT and it is planned to be delivered to CEN processes by end of June 2024.

--[[User:Anasfou|DATA4PT Team]] ([[User talk:Anasfou|talk]]) 10:28, 06 November 2023 (CEST)

== Is it correct to include the data category VehicleType in the TimetableFrame as in the NX-PI-01_LU_NAP_LINE_AVL-AVL-91_20210113.xml EPIP example file? ==

This example file is available for download under https://data4pt-project.eu/knowledge-database/guidelines/, it includes the data category VehicleType.
Yes, the European Passenger Information Profile, CEN/TS 16614-4:2020,(EPIP) states that the data category VehicleType can be provided in the TimetableFrame. See table 131 – TypeOfFrame: EU_PI_TIMETABLE in the documentation.

--[[User:Anasfou|DATA4PT Team]] ([[User talk:Anasfou|talk]]) 19:50, 19 May 2022 (CEST)

== Are there other possibilities where to define the vehicle type? ==

Yes, the European Passenger Information Profile, CEN/TS 16614-4:2020,(EPIP) actually also allows, as an option, that the data category VehicleType is instead provided in the ResourceFrame. See table Table 127 – TypeOfFrame: EU_PI_COMMON in the documentation. This second option is now (2021-02-24) also supported in the set of XSD-files available for download from the project website.

--[[User:Anasfou|DATA4PT Team]] ([[User talk:Anasfou|talk]]) 19:50, 19 May 2022 (CEST)

== How to manage translations with "MultilingualString" in NeTex? ==
There are a lot of MultilingualString in NeTEx. All implementions use them. It may be slightly different depending on the language (Java, C/C++, Ruby, Go, Python, etc.) and also on the use case (e.g. there are translations available to be used).

Furthermore, for translations, AlternativeTexts are expected to be used (they do contain MultilingualString but also some more information as presented in the following schema).

https://data4pt.org/w/images/2/2a/MultilingualString.png

Also note that an object can have multiple names (not translations but different possible naming): in such case AlternativeNames should be considered.

An xml example (EPIP example file), where MultilingualString attributes (lang) are used is available in the DATA4PT knowledge database.

To check your data sets, you may use EPIP adapted XML-schema. The graphic documentation of the EPIP NeTEx XSD, including MultilingualString description is available here .

Generally, NeTEx example files can be found in the main github repository , while also other databases with examples are available, (e.g. from ENTUR).

--[[User:Anasfou|DATA4PT Team]] ([[User talk:Anasfou|talk]]) 19:57, 19 May 2022 (CEST)

== When I try to generate java classes, Ι have a duplication class error. Is it necessary to have those 2 types: vehicleJourneyStopAssignmentsInFrame_RelStructure and VehicleJourneyStopAssignmentsInFrame_RelStructure? ==

It should be only one branch vehicleJourneyStopAssignmentsInFrame_RelStructure. Maybe the second is in a "dead file". Please check https://github.com/NeTEx-CEN/NeTEx/blob/master/xsd/netex_part_2/part2_journeyTimes/netex_vehicleJourney_version.xsd).

In general, regarding java classes, you may check ENTUR recommendations available here https://github.com/entur/netex-java-model.

--[[User:Anasfou|DATA4PT Team]] ([[User talk:Anasfou|talk]]) 20:03, 19 May 2022 (CEST)

== How to use "keylist" to express secondary identifiers for network? ==

The element ''keylist'' and child element ''KeyValue'' is the right way to add secondary identifiers for a network. The ''keylist'' element should be positioned before ''PrivateCode''. For example:
<Network version="any" changed="2022-06-10T09:30:36Z" id="FR1:Network:1045:LOC">
<keyList>
<KeyValue typeOfKey="ALTERNATE_IDENTIFIER">
<Key>NETWORK_SAE</Key>
<Value>456</Value>
</KeyValue>
</keyList>
<PrivateCode>123</PrivateCode>
</Network>

--[[User:Anasfou|DATA4PT Team]] ([[User talk:Anasfou|talk]]) 18:47, 11 June 2022 (CEST)

== Is there a way to express in NeTEx and/or SIRI that the information of provided occupancy level of a public transport vehicle is based on a prognosis (e.g. historical data) or real-time measured data? ==

SIRI VM (vehicle monitoring service) and SIRI SM (stop monitoring) already today allow a simple enumeration describing the general Occupancy level for a monitored Vehicle Journey.
In the coming SIRI version (currently under voting process):
- the enumeration value set will be extended and additional values added. Some additional constructions on Call level will also be added.
- SIRI Estimated Timetable (ET) will be extended with the possibility to exchange passenger count and occupancy information per Call. This will include recorded information as well as estimated values for coming Calls.
The XSD itself is already fully finalised and usable from here https://github.com/SIRI-CEN/SIRI

Also, you can find a very relevant document about " Vehicle Occupancy Data" from RTIG (UK trade body for public transport technology stakeholders) here : https://www.rtig.org.uk/system/files/documents/RTIGT039-1.1%20Providing%20Vehicle%20Occupancy%20Data%20-%20Data%20Interfaces.pdf
It includes detailed references to SIRI and NeTEx data structures :
- The NeTEx format includes PassengerCapacity as part of the VehicleType and has a structure that allows for detail - including seated and standing capacities, to be handled
- The Occupancy field in SIRI is one of the optional properties of ProgressInfo of a MonitoredVehicleJourney. This element can be used in both SIRI-SM and SIRI-VM services.
- There is, in addition, an Occupancy field in the EstimatedCall structure of the SIRI-ET service. If this is populated it represents a predicted passenger load. If the corresponding field is filled in a MonitoredVehicleJourney, this should be used in preference - as it reflects the actual current passenger occupancy value.

--[[User:Anasfou|DATA4PT Team]] ([[User talk:Anasfou|talk]]) 12:40, 03 August 2022 (CEST)

== How different levels of stops of complex stations are expressed in NeTEx EPIP? ==

To describe different levels of stops in complex stations, the XSD is adapted as follows:

<xsd:complexType name="levels_RelStructure">
<xsd:sequence>
<xsd:element ref="Level" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attributeGroup ref="ModificationSetAttributeGroup"/>
</xsd:complexType>

The updated XSD is available https://data4pt.org/w/index.php?title=NeTEX#NeTEx_EPIP.
--[[User:Anasfou|DATA4PT Team]] ([[User talk:Anasfou|talk]]) 13:32, 3 August 2022 (CEST)

== How to differentiate a basic JourneyPattern from one that takes into account re-routings due to planned deviations? ==

For planned deviations, another version of JourneyPattern needs to be described having different validity conditions than the regular JourneyPattern. For deviations that occur the same day of the operation, SIRI Estimated Timetable (ET) can be used, and for deviations known some days before the operational day, SIRI Production Timetable (PT) can be used.

Moreover, there is today no element in the XSD that states if a JourneyPattern is "normal" or "diversion".
This means that you would probably need to analyse the timetable over a longer period of time and compare how often different JourneyPatterns (or versions of a certain JourneyPattern) are actually used on a certain Direction to find which is the "normal" one.

--[[User:Anasfou|DATA4PT Team]] ([[User talk:Anasfou|talk]]) 19:16, 9 September 2022 (CEST)

== Where can I find the UML model for NeTEX? ==

The UML of NeTEx is available https://www.netex-cen.eu/model/conceptual/part1/index.htm. NeTEx is based on data model Transmodel, of which the UML is available in Enterprise Architect file https://www.transmodel-cen.eu/model/. This version corresponds to the CEN v6.0 release c2018, with revisions from 2021. For more information regarding the data model (Transmodel) please check here https://www.transmodel-cen.eu/downloads/. Updates on the Transmodel UML are expected in the coming period.

--[[User:Anasfou|DATA4PT Team]] ([[User talk:Anasfou|talk]]) 16:08, 22 September 2022 (CEST)

== Where can I find information about how and when NeTEx is going to be able to store data about: taxi services, rent of vehicles (with or without driver), parking areas (the classical one, for private cars etc.), low emission zones in cities? ==

TRANSMODEL Part 10 and NeTEx Part 5 (Alternative Modes API) are relevant to the referred functional scope except of low emission zones. In particular, NeTEx Part 5, covers all alternative modes: Vehicle Sharing (any kind of vehicle, car, bike, scooter etc.), Vehicle Pooling (any kind of vehicle, car, van etc.), Transport Network Companies, Renting, Taxis.

NeTEx also includes mobilityServiceConstraintZones that can be applied to any public transport and new mode services and be a restriction for certain types of vehicles. However this needs to be connected to some services, since NeTEx and Transmodel are not describing the private vehicle use (except for carpooling where there is a public offer on the private vehicle). So, there is no explicit description of Low Emission Zones, where the limitation is triggered by a pollution level. Possible enhancement can be considered.

NeTEx Part 5 (CEN/TS 16614-5) is complementary to the previous parts (1/2/3/4). It is fully aligned with the new Transmodel Part 10, being the underlaying data model.
Transmodel extension published as CEN TS 17413:2019. The conversion of CEN TS 17413:2019 into an EN is going to be the Transmodel -Part 10. General information about NeTEx Part 5 is available here http://netex-cen.eu/wp-content/uploads/2021/03/NeTEx-extension-for-New-Modes-Detailed-Scope-v04.pdf. The specifications are also now published by CEN.

Besides the CEN documentation, the users (IT suppliers/operators, in general developers etc.) can have access to the technical artefacts (XSD) through the publicly available repository in GitHub (check https://data4pt.org/w/index.php?title=NeTEX#NeTEx_Part_5_for_New_Modes). In addition, there is an available mapping-comparison with GBFS, the bike sharing data format from Mobility Data https://data4pt.org/w/index.php?title=NeTEX#Canonical_mapping_with_GBFS.

Since NeTEx is about scheduled data (including location of parking places, capacity etc.), is complemented by SIRI for realtime data. Therefore, SIRI has also been extended (recently voted) to cover new modes (vehicles availability, parking places availability etc.). This extension is in SIRI Part 4 (Facility Monitoring).
In particular for parking, there is a comprehensive description in NeTEx. France for example has already a dedicated profile for parking – the documentation in french is available here http://www.normes-donnees-tc.org/wp-content/uploads/2021/10/NF_Profil-NeTEx-pour-les-ParkingsF-v1.2a.pdf ).

--[[User:Anasfou|DATA4PT Team]] ([[User talk:Anasfou|talk]]) 16:28, 22 September 2022 (CEST)

== How to manage codespaces in NeTEx where unique identifiers are needed? ==

In NeTEx a rule to code IDs is included to ease uniqueness (Europe wide) and stability of IDs.

[[File:1.jpg|thumb]]

For example in Italy, they applied this rule, using NUTS code for country-code and local-code.

<ServiceCalendarFrame id="epd:IT:ITC1:ServiceCalendarFrame_EU_PI_CALENDAR:scf" version="any">
<TypeOfFrameRef versionRef="any" ref="epip:EU_PI_CALENDAR"/>
<ServiceCalendar id="IT:ITC1:ServiceCalendar:C01" version="any">
<dayTypes>
<DayType id="IT:ITC1:DayType:5:dt:A" version="any">

Any other rule can be accepted provided that IDs are unique and stable. Using operator's code inside an ID is not suggested as the Operator can change. With the NeTEx recommended rule, even if the Operator changes, the ID will have to remain the same, ignoring that change. Also the Operator code may not be a good choice for the uniqueness of shared lines or shared stops.

--[[User:Anasfou|DATA4PT Team]] ([[User talk:Anasfou|talk]]) 10:04, 05 October 2022 (CEST)

== How to describe two similar stops sequences when the one has a boarding and alighting information and the other has not? ==

One ROUTE is enough, it can cover two different JOURNEY PATTERNS if the vehicle will traverse the same physical path in both cases. The relation between ROUTE POINT and SCHEDULED STOP POINT is formally through projection.

--[[User:Anasfou|DATA4PT Team]] ([[User talk:Anasfou|talk]]) 11:12, 2 November 2022 (CET)

== Should "RouteLink" have a unique identifier? ==

Each unique RouteLink should have a unique identifier (id-attribute).
Note that a RouteLink over time may be altered and still retain its original identifier, but each modification should have a different version-attribute.

At the same time it is OK to refer to the same RouteLink in relation to different Lines, if those Lines include a shared physical path for some part of the respective routes. This applies also if the Lines are provided in separate files.

--[[User:Anasfou|DATA4PT Team]] ([[User talk:Anasfou|talk]]) 15:44, 12 January 2023 (CET)

== What is the difference between stopAreas, Quays, stopPlaces? ==

A STOP AREA is "A group of SCHEDULED STOP POINTs close to each other." so it definitely does not correspond to the quays and stopPlaces of the IFOPT base.

Having a scheduledStopPoint belonging a a single journeyPattern, however this does go via the StopPointInJourneyPattern which is allowing multiple reuse of the same scheduledStopPoint. A scheduledStopPoint can be assigned to StopPlace or Quays thanks to the PassengerStopAssignment.
[[File:Stop assignment model.png|thumb]]

--[[User:Anasfou|DATA4PT Team]] ([[User talk:Anasfou|talk]]) 11:50, 3 May 2023 (CET)
== How to model a transport ticket that costs 6 euros on the 1st day and 3 euros for each additional day? ==

This is a typical case of pricing of a SALES OFFER PACKAGEs: several such packages may exist composed of 1, 2,…n elements and a specific price is provided according to the number of the SALES OFFER PACKAGE ELEMENTS in the SALES OFFER PACKAGE.

So for this particular example:
The PRICE of the SALES OFFER PACKAGE composed of one SALES OFFER PACKAGE ELEMENT is 6 euros.
The price of the SALES OFFER PACKAGE composed of 2…n SALES OFFER PACKAGE ELEMENTs is 6 + (n-1)*3 euros.

You may consider a PREASSIGNED FARE PRODUCT (e.g. a day pass) which is provided by one or more SALES OFFER PACKAGE ELEMENTs. Access rights may correspond to a PREASSIGNED FARE PRODUCT but also other types of access right might be granted by a SALES OFFER PACKAGE ELEMENT.

Moreover, the definition of TimeIntervals is related to the description of the time-related fare structure elements (for example the use of the network during 1 hour would represent a SALES OFFER PACKAGE ELEMENT A - 1 hour pass, the use of the network during 5 hours represent a SALES OFFER PACKAGE ELEMENT B - 5 hours pass). In the present example, the fare structure elements are identical (use of the network during one day several times). So only the pricing differs according to the number of products purchased. TimeInterval will be rather suitable to the pricing of a single trip (DayOffset are only there because some long distance trips can exceed the day).

[[File:Stop assignment model.png|thumb]]

--[[User:Anasfou|DATA4PT Team]] ([[User talk:Anasfou|talk]]) 11:13, 1 September 2023 (CET)
== How to model "hail and ride" section? ==
Hail and ride usually is modelled by using a FlexibleStopPlace that can refer to HailAndRide areas as shown in the UML diagrams below. Hail and Ride is described in CEN TS 16614-1. Examples can be found in [https://github.com/NeTEx-CEN/NeTEx/tree/master/examples NeTEx-CEN GitHub] like this [https://github.com/NeTEx-CEN/NeTEx/blob/master/examples/functions/timetable/Netex_01.4_Bus_SimpleTimetable_WithConnection.xml one].

[[File:FlexibleStopPlace with HailandRideArea.png|thumb|UML diagram of FlexibleStopPlace with HailAndRide]]

[[File:HailAndRide.png|thumb|364x364px]]

--[[User:Anasfou|DATA4PT Team]] ([[User talk:Anasfou|talk]]) 16:40, 17 October 2023 (CET)

== How to start implementing NeTEx Part 5 for new modes (vehicle sharing, rental, taxis etc.)? ==
Simple steps for new users/implementers of NeTEx Part 5:

1) Watch the introduction webinar for NeTEx Part 5, available on [https://data4pt-project.eu/knowledge-database/training-material/ DATA4PT website] under the title “DATA4PT webinar 24 November 2022: NeTEx and SIRI standards for new modes” (direct link to the [https://www.youtube.com/watch?v=F_lK1mfKgbk video] and presentation of the [https://data4pt-project.eu/wp-content/uploads/2022/12/DATA4PT-NeTEx-validation-tool-webinar_Presentation.pdf webinar]).

2) Read the pdf – official CEN documentation CEN/TS 16614-5 (where also some examples are given). The document can be bought from any national standardization body.

3) Use XML editor (there are commercial tools or free tools - a short list is available by [https://data4pt.org/w/index.php?title=NeTEX#Software_.26_tools_.F0.9F.A7.B0 DATA4PT wiki]), to check the [https://github.com/NeTEx-CEN/NeTEx/tree/master/xsd/netex_part_5 XSD for Part 5] and check the [https://github.com/NeTEx-CEN/NeTEx/tree/master/examples/functions/newModes examples] from [https://github.com/NeTEx-CEN/NeTEx/tree/master Github NeTEx repository].

4) Create your own .xml examples based on the XSD and the examples available in GitHub. If the user has no technical background, then IT tool provider is needed to support him/her following the same steps. A general list of tools is available in [https://data4pt.org/w/index.php?title=NeTEX#Software_.26_tools_.F0.9F.A7.B0 DATA4PT wiki.]

5) Validate the example with the XML editor and the Greenlight validator. The latter is the tool that provides feedback both on errors that concern the NeTEx XSD but also the content (plausibility checks).

6) Use the [https://data4pt-project.eu/requests-requirements/ DATA4PT helpdesk] for more technical guidance.

Finally, a useful material for small operators that they use already GBFS is:

-the canonical mapping between GBFS and NeTEx/SIRI to get their head around the fields/attributes they need at a quick glance

- the .xml example that is GBFS-based from the NeTEx GitHub repo.

Relevant material is available [https://data4pt.org/w/index.php?title=NeTEX#NeTEx_part_5_for_.F0.9F.86.95_modes here]

--[[User:Anasfou|DATA4PT Team]] ([[User talk:Anasfou|talk]]) 10:45, 6 November 2023 (CET)

== How to implement DayTypeAssignment in NeTEx? Using OperatingPeriodRef or UicOperatingPeriodRef? ==

Both "OperatingPeriodRef" and "UicOperatingPeriodRef" are in the same substitutionGroup named OperatingPeriods, therefore both options may be used without impacting the interoperability of the file. UicOperatingPeriodRef is probably cleaner to reference a UicOperatingPeriod.In NeTEx EPIP (European Passenger Information Profile) UicOperatingPeriod is mandatory (providing the ValidDayBits is mandatory).
[[File:Image.png|thumb]]

--[[User:Anasfou|DATA4PT Team]] ([[User talk:Anasfou|talk]]) 12:18, 16 February 2024 (CET)

== Does a scheduledStopPoint ID need to be unique per public transport Line? ==

A scheduledStopPoint ID does not need to be unique per Line.
In situations where several Lines use the exact same stop point they may refer to this same stop point using the same scheduledStopPoint ID. If there is a unique ID for the exact same stop that can be used globally it is also ideal from interoperability point of view.

More precisely, based on NeTEx terminology, a LINE is defined as "A group of ROUTEs which is generally known to the public by a similar name or number."
A ROUTE is defined as "An ordered list of located POINTs defining one single path through the road (or rail) network. A ROUTE may pass through the same POINT more than once."
JOURNEY PATTERN, defined as "An ordered list of SCHEDULED STOP POINTs and TIMING POINTs on a single ROUTE, describing the pattern of working for public transport vehicles. A JOURNEY PATTERN may pass through the same POINT more than once. The first point of a JOURNEY PATTERN is the origin. The last point is the destination."

In order not to make confusion, when parsing the XML input, the data user needs to sufficiently preserving awareness of the context in which the scheduledStopPoint ID is being used. With a correct awareness of the context, the ID can be augmented, for example via a composite ID made up of Line plus stop IDs. This would make different occurrences of the same stop have different IDs, without breaking the NeTEx rules.

--[[User:Anasfou|DATA4PT Team]] ([[User talk:Anasfou|talk]]) 17:38, 25 March 2024 (CET)

== Can NeTEx handle frequency-based services? ==
Frequency based serves are typically specified as operating at a given interval, rather than particular times. From a passenger point of view multiple journeys will typically be presented as a single journey running at an approximate interval, for example “every six to 10 minutes”. NeTEx uses TEMPLATE VEHICLE journeys to describe such journeys. From an operational point of view there will still need to be specific service journeys scheduled to fulfil the required frequency of service and NeTEx can also include these to support real time journeys.

== Can I have different journey timings for different times of day? ==
Part 2 of NeTEx includes reusable components for constructing timetables of journeys from reusable components, NeTEx separates the concerns of where the timing of a PT route takes place (The TIMING PATTERN made up of TIMING POINTs and TIMING LINKs) from the actual timing values (which are held separately as RUN TIMEs and WAIT TIMEs). Different sets of timing values belong to different TIME DEMAND TYPEs (Peak, off peak, late night, etc) can be used with the same TIMING PATTERN to generate accurate timetables for journeys at different times of day.

== Can NeTEx describe zone-based fares? ==
NeTEx can be used to describe zone-based fare systems of any topology ranging from a simple patchwork (adjacent zones) to the complex, (honeycomb, doughnut) etc). The TARIFF ZONE allows zones to be associated with stops and stations. Mixed zonal and stage systems are also possible. Fare pricing may be a flat fare system per zone, or zone to zone using a (DISTANCE MATRIX ELEMENT), or be differentially priced for particular sequences of zones (using FARE STRUCTURE ELEMENTs in SEQUENCE).

== Can I restrict certain products to certain classes of user? ==
Among the many different usage conditions that can be specified for NeTEx fare products are restrictions on the type of user – child, senior, student, disabled, etc using a USER PROFILE that may be given precise eligibility criteria (e.g. on age, membership, domicile, etc). A GROUP PROFILE allows the number and makeup of groups to be specified; it can also be used to specify companion criteria for disabled users and other special cases.

== Can I specify time-based constraints on travel? ==
Some fare products only allow travel at particular times – such constraints can be expressed using USAGE PARAMETERs. Others only allow travel for a particular duration; FARE STRUCTURE ELEMENTs with TIME STUCTURE FACTORs can be used to describe the different durations. Furthermore, sometimes journey time is related to journey length, so for example a longer time is allowed for a two-zone trip than a one zone trip; all this can be precisely specified in NeTEx.

Temporal conditions may also apply to the purchase or refund of tickets, likewise, expressed as USAGE PARAMETERs attached to fare products.

As well as the routine examples given above, NeTEx can also handle more complex cases. For example, in the periphery of a large city, off peak times may start at different times in each station since by the time a journey to the centre starting from the station ends, the peak period will have ended.

== Does NeTEx support dynamic/yield managed pricing? ==
For long-distance travel, especially on-rail, there is increasing use of yield managed fares with dynamic pricing, provided by web services. Note that such applications increase rather than decrease the need for standards such as NeTEx as such applications nonetheless require a machine-readable definition of the access rights fare structure and usage conditions that apply to the products for which prices are supplied. Furthermore, the search parameters used to find the best fare for a user (such as age, possession of rail cards, fulfilment method etc) need to correspond to the properties of the fare product. The NeTEx Part3 specification and UML model includes an annex showing a sample fare query which shows all the NeTEx model elements relevant for constructing a Fare API.

== Can NeTEx define products for modern e-card based ticketing? ==
Yes. Electronic payment cards such as OV Chipkart (NL), Oyster (London region), Navigo (Paris region) Sube T (Madrid), BIP Card (Turin) are becoming increasingly common and etc transport operators are able to devise increasingly sophisticate products. For example,, Oyster has fares that adjust according to consumption, capping the cost of trips made in a day to that of a day pass. NeTEx is able to describe the fare structures and scope and conditions for such complex products, as well as to supporting a record of consumption for account-based products. (A NeTEx SALES TRANSACTION records an individual PRODUCT SALE).

As products on cards are physical invisible to the user, the ability to create user readable representations become increasingly important – such applications require a machine-readable format with corresponding human readable rendering, such as is available through NeTEx.

== Does NeTEx support Flexible and Demand Responsive Travel? ==
Yes, unlike classical route and timetable standards, NeTEx is also designed to support FTS (Flexible Transport Service) and DRT (Demand Responsive Transport). DRT and FTS often cover similar services; FTS being more generic since flexibility may not be directly linked to the demand, but may be related to some operating needs or cost optimisations.

The flexibility can be applied to the line, route and stop structure (areas, corridors, hail and ride, etc.) or to their scheduling (dynamic and/or demand responsive passing times, with all necessary booking arrangements and contact details).

== Can I create applications to run in different national Languages? ==
Yes, NeTEx includes full support for internationalisation. All text elements may be created in multiple languages so that place names and other names and descriptions can be provided in one or more languages. Other aspects important for multiregional use are parameterized such as time zones, currency, etc. and the Calendar functions allow conditions based on different national holidays to be described.

== Can I have different versions of data for the same element extant at the same time? ==
Yes, every NeTEx data element can be versioned, and multiple versions can coexist. Coherent sets of data are assembled for exchange using a ‘version frame’, which itself has a version and knows the version of the elements in it. There are specific types of version frame for different types of data that are commonly exchanged together (SERVICE, TIMETABLE, FARE etc).

== Can I create Network maps with NeTEx? ==
Yes, one of the additional capabilities of NeTEx is the ability to define and exchange the full topology of a network as presented in simplified view to a user (often with presentational attributes such as colour), with non-directional network segments, loops etc, while also retaining a projection onto the actual underlying stops and route. This allows automatic creation of interactive map applications.

* The LINE element names the line and sets basic properties

* The LINE NETWORK and LINE SECTION elements can be used to describe the topology

* The ROUTE, ROUTELINK, and ROUTE POINT elements can be used to define the directional elements of the underlying line

* The SCHEDULED STOP POINT can be used to define the stops of a line.

All these objects can have their own geographic positions and geometry or/and be projected onto a custom drawn map using a SCHEMATIC MAP element.

== I have my own classification for Stops/ Lines / etc. Can NeTEx handle this? ==
Yes, NeTEx allows arbitrary user defined code classifications for elements using the TYPE OF STOP, TYPE OF LINE and other ‘Type of Entity’ elements that. In addition, NeTEx, to encourage standardised use, also provides fixed enumerations of many commonly found classifications of specific elements, including types of equipment, on-board facilities, etc. The ‘Key Value’ extension mechanism allows Also allows additional user defined attributes to be added, which can include classifier.

Main Page

2025-07-30T20:31:27Z

Admin: /* Welcome to the DATA4PT Wiki */

[[File:Data4PT logo flat.jpg|center|600px]]
<big>
= '''Welcome to the DATA4PT Wiki''' =
[[File:People Collaborating.png|right|400px]]

==Discover, Verify, Connect==
 
*'''Want to become aware of NAP and related standards?'''
[https://data4pt-project.eu/ Explore the DATA4PT project pages] and enjoy a wealth of knowledge!

*'''Need to verify your NeTEx data?'''
[mailto:technical.support@itxpt.org?subject=Greenlight%20tool%20DATA4PT%20wiki Utilize our free validation tool] for accurate results!

*'''Require support?'''
Don't hesitate! [https://docs.google.com/forms/d/1xQD5pPrxOFvoQrheQ0jpnFtWR3oWdCy5DyUZBRvWr0c/viewform?edit_requested=true Fill in a support request], and we're here to help.

*'''Like to comment on the available pages in the "Discussion" tab?'''
We value your input! [https://docs.google.com/forms/d/1xQD5pPrxOFvoQrheQ0jpnFtWR3oWdCy5DyUZBRvWr0c/viewform?edit_requested=true Contact us] and share your thoughts.

*'''Wish to contribute and create new pages?'''
[https://docs.google.com/forms/d/1xQD5pPrxOFvoQrheQ0jpnFtWR3oWdCy5DyUZBRvWr0c/viewform?edit_requested=true Join our expert community] and be part of something great!

==Why DATA4PT?==

DATA4PT is your one-stop destination for public transportation data, standards, and collaboration. Whether you're a newcomer or an expert, we're here to support your journey.

Join us in shaping the future of public transportation data together!
</big>

Main Page

2025-07-30T20:23:46Z

Admin: /* Discover, Verify, Connect */

[[File:Data4PT logo flat.jpg|center|600px]]
<big>
= '''Welcome to the DATA4PT Wiki''' =
[[File:People Collaborating.png|right|400px]]

==Discover, Verify, Connect==
 
*'''Want to become aware of NAP and related standards?'''
[https://data4pt-project.eu/ Explore the DATA4PT project pages] and enjoy a wealth of knowledge!

*'''Need to verify your NeTEx data?'''
[mailto:technical.support@itxpt.org Utilize our free validation tool] for accurate results!

*'''Require support?'''
Don't hesitate! [https://docs.google.com/forms/d/1xQD5pPrxOFvoQrheQ0jpnFtWR3oWdCy5DyUZBRvWr0c/viewform?edit_requested=true Fill in a support request], and we're here to help.

*'''Like to comment on the available pages in the "Discussion" tab?'''
We value your input! [https://docs.google.com/forms/d/1xQD5pPrxOFvoQrheQ0jpnFtWR3oWdCy5DyUZBRvWr0c/viewform?edit_requested=true Contact us] and share your thoughts.

*'''Wish to contribute and create new pages?'''
[https://docs.google.com/forms/d/1xQD5pPrxOFvoQrheQ0jpnFtWR3oWdCy5DyUZBRvWr0c/viewform?edit_requested=true Join our expert community] and be part of something great!

==Why DATA4PT?==

DATA4PT is your one-stop destination for public transportation data, standards, and collaboration. Whether you're a newcomer or an expert, we're here to support your journey.

Join us in shaping the future of public transportation data together!
</big>

Main Page

2024-10-17T13:21:13Z

Admin:

[[File:Data4PT logo flat.jpg|center|600px]]
<big>
= '''Welcome to the DATA4PT Wiki''' =
[[File:People Collaborating.png|right|400px]]

==Discover, Verify, Connect==
 
*'''Want to become aware of NAP and related standards?'''
[https://data4pt-project.eu/ Explore the DATA4PT project pages] and enjoy a wealth of knowledge!

*'''Need to verify your NeTEx data?'''
[https://greenlight.itxpt.eu/ Utilize our free validation tool] for accurate results!

*'''Require support?'''
Don't hesitate! [https://docs.google.com/forms/d/1xQD5pPrxOFvoQrheQ0jpnFtWR3oWdCy5DyUZBRvWr0c/viewform?edit_requested=true Fill in a support request], and we're here to help.

*'''Like to comment on the available pages in the "Discussion" tab?'''
We value your input! [https://docs.google.com/forms/d/1xQD5pPrxOFvoQrheQ0jpnFtWR3oWdCy5DyUZBRvWr0c/viewform?edit_requested=true Contact us] and share your thoughts.

*'''Wish to contribute and create new pages?'''
[https://docs.google.com/forms/d/1xQD5pPrxOFvoQrheQ0jpnFtWR3oWdCy5DyUZBRvWr0c/viewform?edit_requested=true Join our expert community] and be part of something great!

==Why DATA4PT?==

DATA4PT is your one-stop destination for public transportation data, standards, and collaboration. Whether you're a newcomer or an expert, we're here to support your journey.

Join us in shaping the future of public transportation data together!
</big>

Draft:Portugal

2024-10-08T13:20:22Z

Admin: Admin moved page Draft:Portugal to Portugal

#REDIRECT [[Portugal]]

Portugal

2024-10-08T13:20:22Z

Admin: Admin moved page Draft:Portugal to Portugal

== Overview in the National Level ==
In Portugal, AMP (Metropolitan Area of Porto) is working with native NeTEx, and it is anticipated that other PTAs will soon adopt and use it as well. AMP has extensively utilized the validator, while TML (Metropolitan Transport of Lisbon) and Carris (one of the largest PTOs in Portugal) have also employed it to validate some NeTEx information.

Regarding the use of the NAP, the number of users has been growing considerably, and the available information is highly diverse. It encompasses public transportation (both roadway and railway), electric charging points, Zones of Conditional Automobile Access (UVAR), loading and unloading zones, scooter parks, parking lots, taxi ranks, bus lanes, passenger drop-off and pick-up zones, bicycle parking, motorcycle parks, cycle paths, and other related information.

== Use cases ==

=== Description ===
The Metropolitan Area of Porto covers 2,041 km², with a population of 1.76 million, including 76,000 university students, which represents 20% of Portugal's university population. As a Transport Authority, responsibilities include overseeing bus services operated by private companies, which covers:

* Planning (routes, interconnections, frequencies, coverage, etc.)
* Establishing ticketing, fees, pricing, and regulations
* Managing contracts
* Handling payments related to contractual obligations (bonuses/penalties)
* Providing public information (indirectly, to other public or private entities that are better positioned to integrate the information)

To meet these requirements, the exchange of detailed information is essential. NeTEx has been chosen for data exchange between stakeholders due to its advantages:

* Comprehensive coverage of all transport system areas
* Object-oriented data model
* Version control mechanisms
* Supports transmission as both payload and file
* Compliant with the Portuguese NAP standard (IMT)
* A fully recognized European standard since 2006

=== Architecture ===
The platform is designed as a collection of microservices, with information exchange between specialized applications managed through NeTEx. This architecture allows for the replacement of any application with a commercial, internal, or open-source solution, provided that it supports exporting or importing data in the NeTEx format.
[[File:Portugal schema.png|thumb|656x656px|center|Flux diagram of NeTEx exchange]]
=== Use cases ===
PLIM is the name of the platform where all internal information is communicated using NeTEx. It produces NeTEx, GTFS, SIRI, and GTFS-feed formats for dissemination to National Access Points (NAP).

=== Outcome ===
Netex will be seen as the base for information sharing as long as it covers all the aspects of the organisation needs. Potential extensions might be considered.

In the future, it is hoped that comprehensive transport information will be available through NeTEx and SIRI via collaborative sharing. This information will enable companies and individual projects to develop applications that address global needs or specific interests.

Draft:Switzerland

2024-10-08T12:56:34Z

Admin: Admin moved page Draft:Switzerland to Switzerland

#REDIRECT [[Switzerland]]

Switzerland

2024-10-08T12:56:34Z

Admin: Admin moved page Draft:Switzerland to Switzerland

== Overview in the National Level ==
In Switzerland the [https://www.bav.admin.ch/bav/en/home.html Federal Office of Transportation] (FOT) was tasked with the realization of the National Access Point (NAP) for Switzerland, called the “[https://opentransportdata.swiss/en/ Open data platform mobility Switzerland]” (ODMCH). Additionally, a national open non-discriminatory trip planner has been made available named after its interface standard “Open Journey Planner” (OJP-System). A demo is available [https://opentdatach.github.io/ojp-demo-app/search here].

It is important to note, that the presented data covers primarily conventional public transport of all of Switzerland. The goal is to extend to other forms of transport, too. All street related data is handled by the [https://www.astra.admin.ch/astra/en/home.html Federal Roads Office in Switzerland] (FEDRO), while all geographical and topological information is gathered by the Federal Office of Topography ([https://www.swisstopo.admin.ch/en swisstopo]). Here we focus on the FOT related data.

Via these two channels, Switzerland provides the following data standards for Switzerland:
{| class="wikitable" style="width: 50%;"
|-
| style="text-align: center;" | Timetables
| [https://www.oev-info.ch/sites/default/files/2024-05/NeTEx_Core-Realisation_Guide_TP_Suisse-v1.00.pdf NeTEx – Swiss Profile]

[https://www.oev-info.ch/sites/default/files/2024-04/gtfs_profil_switzerland_version_0_16_en.pdf GTFS – Swiss Profile]

[https://www.oev-info.ch/sites/default/files/2023-07/hrdf_2_0_5_e.pdf HRDF – Swiss Profile]
|-
| style="text-align: center;" | On demand
| [https://www.oev-info.ch/sites/default/files/2024-07/Fachkonzept%20On-Demand_v2.1_en.pdf NeTEx]

[https://www.oev-info.ch/sites/default/files/2024-04/gtfs_profil_switzerland_version_0_16_en.pdf GTFS Flex]
|-
| style="text-align: center;" | Realtime data
| [https://www.oev-info.ch/sites/default/files/2023-04/siri_realisation-guide_pt_ch_v0.9.0.pdf SIRI-ET/PT – Swiss Profile]

[https://www.oev-info.ch/sites/default/files/2024-04/gtfs_profil_switzerland_version_0_16_en.pdf GTFS Realtime – Swiss Profile]
|-
| style="text-align: center;" | Events
| [https://www.oev-info.ch/sites/default/files/2024-07/realization_guide_siri-sx_oev_schweiz_v1.0.pdf SIRI-SX – Swiss Profile]

[https://www.oev-info.ch/sites/default/files/2024-04/gtfs_profil_switzerland_version_0_16_en.pdf GTFS Service Alerts]
|-
| style="text-align: center;" | Routing
| OJP 1.0 – Swiss Profile ([https://www.oev-info.ch/sites/default/files/2023-05/open_journey_planner_ojp_de_v1_eng.pdf Documentation], [https://opentransportdata.swiss/de/dataset/ojp2020 API])

OJP 2.0 – Swiss Profile (Documentation: Work In Progress, [https://opentransportdata.swiss/de/dataset/ojp2-0 API])
|-
| style="text-align: center;" | Fares
| OJP-Fare – Swiss Profile ([https://opentransportdata.swiss/en/cookbook/beta-price-information-with-ojp-fares-2/ Documentation], [https://opentransportdata.swiss/de/dataset/ojpfare API])
|}

== Use cases ==

=== Description ===
NeTEx is not used by (public) transport operators in Switzerland. The export is primarily used by the neighbouring countries and their larger transport operators (e.g., SNCF in France). The reason being its complexity (you need experts to understand and apply it) and multiplicity (substitution classes and similar constructs make simple adaptations difficult). Data exchange for timetables is mostly done by HRDF:

SIRI-SX is being actively used to represent disruptions, while SIRI-ET and -PT have only recently been introduced and are not widely adapted (currently VDV 454 and 453 are used mainly).

The GTFS standards are used most by small and medium-sized mobility providers.

The OJP standard is being increasingly adapted by transport operators, alongside the use of the routing service. With the recent introduction of OJP 2.0 we expect another increase.

=== Architecture ===
The following Figure provides an overview of the public transport data being centrally provided and processed for the various previously introduced data categories.

Short translation:

* Ereignisdaten = event data
* Echtzeitdaten = realtime data
* Fahrplandaten = timetable data
* Stammdaten = master data
* Datendrehscheibe = data exchange hub

[[File:Swiss architecture.png|center|thumb|674x674px]]

=== Use cases ===
The provided data is used for all public transport customer information systems in Switzerland.

Furthermore, a set of showcases created with the ODMCH data can be found [https://opentransportdata.swiss/de/showcase-5/ here]:

=== Outcome ===
The easier the standards are to use and to adapt, the more they are accepted and used by transport operators and mobility service providers.

Draft:Slovenia

2024-10-08T12:55:25Z

Admin: Admin moved page Draft:Slovenia to Slovenia

#REDIRECT [[Slovenia]]

Slovenia

2024-10-08T12:55:25Z

Admin: Admin moved page Draft:Slovenia to Slovenia

== Overview in the National Level ==
Adoption and implementation of standards for digital mobility ecosystems in Slovenia is driven by the requirements of the EU Delegated Regulations for the provision of multi-modal travel information (DU 2017/1926 and DU 2024/490) and the established technical specifications to ensure the efficient exchange of data between data owners, data suppliers, data aggregators, mobility data publishers and travel information service providers. National Access Point (NAP, nap.si) serves as a technical platform aimed to obtain, analyse, process, manage and publish data for end users and product developers at the NAP.

The governance of the NAP is responsibility of the National Traffic Management Centre (NCUP, ncup.si), as part of the Ministry of Infrastructure.

As part of the national NCUP-2 project Transmodel based technical standards NeTEx and SIRI are implemented.

== Use cases ==
Under the coordination of the NCUP following national developments are related to this report:

# Establishment of IT services for the implementation of the NeTEx National Profile
# Implementation of dynamic multimodal data according to the SIRI standard specification
# Slovenian Multimodal Journey Planner: SiMO

=== Description ===
All projects mentioned in this report have national (Slovenian) coverage. The NAP integrates all relevant data in terms of transport infrastructure (roads, rail, seaway) and service providers (public transport operators, mobility data service providers) with all modalities nationwide. Recent developments also emphasize standardized data collection for private modes like cycling and alternative modes like car-pooling where NeTEx, SIRI and DATEXII are being identified as best candidates.

=== Architecture ===
The IT architecture of the above mentioned projects 1, 2 and 3 can be can be summarised in the following data pipeline (see the diagram on Figure 1) It shows the flow of multimodal mobility data from data owners that can use intermediary data suppliers providing input for NCUP as the main data aggregator. The aggregated data is then prepared for utilization at NAP. The NAP data can be further processed by different travel and mobility information services providers.
[[File:Digital mobility data ecosystem at NCUP Slovenia.png|center|thumb|568x568px|Digital mobility data ecosystem at NCUP]]

=== Use cases ===
In the section the three projects related to NeTEx, SIRI and OJP are described

==== National NeTEx profile ====
In July 2021 the Slovenian National Profile for NeTEx v 1.0 was specified based on the standardised NeTEx EPIP (SIST-TS CEN/TS 16614-4:2020, NeTEx - Part 4: Passenger Information European Profile). In August 2024 preparation of the Slovenian National Profile for NeTEx v 2.0 started. Requirements for the task are to upgrade the profile by checking its compliance with the EU Delegated Regulations for the provision of multi-modal travel information (DU 2017/1926 and DU 2024/490).

==== SIRI implementation ====
In 2023, the SIRI implementation from 2020 was upgraded. The SIRI web service is installed within the NCUP's digital mobility ecosystem. The web service module for preparation of the SIRI files was upgraded to add static timetable data (from NeTEx) to the dynamic vehicle location data that operate within the national integrated public transport system (IJPP). The SIRI web service retrieves the references of the following NeTEx timetable objects: LineRef, PublishedLineName, VehicleJourneyRef, VehicleJourneyName, JourneyPatternRef, JourneyPatternName, RouteRef, OperatorRef, JourneyParts.

The current situation after the implementation of the project in 2023 is shown in Figure 1, where it can be seen that the SIRI modules have been installed throughout the entire information pipeline, from the data owners and suppliers (for the time being the IJPP system), to the data aggregator NCUP, and the national access point NAP.si.

==== SIMO.si ====
The Slovenian Multimodal Journey Planner (SiMO - Slovenian mobility, simo.si, Figure 1) is a national solution for improved sustainable travel choices based on reliable and accurate data.

Managed by the NCUP, and supported by data from our NAP, SiMO offers comprehensive route planning that integrates various modes of transport – personal, scheduled, and demand-based – into a single, user-friendly platform. SiMO eliminates fragmented information by gathering all travel options in one service, enabling users to explore, compare, and better plan their journeys. Accurate schedules, real-time updates on routes, equipment and accessibility information improve the travel experience, with delays, disruption and exceptional circumstances being reported to users, as incidents, roadworks or severe weather warnings.

=== Outcome ===
The Transmodel family of standardised technical specifications (NeTEx, SIRI, OJP) is well used in the Slovenian multimodal services reality. The initial implementations started in 2020 and are now being upgraded to latest requirements in the EU Delegated regulations. Until the end of 2024 the developments are expected to improve the multimodal mobility services experience in Slovenia.

Additionally, synergies with other ITS projects are created, such as implementation of the C-ITS (benefiting from SIRI), Traffic GIS (benefiting from NeTEx), etc.

Draft:Sweden

2024-10-08T12:54:51Z

Admin: Admin moved page Draft:Sweden to Sweden

#REDIRECT [[Sweden]]

Sweden

2024-10-08T12:54:51Z

Admin: Admin moved page Draft:Sweden to Sweden

==Overview in the National Level==
The National project “Open Data” has been the foundation in implementing NeTEx and SIRI (Nordic Profile) in accordance with MMTIS in Sweden. The solution consists of an integration platform (STIP) where national imported Public Transport data in Noptis DOI/DII (Static data) and Noptis ROI (Realtime data) as well as Transport and MPK – proprietary formats, is translated into NeTEx and SIRI (as well as GTFS and GTFS-R). The translated data is published at the NAP (Trafiklab.se) and used within the National ticketing Distribution System as well as various traffic information services such as Skånetrafikens OTP2 (Open Trip Planner).

==Use cases ==

There are two main use cases in Sweden where Transmodel based standards are implemented and used.

#'''National ticket Distribution System, Sweden''' (all PTA´s and PTO´s). New national ticketing distribution based on booking standard OSDM with traffic data in NeTEx format. Sweden is the first in Europe with a distributed ecosystem connected to multiple booking systems. The system is built on the open and international booking standard OSDM-Online, developed by the International Union of Railways (UIC). The system is fed with Public Transport data based on NeTEx (Nordic Profile). With this competition-neutral standards as a foundation, all producers in both Sweden and Europe have the opportunity to connect. Consequently, the system will have multiple booking systems linked to it. The system is being developed in collaboration with Turnit, an Estonian company with experience in standards within the railway industry in Europe.
#'''Open Trip Planner Skåne, Sweden'''. New trip planner developed on open standard OTP2 for regional travelling and cross boarder travelling purposes. Skåne is the 3rd largest region (PTA) in Sweden with Public Transport including city buses (incl. BRT) and regional trains.

===Architecture===

==== National ticket Distribution System ====
The new '''National ticket Distribution System, Sweden''' infrastructure creates favorable conditions for the continued development of the ticket collaboration Resplus. The service will also enable more secure and widely validatable tickets when implemented. This, in turn, will contribute to increased safety and secured revenue. The system is being developed in collaboration with Turnit, an Estonian company with experience in standards within the railway industry in Europe. The new infrastructure is built on four essential components, with communication between these components based on the international and open OSDM-Online standard (Open Sales and Distribution Model).
# A "data warehouse" where the majority of Samtrafiken's partners will store their ticket products. This is where the offerings of transportation companies are entered, and it is from here that the service retrieves the inventory.
# The sales tool Samtrafiken TRAID and a sales API. In TRAID, retailers can directly book journeys, suitable for those retailers with a need for manual sales management (such as kiosks, stores, or call centers) or as a complement to web sales. Retailers and producers wishing to sell through their own sales tools (such as websites or apps) can choose to access the inventory via API.
# Travel search for all saleable ground-based collective transport.
# A central service, a so-called distribution hub, which retrieves, combines, and distributes ticket products from both Samtrafiken's data warehouse and external data warehouses for partners with their booking systems.

==== Open Trip Planner Skåne ====
'''The Skåne OpenTripPlanner''' (OTP2) is a server-side Java application that is primarily designed to interpret and combine map, transit service, and other mobility data sets, providing API endpoints that receive user origins and destinations and return trip plans to other applications along with vector map tiles, stop departures, and other rider information. In other words, OTP is a backend application that can work with other frontend user interfaces. OTP is an open standard and works with your website, mobile app, physical signage or other applications in order to provide relevant customer information and meaningful trip plans to riders.

=== Outcome ===
The '''National ticket Distribution System''' and '''Open Trip Planner Skåne OTP2''' are implemented and in operation with minor operational problems to fix as well as ongoing further developments. Both implementations are built on open and international standards provided with Public Transport data like NeTEx and Siri. With this competition-neutral standards as a foundation, all producers in both Sweden and Europe have the opportunity to connect. This provides significant benefits for travelers, making it easier to access, plan, and book train journeys with multiple transport operators, including competing companies, both in national and reginal level as well as to/from Europe.

Draft:France

2024-10-08T12:54:24Z

Admin: Admin moved page Draft:France to France

#REDIRECT [[France]]

France

2024-10-08T12:54:24Z

Admin: Admin moved page Draft:France to France

== Overview in the National Level ==

=== Current Situation ===
Many datasets based on NeTEx and SIRI standard are available in [https://transport.data.gouv.fr/?locale=en French National Access Point] .
* '''Mass transit''': 114 datasets in NeTEx – French Profile format are available (excluding tariff and accessibility data) out of 421 total mass transit datasets.
* '''Mass transit (Real-time)''': 25 SIRI datasets are available compared to 159 GTFS-RT datasets.
* '''Pedestrian accessibility''': 2 datasets in NeTEx – French Profile format have been provided.

=== Upcoming Developments ===
For several months, towns and regions have been collecting accessibility-related data and plan to publish it in NeTEx – French Profile. A decree issued in May has strengthened the collection of this data.

In connection with the single-ticketing experiment, the French NAP team is assisting data producers, particularly in 2 regions, in providing their tariff data in NeTEx – French Profile.

More NeTEx and SIRI mass transit datasets are expected to be published in the coming months, as stakeholders are now ready to produce them. The French NAP team is actively supporting these efforts.

A French Profile for new mobility modes (such as free-floating services) is currently in development, although the release date is still unknown.

The French NAP is also working on implementing a NeTEx validation tool to help providers comply with the standard.

== Use cases ==

=== Description ===
More information regarding the implementation of public transport standards can be found at the following link: [https://transport.data.gouv.fr/stats#public-transport-format Public Transport Format Statistics]. This includes data from regions such as '''Nouvelle-Aquitaine''', '''Pays de la Loire''', and '''Île-de-France'''.

In '''Paris''' and some surrounding towns, NeTEx accessibility datasets have been provided through an experimental project that involved converting data from OpenStreetMap into the NeTEx format. Further details on this initiative can be found here: [https://transport.data.gouv.fr/datasets?q=jungle+bus Jungle Bus Datasets].

European regulations require transport authorities to provide datasets in the NeTEx format. As a result, an increasing number of local authorities and digital service providers recognize the utility of this standard, especially for establishing a multimodal information system. French law mandates that these multimodal systems must cover every region in the country.

Despite the growing acceptance of NeTEx, many transport authorities and private transport operators find the standard to be overly complex. While some digital service providers have mastered certain aspects of NeTEx, the intricate nature of the standard presents challenges for broader adoption.

To support the transition, the French Ministry of Transport has invested in developing specific tools that assist producers in collecting accessibility data and publishing it in the NeTEx format. This financial backing aims to simplify the process and encourage compliance with the standard among local authorities.

=== Architecture ===
The implementation of public transport standards follows the guidelines set forth in the French Profile, which can be accessed [https://normes.transport.data.gouv.fr/ here]. This profile is compatible with the EPIP (Échange de données pour l'Information et la Planification des Transports) standard, ensuring that data exchanges meet established interoperability requirements.

=== Implementation ===
Many transport authorities use SIRI for their own purposes, although the exact extent of this usage is unclear. The multimodal information system in '''Nouvelle-Aquitaine''' (Modalis) utilizes NeTEx, or there are plans to implement it. Similarly, '''Île-de-France''' (IDFM) is also expected to adopt NeTEx for its multimodal information system.

=== Outcome ===
Currently, it is too early to observe the benefits of the NeTEx implementation, as the process is still ongoing.

In the future, there are expectations for two key improvements:

# The availability of more detailed information, including tariffs and accessibility of locations;
# Datasets with a higher level of quality.

However, it is likely that in the coming years, a gap will emerge between the most advanced transport authorities and operators and those that are less advanced in their implementation of the NeTEx standard and multimodal information systems.

Draft:Belgium

2024-10-08T12:53:52Z

Admin: Admin moved page Draft:Belgium to Belgium

#REDIRECT [[Belgium]]

Belgium

2024-10-08T12:53:52Z

Admin: Admin moved page Draft:Belgium to Belgium

In Belgium, a national NeTEx profile has been defined, but it is currently not utilized by the Public Transport Operators (PTOs). Instead, there are existing NeTEx datasets available on the NAP in accordance with EU requirements, using EPIP. A converter has been employed to ensure compliance with these regulations. Recently, the Belgian PTOs have decided to adopt EPIP/EPIAP/EPIP-RT as their shared EU-compliant NeTEx/SIRI profiles. Work on producing and implementing these profiles is set to begin in autumn 2024.

MediaWiki:Sidebar

2024-09-25T13:55:40Z

Admin:

Draft:Italy

2024-09-25T12:39:27Z

Admin: Admin moved page Draft:Italy to Italy

#REDIRECT [[Italy]]

Italy

2024-09-25T12:39:27Z

Admin: Admin moved page Draft:Italy to Italy

{{DISPLAYTITLE:Country:Italy}}

= Overview in the National Level =

=== Italian NeTEx Profile ===
For the exchange of Public Transport (PT) data with Italian National Access Point (NAP), a NeTEx Profile has been defined among the affected stakeholders.

The profile is a subset of the standard; it has been defined selecting the needed concepts (entities and associated attributes) for specific use cases or set of use cases and complemented by rules defined to restrict possibilities of divergent interpretations of open parts of the standard.

The Italian NeTEx profile is structured in 5 levels, with the minimum objective of being able to have a protocol useful to transport of all the data categories required by the Del. Reg. 1926. It is currently used by stakeholders, few of them implemented the whole stack.
[[File:NeTEx Italian Profile.png|center|thumb|''Italian NeTEx Profile structure'']]

==== Passenger Information Profile (Level 1) ====

For the level 1 of the Italian NeTEx Profile, European Passenger Information Profile (EPIP) has been adopted as defined in the CEN Technical Specification CEN/TS 16614-4:2021.

Typical Passenger ''Information’s'' Use Cases are:

* provision of operativity calendars and timetables
* provision of network topology and routes
* provision of transport operators
* provision of access nodes to stop places

Main data categories exchanged are:

* Network topology:
** Stop
** Access nodes to the transport network
** Node geometry

* Timetables
* Validity calendars
* Lines
* Transport Operators

==== Contracts profile (Level 2) ====
For Contracts, Use Cases are:

* provision of Contract / Journey Accounting (with operator roles)
* provision of Stop Points Facilities (ticketing, accessibility, safety, etc.)
* provision of Vehicles Equipment (lift/ramps, wheelchair, etc.)

The level 2 of the Italian NeTEx Profile is defined upon the first level of European Passenger Information Profile (EPIP).

Main data categories exchanged are:

* Vehicle equipment (BUS, Trams, Trains):
** Characteristics (chassis, serial number, carriages, etc.)
** Capacity (no. of seats)
** Installed devices
** Services on board (WiFi, etc.)
* Parking:
** PK in structure
** Park&Ride
* Service contracts

==== Fare (Level 3) ====
This level contains the structures to exchange data relevant tariffs and Fare products.

Main data categories exchanged are:

* Points of sale (TPL):
** Tickets for scheduled transport/on request
** Parking tickets
** Ticket offices
** Digital sales platforms
* Tariffs (TPL):
** Fare zones/bands/stops (O/D matrices, etc.)
** Standard fare structures (point-to-point, fixed, etc.)
* Classes of passengers (adults, children, students, elderly, disabled, etc.)
* Standard and special pricing products (offers, etc.)

==== Alternative Modes (Level 4) ====
This level deals with data relevant to sharing and micromobility.

Main data categories exchanged are:

* Network topology:
** Operational area of the service
** Sharing stations
** TAXI stations
** Electric charging stations
* Parking: Secure parking spaces for bicycles
* Booking (sharing): Digital platforms
* Points of sale (sharing): Digital sales platforms
* Tariffs (sharing): Pricing structure

==== Accessibility (Level 5) ====
With this level of NeTEx profile is possible to exchange data relevant accessibility of PT Service. For the level 5 of the Italian NeTEx Profile, European Passenger Information Accessibility Profile (EPIAP) has been adopted as defined in the CEN Technical Specification CEN/TS 16614-6:2024.

Main data categories exchanged are:

* Accessibility of the transport network:
** Access nodes
** Internal routes in interchanges (e.g. elevators, escalators)
* Existence of user assistance services

=== Italian SIRI Profile ===
For the exchange of Public Transport (PT) dynamic data with Italian National Access Point (NAP), a SIRI Profile has been defined among the affected stakeholders.
[[File:SIRI Italian Profile.png|center|thumb|Italian SIRI Profile structure]]

The Italian SIRI Profile has been defined, basically EPIP-RT has been adopted. It includes following have been selected:

* '''SIRI-ET''': Estimated Timetable service: this function is defined by siri_estimatedTimetable_service.xsd and transfers vehicle passing times at stops already reached. In SIRI “2.1” for each stopping points, boarding and alighting passengers number are recorded.
* '''SIRI-VM''': Vehicle Monitoring service: this function is defined by siri_vehicleMonitoring_service.xsd and transfers real-time vehicle positions and/or stop point arrival/passing times with forecasts on next stopping points.
* '''SIRI-SX''': Situation Exchange service: this function is defined by siri_situationExchange_service.xsd and transfers events affecting regular PT service.
* '''SIRI-FM''': Facility Monitoring service: exchange real-time status of facilities at a stop (lifts, escalators, etc.)

=== NAP MMTIS ===
The Italian NeTEx profile is used to exchange with the NAP MMTIS (National Access Point Multi-Modal Travel Information Services) the transport information collected at regional level through collectors named RAP (Regional Access Points) and National Transport Operators. The following figure shows the architecture of this implementation:
[[File:Italian NAP MMTIS.png|center|thumb|600x600px|Italian NAP MMTIS architecture]]
National architecture design and implementation has been completed, it foresees the creation of an intermediate level between PTOs and NAP, called Regional Access Point (RAP), that will be one for each Italian region and will be managed by local PTAs or mobility agencies.

Implementation of this technical architecture implies also formalization through the signature of specific MOU, of relationships and responsibilities concerning data gathering and exchange of all stakeholders: PTOs, PTAs, Agencies and System Integrators

= Use cases =

== Bolzano, STA (Südtiroler Transportstrukturen)==

STA (Südtiroler Transportstrukturen), is the in-house company working on behalf of the Public Transport Authority in Bolzano.

STA is positioned in a unique location, is part of Italy but very close to Austria and the majority of the people speaks German. This means that the travel information STA offers (such as bus stop names) has to be multilingual. Therefore, there were needing a standard which allows them to exchange this kind of information considering the multilingual data. NeTEx provided this opportunity.

[[File:STA 1.jpg|center|thumb|500x500px]]
[[File:STA 2.png|center|thumb|500x500px]]
=== System Architecture ===

STA opted to implement NeTEx and SIRI ‘natively’, meaning there is no conversion between the production of the data and NeTEx data files from another exchange data format. Considering the complex modelling that is needed to represent the physical environment of public transport, the complete standards NeTEx and SIRI were decided as more suitable.
[[File:STA 3.png|center|thumb|500x500px|Challenges]]Based on the new architecture, NeTEx - SIRI, and other relevant standards, are implemented for the exchange of planned and real time data between back end systems (like operational planning tool ticketing system, travel planner and others. This architecture and the introduction of those standards is seen as the sustainable solution that can accommodate future developments on for example MaaS and integrated ticketing systems.
[[File:SA 1.png|center|thumb|731x731px]]
[[File:SA 2.png|center|thumb|500x500px]]

=== Implementation ===
In particular this architecture was chosen to support also "LinkingAlps", one of the EU projects in which it is developed a decentralised network of travel information services. This network will be created by interlinking existing regional or national journey planner services from all neighbour countries, with focus on multimodal transport (public transport, railways, new modes) through a standardised exchange service. In this context, the exchange of complete and interoperable datasets is key.

=== Outcome ===
To be completed.

{{DEFAULTSORT:Country:Italy}}

Italy

2024-03-29T14:36:25Z

Admin: Created page with "in progress"

in progress

MediaWiki:Sidebar

2024-03-29T14:33:24Z

Admin:

National implementations

2024-03-29T14:31:45Z

Admin: Redirected page to National Implementations

#REDIRECT [[National Implementations]]

MediaWiki:Sidebar

2024-03-29T14:30:21Z

Admin:

MediaWiki:Sidebar

2024-03-29T14:29:47Z

Admin:

MediaWiki:Sidebar

2024-03-29T14:28:40Z

Admin:

MediaWiki:Sidebar

2024-03-29T14:27:35Z

Admin:

National implementations

2024-03-28T14:23:57Z

Admin: Created page with "= NeTEx national and EU minimum profiles inventory 🌐 = A number of national and transnational profiles have already been defined for different European countries, while th..."

= NeTEx national and EU minimum profiles inventory 🌐 =

A number of national and transnational profiles have already been defined for different European countries, while there are new profiles under development. In the following tables, DATA4PT provides an overview of the '''key characteristics of the national profiles per country''', including the data categories that are currently covered. The tables will be continuously updated following new implementations.

== Published profiles ==

{| class="wikitable" style="width : 60%"
|-
! width="150px"| Profile Name !! width="100px"| NeTEx EPIP Based* !! width="100px" | NeTEx EPIP Compatible** !! width="300px" | Documentation
|-
| Austria (AT) || style="text-align:center;" |✅ || || [https://mobilitaetsverbuende.atlassian.net/wiki/spaces/NET/overview Austrian profile]
|-
| Denmark (DK) ||style="text-align:center;" | ✅ || || [https://www.trafikstyrelsen.dk/Media/638013312835439194/Vejledning%20om%20brug%20af%20NeTEx.pdf Denmark profile] - [https://www.trafikstyrelsen.dk/arbejdsomraader/kollektiv-trafik/statistik-og-data/krav-til-udstilling-af-data-til-rejseplanlaegning NAP in Denmark]
|-
| France (FR) || || style="text-align:center;" |✅ || [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 profil] - [http://www.normes-donnees-tc.org/wp-content/uploads/2014/05/NF_Profil_NeTEx_pour_les_arrets-_F-_-_v2.pdf Stop Profile] - [http://www.normes-donnees-tc.org/wp-content/uploads/2019/11/NF_Profil-NeTEx-pour-les-R%C3%A9seauxF-v2.1.pdf Network Profil] - [http://www.normes-donnees-tc.org/wp-content/uploads/2019/11/NF+Profil-NeTEx-pour-les-HorairesF-v2.1.pdf Timetable profile] - [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]
|-
| Italy (IT) ||style="text-align:center;" | ✅ ||
|[https://netex-cen.eu/implementation/italian-implementation/ Italian profile]
|-
| Netherlands (NL) ||style="text-align:center;" | ✅ || || [https://bison.dova.nu/standaarden/nederlands-netex-profiel Netherlands profile] - [https://bison.dova.nu/sites/default/files/bison_prijzen_producten_en_tarieven_v8.1.3.0_release.pdf Bison Fares]
|-
| Nordic (Norway, Sweden, Finland, Denmark) || ||style="text-align:center;" | ✅ || [https://enturas.atlassian.net/wiki/spaces/PUBLIC/pages/728891481/Nordic+NeTEx+Profile Nordic profile]
|-
| Portugal (PT) || || || [https://ptprofiles.azurewebsites.net/netex-profile Portuguese profile]
|-
| Slovenija (SI) || || style="text-align:center |✅ || [https://www.nap.si/_resources/profiles/NeTEx_SI_Profile_v2.pdf Slovenian profile]
|-
| UK (GB) || || style="text-align:center |✅ || [http://netex.uk/farexchange/ UK profile] - [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 Stop and Timetables] - [http://netex.uk/farexchange/doc/uk_profile/DfT-NeTEx-3-Fares_Spec-2019.06.17-v0.17.pdf Fares]
|-
| Ireland (IE) || || || [https://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]
|-
|Czech Republic (CZ)
|✅
|
|
|}
<nowiki>*</nowiki>Profiles of this category have been specified based on EU Minimum profile.

<nowiki>**</nowiki> Profiles of this category have been specified before the definition of EU Minimum profile but they have been formed the basis for its specification.

== Data categories ==

''Data categories are identified based on [https://eur-lex.europa.eu/eli/reg_del/2017/1926/oj MMTIS EU Regulation 1926/2017]''
{| class="mw-collapsible mw-collapsed wikitable" style="width:50%"
|+ style="white-space:nowrap; border:1px solid; padding:3px;" | Data categories table.
|-
! Level of service (LOS) !! Static data
|-
| colspan="2" style="text-align:center |'''Static data - Level of service 1 (LOS 1 )'''
|-
| LOS 1-1 || Address identifiers (building number, street name, postcode)
|-
| LOS 1-2 || Topographic places (city, town, village, suburb, administrative unit)
|-
| LOS 1-3 || Points of interest (related to transport information) to which people may wish to travel
|-
| LOS 1-4 || Operational Calendar, mapping day types to calendar dates
|-
| LOS 1-5 || Identified access nodes (all scheduled modes)
|-
| LOS 1-6 || Geometry/map layout structure of access nodes (all scheduled modes)
|-
| LOS 1-7 || Connection links where interchanges may be made, default transfer times between modes at interchanges
|-
| LOS 1-8 || Network topology and routes/lines (topology)
|-
| LOS 1-9 || Transport operators
|-
| LOS 1-10 || Timetables
|-
| LOS 1-11 || Planned interchanges between guaranteed scheduled services
|-
| LOS 1-12 || Hours of operation
|-
| LOS 1-13 || Vehicles (low floor; wheelchair accessible.)
|-
| LOS 1-14 || Accessibility of access nodes, and paths within an interchange (such as existence of lifts, escalators)
|-
| LOS 1-15 || Existence of assistance services (such as existence of on-site assistance)
|-
| LOS 1-16 || Road network
|-
| LOS 1-17 || Cycle network (segregated cycle lanes, on-road shared with vehicles, on-path shared with pedestrians)
|-
| LOS 1-18 || Pedestrian network and accessibility facilities
|-
| || Framework data
|-
|-
| colspan="2" style="text-align:center |'''Static data - Level of service 2 (LOS 2)'''
|-
| LOS 2-1 || Park & Ride stops
|-
| LOS 2-2 || Bike sharing stations
|-
| LOS 2-3 || Car-sharing stations
|-
| LOS 2-4 || Publicly accessible refueling stations for petrol, diesel, CNG/LNG, hydrogen powered vehicles, charging stations for electric vehicles
|-
| LOS 2-5 || Secure bike parking (such as locked bike garages)
|-
| LOS 2-6 || Information service
|-
| 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, fulfillment methods, payment methods)
|-
| LOS 2-8 || Trip plans, auxiliary information, availability check
|-
| LOS 2-9 || Basic common standard fares (all scheduled modes)
|-
| LOS 2-10|| Fare network data (fare zones/stops and fare stages)
|-
| LOS 2-11|| Standard fare structures (point to point including daily and weekly fares, zonal fares, flat fares)
|-
| LOS 2-12|| Vehicle facilities such as classes of carriage, on-board Wi-Fi.
|-
| colspan="2" style="text-align:center |'''Static data - Level of service 3 (LOS 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.)
|-
| 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)
|-
| 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
|-
| LOS 3-4 || 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.
|-
| LOS 3-5 || How to pay tolls (incl. retail channels, fulfillment methods, payment methods)
|-
| LOS 3-6 || How to book car sharing, taxis, cycle hire etc. (incl. retail channels, fulfillment methods, payment methods)
|-
| LOS 3-7 || Where how to pay for car parking, public charging stations for electric vehicles and refueling points for CNG/LNG, hydrogen, petrol and diesel powered vehicles (incl. retail channels, fulfillment methods, payment methods)
|-
| LOS 3-8 || 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)
|-
| LOS 3-9 || Parameters needed to calculate an environmental factor such as carbon per vehicle type or passenger mile or per distance walked
|-
| LOS 3-10 || Parameters such as fuel consumption needed to calculate cost
|-
| LOS 3-11 || Estimated travel times by day type and time-band by transport mode/combination of transport modes
|-
|}

== Static data - Level of service 1 (LOS 1) ==

{| class="wikitable" style="width:70%"
|-
! width="80px"| Data Categories
! width="80px" style="text-align:center | EPIP
! width="80px"| AT
! width="80px"| DK
! width="80px"|FR
! width="80px"|IT
! width="80px"|NL
! width="150px" | Nordic (SE, NOR, DK, FIN)
! width="80px"|PT
! width="80px"| SI
! width="80px"|GB
|-
| [[#Data categories|LOS 1-1]] || || || || style="text-align:center |✅ || || || style="text-align:center |✅ || ||style="text-align:center | ✅ ||
|-
|[[#Data categories|LOS 1-2]] || || || || style="text-align:center |✅ || || ||style="text-align:center | ✅ || || style="text-align:center |✅ ||style="text-align:center | ✅
|-
|[[#Data categories|LOS 1-3]] || || || || style="text-align:center |✅ || || ||style="text-align:center | ✅ || ||style="text-align:center | ✅ ||
|-
|[[#Data categories|LOS 1-4]] || ||style="text-align:center | ✅ ||style="text-align:center | ✅ || style="text-align:center |✅ || || style="text-align:center |✅ || style="text-align:center |✅ || || style="text-align:center |✅ ||style="text-align:center | ✅
|-
|[[#Data categories|LOS 1-5]] || ||style="text-align:center | ✅ ||style="text-align:center | ✅ || style="text-align:center |✅ || ||style="text-align:center | ✅ || style="text-align:center |✅ || ||style="text-align:center | ✅ ||
|-
|[[#Data categories|LOS 1-6]] || ||style="text-align:center | ✅ || || style="text-align:center |✅ || || style="text-align:center |✅ ||style="text-align:center | ✅ || || style="text-align:center |✅ ||
|-
|[[#Data categories|LOS 1-7]] || ||style="text-align:center | ✅ || ||style="text-align:center | ✅ || || ||style="text-align:center | ✅ || || style="text-align:center |✅ || style="text-align:center |✅
|-
|[[#Data categories|LOS 1-8]] ||style="text-align:center | ✅ ||style="text-align:center | ✅ || style="text-align:center |✅ ||style="text-align:center | ✅ || style="text-align:center |✅ || style="text-align:center |✅ ||style="text-align:center | ✅ || style="text-align:center |✅ || style="text-align:center |✅ || style="text-align:center |✅
|-
|[[#Data categories|LOS 1-9]] || style="text-align:center |✅ ||style="text-align:center | ✅ || style="text-align:center |✅ ||style="text-align:center | ✅ || style="text-align:center |✅ || style="text-align:center |✅ || ||style="text-align:center | ✅ ||style="text-align:center | ✅ || style="text-align:center |✅
|-
|[[#Data categories|LOS 1-10]] ||style="text-align:center | ✅ || style="text-align:center |✅ ||style="text-align:center | ✅ ||style="text-align:center | ✅ || style="text-align:center |✅ || style="text-align:center |✅ || style="text-align:center |✅ || style="text-align:center |✅ || style="text-align:center |✅ || style="text-align:center |✅
|-
|[[#Data categories|LOS 1-11]] || ||style="text-align:center | ✅ || not existent || style="text-align:center |✅ || || style="text-align:center |✅ || style="text-align:center | For connection links we use journey planner based on OSM map data, road, cycle, and pedestrian network is based on OpenStreetMap || ||style="text-align:center | ✅ ||style="text-align:center | ✅
|-
|[[#Data categories|LOS 1-12]] || || style="text-align:center |✅ || style="text-align:center |✅ || style="text-align:center |✅ || || || style="text-align:center |✅ || ||style="text-align:center | ✅ ||
|-
|[[#Data categories|LOS 1-13]] || || style="text-align:center |✅ || style="text-align:center |✅ || style="text-align:center |✅ || || style="text-align:center |✅ || style="text-align:center |✅ || || style="text-align:center |✅ ||
|-
|[[#Data categories|LOS 1-14]] || || style="text-align:center |✅ || style="text-align:center |✅ || style="text-align:center |✅ || || || style="text-align:center |✅ || || style="text-align:center |✅ ||
|-
|[[#Data categories|LOS 1-15]] || || || style="text-align:center |✅ ||style="text-align:center | ✅ || || ||style="text-align:center | ✅ || || style="text-align:center |✅ ||
|-
|[[#Data categories|LOS 1-16]] || || || || style="text-align:center |✅ || || || style="text-align:center |✅ || || style="text-align:center |✅ ||
|-
|[[#Data categories|LOS 1-17]] || || || || style="text-align:center |✅ || || || style="text-align:center |✅ || || style="text-align:center |✅ ||
|-
|[[#Data categories|LOS 1-18]] || || || || style="text-align:center |✅ || || || style="text-align:center |✅ || ||style="text-align:center | ✅ ||
|-
|Framework data || || || || || || || || style="text-align:center |✅ || ||
|-
|}

== Static data - Level of service 2 (LOS 2) ==

{| class="wikitable" style="width:70%"
|-
!width="80px"| Data Categories
! width="80px" style="text-align:center | EPIP
! width="80px"| AT
! width="80px" | DK
! width="80px"|FR
! width="80px"|IT
! width="80px"|NL
! width="150px" | Nordic (SE, NOR, DK, FIN)
! width="80px"|PT
! width="80px"| SI
! width="80px"|GB
|-
|[[#Data categories|LOS 2-1]] || || ||style="text-align:center |✅ || style="text-align:center |✅ || || || style="text-align:center |✅ || || style="text-align:center | ✅ ||
|-
|[[#Data categories|LOS 2-2]] || || ||style="text-align:center |✅ || style="text-align:center |✅ || || || style="text-align:center | ✅ || || style="text-align:center | ✅ ||
|-
|[[#Data categories|LOS 2-3]] || || ||style="text-align:center |✅ ||style="text-align:center | ✅ || || || style="text-align:center |✅ || || style="text-align:center | ✅ ||
|-
|[[#Data categories|LOS 2-4]] || || || || || || ||style="text-align:center | Only charging stations for electric vehicles || || style="text-align:center |✅ ||
|-
|[[#Data categories|LOS 2-5]] || || || style="text-align:center |✅ ||style="text-align:center | ✅ || || ||style="text-align:center | ✅ || || style="text-align:center | ✅ ||
|-
|[[#Data categories|LOS 2-6]] || || || style="text-align:center | ✅ || style="text-align:center |✅ || || ||style="text-align:center | ✅ || || style="text-align:center |✅ ||
|-
|[[#Data categories|LOS 2-7]] || || || ||style="text-align:center |✅ || || || style="text-align:center | ✅ || || style="text-align:center | ✅ ||
|-
|[[#Data categories|LOS 2-8]] || || || ||style="text-align:center | ✅ || || ||style="text-align:center | ✅ || ||style="text-align:center | ✅ ||
|-
|[[#Data categories|LOS 2-9]] || || || || style="text-align:center | ✅ || || style="text-align:center | ✅ || style="text-align:center | ✅ || || style="text-align:center | ✅ || style="text-align:center |✅
|-
|[[#Data categories|LOS 2-10]] || || || || style="text-align:center | ✅ || || || style="text-align:center | ✅ || || style="text-align:center | ✅ || style="text-align:center |✅
|-
|[[#Data categories|LOS 2-11]] || || || ||style="text-align:center | ✅ || || || style="text-align:center | ✅ || || style="text-align:center | ✅ ||style="text-align:center | ✅
|-
|[[#Data categories|LOS 2-12]] || || ||style="text-align:center | ✅ || style="text-align:center | ✅ || || || style="text-align:center | ✅ || || style="text-align:center | ✅ || style="text-align:center |✅
|-
|}

== Static data - Level of service 3 (LOS 3) ==

{| class="wikitable" style="width:70%"
|-
! width="80px"| Data Categories
! width="80px" style="text-align:center | EPIP
! width="80px"| AT
! width="80px" | DK
! width="80px"|FR
! width="80px"|IT
! width="80px"|NL
! width="150px" | Nordic (SE, NOR, DK, FIN)
! width="80px"|PT
! width="80px"| SI
! width="80px"|GB
|-
|[[#Data categories|LOS 3-1]] || || || ||style="text-align:center | ✅ || || ||style="text-align:center | ✅ || || || style="text-align:center | ✅
|-
|[[#Data categories|LOS 3-2]] || || || || style="text-align:center |✅ || || || style="text-align:center | ✅ || || || style="text-align:center | ✅
|-
|[[#Data categories|LOS 3-3]] || || || ||style="text-align:center | ✅ || || || style="text-align:center |✅ || || || style="text-align:center | ✅
|-
|[[#Data categories|LOS 3-4]] || || || ||style="text-align:center | ✅ || || || style="text-align:center | ✅ || || ||
|-
|[[#Data categories|LOS 3-5]] || || || || style="text-align:center |✅ || || || || || ||
|-
|[[#Data categories|LOS 3-6]] || || || || || || || || || ||
|-
|[[#Data categories|LOS 3-7]] || || || ||style="text-align:center |✅ || || || || || ||
|-
|[[#Data categories|LOS 3-8]] || || || || || || || style="text-align:center |✅ || || ||
|-
|[[#Data categories|LOS 3-9]] || || || || || || || style="text-align:center | ✅ || || ||
|-
|[[#Data categories|LOS 3-10]] || || || || || || || style="text-align:center |✅ || || ||
|-
|[[#Data categories|LOS 3-11]] || || || || || || || style="text-align:center |✅ || || ||
|-
|}

⚠️ 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.

📄 You can also find contact details for some of the entities responsible for the profiles in the documentation list. Otherwise you can contact us in [https://data4pt-project.eu/requests-requirements/ DATA4PT].

MediaWiki:Sidebar

2024-03-28T14:22:57Z

Admin:

MediaWiki:Sidebar

2024-03-28T14:08:47Z

Admin:

Main Page

2023-10-08T19:35:09Z

Admin:

[[File:Data4PT logo flat.jpg|center|600px]]
<big>
= '''Welcome to the DATA4PT Wiki''' =
[[File:People Collaborating.png|right|400px]]

==Discover, Verify, Connect==
 
*'''Want to become aware of NAP and related standards?'''
[https://data4pt-project.eu/ Explore the DATA4PT project pages] and enjoy a wealth of knowledge!

*'''Need to verify your NeTEx data?'''
[https://greenlight.atomite.io/ Utilize our free validation tool] for accurate results!

*'''Require support?'''
Don't hesitate! [https://docs.google.com/forms/d/1xQD5pPrxOFvoQrheQ0jpnFtWR3oWdCy5DyUZBRvWr0c/viewform?edit_requested=true Fill in a support request], and we're here to help.

*'''Like to comment on the available pages in the "Discussion" tab?'''
We value your input! [https://docs.google.com/forms/d/1xQD5pPrxOFvoQrheQ0jpnFtWR3oWdCy5DyUZBRvWr0c/viewform?edit_requested=true Contact us] and share your thoughts.

*'''Wish to contribute and create new pages?'''
[https://docs.google.com/forms/d/1xQD5pPrxOFvoQrheQ0jpnFtWR3oWdCy5DyUZBRvWr0c/viewform?edit_requested=true Join our expert community] and be part of something great!

==Why DATA4PT?==

DATA4PT is your one-stop destination for public transportation data, standards, and collaboration. Whether you're a newcomer or an expert, we're here to support your journey.

Join us in shaping the future of public transportation data together!
</big>

Main Page

2023-10-08T19:34:03Z

Admin:

[[File:Data4PT logo flat.jpg|center|600px]]
= '''Welcome to the DATA4PT Wiki''' =
[[File:People Collaborating.png|right|400px]]

==Discover, Verify, Connect==
 
<big>
*'''Want to become aware of NAP and related standards?'''
[https://data4pt-project.eu/ Explore the DATA4PT project pages] and enjoy a wealth of knowledge!

*'''Need to verify your NeTEx data?'''
[https://greenlight.atomite.io/ Utilize our free validation tool] for accurate results!

*'''Require support?'''
Don't hesitate! [https://docs.google.com/forms/d/1xQD5pPrxOFvoQrheQ0jpnFtWR3oWdCy5DyUZBRvWr0c/viewform?edit_requested=true Fill in a support request], and we're here to help.

*'''Like to comment on the available pages in the "Discussion" tab?'''
We value your input! [https://docs.google.com/forms/d/1xQD5pPrxOFvoQrheQ0jpnFtWR3oWdCy5DyUZBRvWr0c/viewform?edit_requested=true Contact us] and share your thoughts.

*'''Wish to contribute and create new pages?'''
[https://docs.google.com/forms/d/1xQD5pPrxOFvoQrheQ0jpnFtWR3oWdCy5DyUZBRvWr0c/viewform?edit_requested=true Join our expert community] and be part of something great!
</big>
==Why DATA4PT?==

DATA4PT is your one-stop destination for public transportation data, standards, and collaboration. Whether you're a newcomer or an expert, we're here to support your journey.

Join us in shaping the future of public transportation data together!

Main Page

2023-10-08T19:15:59Z

Admin:

[[File:Data4PT logo flat.jpg|center|600px]]

= '''Welcome to the DATA4PT Wiki''' =
[[File:People Collaborating.png|right|400px]]

==Discover, Verify, Connect==
 
<big>
*'''Want to become aware of NAP and related standards?'''
[https://data4pt-project.eu/ Explore the DATA4PT project pages] and enjoy a wealth of knowledge!

*'''Need to verify your NeTEx data?'''
[https://greenlight.atomite.io/ Utilize our free validation tool] for accurate results!

*'''Require support?'''
Don't hesitate! [https://docs.google.com/forms/d/1xQD5pPrxOFvoQrheQ0jpnFtWR3oWdCy5DyUZBRvWr0c/viewform?edit_requested=true Fill in a support request], and we're here to help.

*'''Like to comment on the available pages in the "Discussion" tab?'''
We value your input! [https://docs.google.com/forms/d/1xQD5pPrxOFvoQrheQ0jpnFtWR3oWdCy5DyUZBRvWr0c/viewform?edit_requested=true Contact us] and share your thoughts.

*'''Wish to contribute and create new pages?'''
[https://docs.google.com/forms/d/1xQD5pPrxOFvoQrheQ0jpnFtWR3oWdCy5DyUZBRvWr0c/viewform?edit_requested=true Join our expert community] and be part of something great!
</big>
==Why DATA4PT?==

DATA4PT is your one-stop destination for public transportation data, standards, and collaboration. Whether you're a newcomer or an expert, we're here to support your journey.

Join us in shaping the future of public transportation data together!

File:Data4PT logo flat.jpg

2023-10-08T19:10:53Z

Admin:

Data4PT logo

Main Page

2023-10-08T19:09:55Z

Admin:

[[Media:DATA4PT Logo.png|center|400px]]

= '''Welcome to the DATA4PT Wiki''' =
[[File:People Collaborating.png|right|400px]]

==Discover, Verify, Connect==

*'''Want to become aware of NAP and related standards?'''
[https://data4pt-project.eu/ Explore the DATA4PT project pages] and enjoy a wealth of knowledge!

*'''Need to verify your NeTEx data?'''
[https://greenlight.atomite.io/ Utilize our free validation tool] for accurate results!

*'''Require support?'''
Don't hesitate! [https://docs.google.com/forms/d/1xQD5pPrxOFvoQrheQ0jpnFtWR3oWdCy5DyUZBRvWr0c/viewform?edit_requested=true Fill in a support request], and we're here to help.

*'''Like to comment on the available pages in the "Discussion" tab?'''
We value your input! [https://docs.google.com/forms/d/1xQD5pPrxOFvoQrheQ0jpnFtWR3oWdCy5DyUZBRvWr0c/viewform?edit_requested=true Contact us] and share your thoughts.

*'''Wish to contribute and create new pages?'''
[https://docs.google.com/forms/d/1xQD5pPrxOFvoQrheQ0jpnFtWR3oWdCy5DyUZBRvWr0c/viewform?edit_requested=true Join our expert community] and be part of something great!

==Why DATA4PT?==

DATA4PT is your one-stop destination for public transportation data, standards, and collaboration. Whether you're a newcomer or an expert, we're here to support your journey.

Join us in shaping the future of public transportation data together!

File:People Collaborating.png

2023-10-08T19:07:03Z

Admin: Admin uploaded a new version of File:People Collaborating.png

Main Page

2023-10-08T19:03:06Z

Admin:

[[File:DATA4PT Logo.png|center|400px]]

= '''Welcome to the DATA4PT Wiki''' =
[[File:People Collaborating.png|right|400px]]

==Discover, Verify, Connect==

*'''Want to become aware of NAP and related standards?'''
[https://data4pt-project.eu/ Explore the DATA4PT project pages] and enjoy a wealth of knowledge!

*'''Need to verify your NeTEx data?'''
[https://greenlight.atomite.io/ Utilize our free validation tool] for accurate results!

*'''Require support?'''
Don't hesitate! [https://docs.google.com/forms/d/1xQD5pPrxOFvoQrheQ0jpnFtWR3oWdCy5DyUZBRvWr0c/viewform?edit_requested=true Fill in a support request], and we're here to help.

*'''Like to comment on the available pages in the "Discussion" tab?'''
We value your input! [https://docs.google.com/forms/d/1xQD5pPrxOFvoQrheQ0jpnFtWR3oWdCy5DyUZBRvWr0c/viewform?edit_requested=true Contact us] and share your thoughts.

*'''Wish to contribute and create new pages?'''
[https://docs.google.com/forms/d/1xQD5pPrxOFvoQrheQ0jpnFtWR3oWdCy5DyUZBRvWr0c/viewform?edit_requested=true Join our expert community] and be part of something great!

==Why DATA4PT?==

DATA4PT is your one-stop destination for public transportation data, standards, and collaboration. Whether you're a newcomer or an expert, we're here to support your journey.

Join us in shaping the future of public transportation data together!

File:People Collaborating.png

2023-10-08T18:48:52Z

Admin:

MediaWiki:Common.css

2023-10-08T17:29:52Z

Admin:

/* CSS placed here will be applied to all skins */
/* Custom CSS for MediaWiki:Common.css */

/* Change the font size and color of headings */
h1, h2, h3, h4, h5, h6 {
font-size: 24px;
color: #333333;
}

/* Style for links */
a {
text-decoration: none;
color: #0066cc;
}

/* Style for tables */
table {
border-collapse: collapse;
width: 100%;
}

table, th, td {
border: 1px solid #ddd;
}

th, td {
padding: 8px;
text-align: left;
}

/* Custom background color for the header */
#header {
background-color: #f7f7f7;
}

/* Custom styling for buttons */
.button {
background-color: #0066cc;
color: #fff;
padding: 10px 20px;
border: none;
border-radius: 5px;
cursor: pointer;
}

/* Additional custom styles here */

/* End of custom CSS */

Main Page

2023-08-21T14:54:27Z

Admin:

Welcome to the [https://data4pt-project.eu/ DATA4PT] Wiki.
{| class="wikitable"
|+
!Do you...
!Please,
|-
|
1. want to become '''aware''' of NAP and related standards?
|
browse these pages and enjoy!
|-
|
2. need to '''verify''' your NeTEx data?
|
use our [https://greenlight.itxpt.eu/ '''free''' validation tool!]
|-
|
3. require '''support'''?
|
fill in a [https://docs.google.com/forms/d/1xQD5pPrxOFvoQrheQ0jpnFtWR3oWdCy5DyUZBRvWr0c/viewform?edit_requested=true support request.]
|-
|
4. like to '''comment''' the available pages in the "Discussion" tab?
|
[https://docs.google.com/forms/d/1xQD5pPrxOFvoQrheQ0jpnFtWR3oWdCy5DyUZBRvWr0c/viewform?edit_requested=true contact us]!
|-
|
5. wish to '''contribute''' and create new pages?
|
be part of the [https://docs.google.com/forms/d/1xQD5pPrxOFvoQrheQ0jpnFtWR3oWdCy5DyUZBRvWr0c/viewform?edit_requested=true Expert community]!
|}
::

SIRI

2023-07-19T14:09:01Z

Admin: /* Mapping with GBFS for real time information */

= SIRI overview =
SIRI was established as European standard in October 2006. It is a CEN (Comité Européen de Normalisation) and Technical Standard that specifies a European interface standard for exchanging information about the planned, current or projected performance of real-time public transport operations between different computer systems.

SIRI allows pairs of server computers to exchange structured real-time information about schedules, vehicles, and connections, together with general informational messages related to the operation of the services. The information can be used for many different purposes, for example:

*To provide real time-departure from stop information for display on stops, internet and mobile delivery systems;
*To provide real-time progress information about individual vehicles;
*To manage the movement of buses roaming between areas covered by different servers;
*To manage the synchronisation of guaranteed connections between fetcher and feeder services;
*To exchange planned and real-time timetable updates;
*To distribute status messages about the operation of the services;
*To provide performance information to operational history and other management systems.

To find out more about the '''SIRI data model''', please visit the [http://www.transmodel-cen.eu/standards/siri/ Transmodel page] and [https://siri-cen.eu/ SIRI page].

== SIRI National and EU minimum profiles inventory ==
National profiles are specified to cover the national needs. To help implementation, DATA4PT is also in process of delivering SIRI EU minimum profile, in collaboration with relevant CEN group. DATA4PT has prepared a table with the currently available SIRI national profiles, including an overview of data categories that are currently covered. For data categories relevant to static data check the [[NeTEX#Profiles inventory|NeTEx Profiles Inventory]].

{| 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; ""
|- style="font-weight:bold;"
! colspan="2" style="text-align:center; min-width: 100px; max-width: 150px;" | SIRI Profiles
! style="width: 80px;" | Full SIRI format
! style="width: 80px;" | EU SIRI Minimum profile
! 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 Norway, Sweden, Finland, Denmark(?)
! style="width: 80px;" | Portugal
! style="width: 80px;" | Slovenija
! style="width: 80px;" | Switzerland
! style="width: 80px;" | UK
! style="width: 80px;" | Irish
! style="width: 80px;" | German - VDV
|-
| colspan="2" | Availability of SIRI national profile
!
! under development
| in progress
|
|
|
|In use in numerous cities and regions
| in progress
| specified but not yet in operation
| Specified and in use
|
|
| in progress
| Specified and in use
|
|
|-
| colspan="2" | EU Minimum SIRI profile based (applicable when EU SIRI minimum profile available)
!
!
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| colspan="2" | EU Minimum SIRI profile compatible (applicable when EU SIRI minimum profile available)
!
!
|
|
|
|
|[[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 SIRI format
!
!
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| colspan="2" | Available mappings with EU Minimum SIRI profile
!
!
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
! colspan="2" | '''Functional scope based on MMTIS EU Regulation 1926/2017'''
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
|-
| style="font-weight:bold; background-color:#efefef;" | LOS 1
| style="font-weight:bold; background-color:#efefef;" | Dynamic travel and traffic data - Level of service 1
!
!
! SIRI implementation in development by PTA
!
!
!
!
!
! specified but not yet in operation
!
!
!
!
!
!
!
|-
| LOS 1-1
| Disruptions (all modes)
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|[[File:compliant.png|15px|link=]] dynamic platform is included
|
| Bus locations for about 800 vehicles included in the integrated public passenger transport system.
|
|[[File:compliant.png|15px|link=]]
|
|
|-
| LOS 1-2
| Real-time status information — delays, cancellations, guaranteed connections monitoring (all modes)
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|[[File:compliant.png|15px|link=]] dynamic platform is included
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|-
| LOS 1-3
| Status of access node features (including dynamic platform information, operational lifts/escalators, closed entrances and exit locations — all scheduled modes)
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|[[File:compliant.png|15px|link=]] dynamic platform is included
|
|
|
|
|
|
|-
| style="font-weight:bold; background-color:#efefef;" | LOS 2
| style="font-weight:bold; background-color:#efefef;" | Dynamic travel and traffic data - Level of service 2
!
!
! SIRI implementation in development by PTA
!
!
!
!
!
!
!
!
!
!
!
!
!
|-
| LOS 2-1
| Estimated departure and arrival times of services
|[[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-2
| Current road link travel times
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|-
| LOS 2-3
| Cycling network closures/diversions
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| LOS 2-4
| Availability of publicly accessible charging stations for electric vehicles and refuelling points for CNG/LNG, hydrogen, petrol and diesel powered vehicles
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| LOS 2-5
| Car-sharing availability, bike sharing availability
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|-
| LOS 2-6
| Car parking spaces available (on and off-street), parking tariffs, road toll tariffs
|[[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;" | Dynamic travel and traffic data - Level of service 3
!
!
!
!
!
!
!
!
!
![[File:compliant.png|15px|link=]]
!
!
!
!
!
!
|-
|
|'''Links to the documentation'''
!
!
!
!
!
!
!
!
!
![https://enturas.atlassian.net/wiki/spaces/PUBLIC/pages/637370420/Norwegian+SIRI+profile SIRI Nordic profile]
!
!
!
!
!
!
|}

= SIRI software =

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 and connectors to SIRI software and between other formats==
{| class="wikitable"
!colspan="1"|Name
!colspan="1"|Availability
!colspan="1"|Description
!colspan="1"|Profile
!colspan="1"|License
!colspan="1"|URL
|-
!style="text-align:left;" rowspan="1"|[[Anshar]]
|Available
|Java based tool to connect, validate and redistribute SIRI. (Act as a national aggreagation hub for all SIRI feeds in Norway)
|Norwegian
|EUPL
|https://github.com/entur/anshar
|-
!style="text-align:left;" rowspan="1"|[[OneBusAway SIRI]]
|Available
|A set of tools to connect to and convert SIRI.
|
|Apache-2.0
|https://github.com/OneBusAway/onebusaway-siri
|-
!style="text-align:left;" rowspan="1"|[[ara]]
|Available
|A set of tools to connect, convert and store SIRI, SIRI-Lite.
|
|Apache-2.0
|https://bitbucket.org/enroute-mobi/ara/src/master/
|-
!style="text-align:left;" rowspan="1"|[[irys]]
|Available
|A set of tools to connect and redistribute SIRI.
|
|CeCILL-B
|https://github.com/afimb/irys
|-
!style="text-align:left;" rowspan="1"|[[Diginext/CS-Group]]
|Available
|
|
|
|https://mobilitx.diginext.fr/
|-
!style="text-align:left;" rowspan="1"|[[Soridis/Lumiplan]]
|Available
|
|
|
|https://www.lumiplan.com/produit/mobiflux/
|-
!style="text-align:left;" rowspan="1"|[[Qommute]]
|Available
|
|
|
|https://qommute.com
|-
|}

==Validators==
{| class="wikitable"
!colspan="1"|Name
!colspan="1"|Availability
!colspan="1"|Description
!colspan="1"|Profile
!colspan="1"|License
!colspan="1"|URL
|-
!style="text-align:left;" rowspan="1"|[[BODS]]
|Available
|Validator of TransXChange and SIRI-VM
|
|Open Source
|https://github.com/department-for-transport-BODS/bods
|-
|}

==Producers from CAD/AVL==
{| class="wikitable"
!colspan="1"|Name
!colspan="1"|Availability
!colspan="1"|Description
!colspan="1"|Profile
!colspan="1"|License
!colspan="1"|URL
|-
!style="text-align:left;" rowspan="1"|[[IVU.realtime]]
|Available
|Producer of realtime data.
|
|Commercial
|https://www.ivu.com/products-and-solutions/ivusuite/passenger-information.html
|-
!style="text-align:left;" rowspan="1"|[[Mobile-ITCS]]
|Available
|Producer of realtime data.
|
|Commercial
|https://www.initse.com/fileadmin/user_upload/Content/3_Solutions/3_Operations/MOBILE-ITCS_us.pdf
|-
!style="text-align:left;" rowspan="1"|[[INEO]]
|Available
|
|
|
|
|-
|-
!style="text-align:left;" rowspan="1"|[[Navocap]]
|Available
|
|
|
|
|-
!style="text-align:left;" rowspan="1"|[[ZenBus]]
|Available
|Producer of realtime data.
|
|Commercial
|https://zenbus.fr/
|-
!style="text-align:left;" rowspan="1"|[[IXXI/RATP Smart System]]
|Available
|Producer of realtime data.
|
|Commercial
|https://www.ratpsmartsystems.com/hopen-go/
|-
!style="text-align:left;" rowspan="1"|[[Alstom]]
|Available
|Producer of realtime data.
|
|Commercial
|
|-
|}

= SIRI extension for New Modes =
In line with NeTEx Part 5, corresponding extensions are made in SIRI for real time data such as current number of available vehicles, current number of spaces available to bring back a vehicle or to park, etc. SIRI also provide updates of positions (typically for free floating vehicles). The SIRI Facility Monitoring (FM) service is extended to provide this counted information. Further details are available in the relevant [https://www.netex-cen.eu/wp-content/uploads/2021/03/NeTEx-extension-for-New-Modes-Detailed-Scope-v04.pdf document].

== Mapping with GBFS for real time information ==
In the framework of the CEN work for the extension, a canonical mapping was made between NeTEx Part 5 /SIRI and GBFS. It is available''' [[Media:Canonical mapping - NeTEx and SIRI new modes with GBFS.pdf|here]]'''.

NeTEX

2023-07-19T09:37:34Z

Admin:

= 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 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.

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.

To find out more about the '''NeTEX data model''', visit the [http://netex-cen.eu/ NeTEX website].

To verify your NeTEx data, use our [https://greenlight.atomite.io/ '''free validation tool'''].

=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.
* 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].
[[File:NeTEx EPIP XSD.png|center|thumb|link=https://data4pt.org/NeTEx/GraphicKit/Documention_of_XSD_for_EPIP.html|Graphic and interactive technical presentation NeTEx XSD for EPIP]]
 NeTEx-Light[[File:NeTEx EPIP reduced XSD.png|right|thumb|link=https://data4pt.org/NeTEx/GraphicKit/Documention_of_reduced_XSD.html|Graphic and interactive technical presentation NeTEx Light (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].

= NeTEx national and EU minimum profiles inventory =
A number of national and transnational profiles have already been defined for different European countries, while there are new profiles 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. The table will be continuously updated following new implementations.

''*Data categories are identified based on [https://eur-lex.europa.eu/eli/reg_del/2017/1926/oj MMTIS EU Regulation 1926/2017]''

<nowiki>**</nowiki> European Passenger Information Profile

<nowiki>***</nowiki> European Passenger Information Accessibility Profile

{| class="wikitable filterable" style="padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;border-spacing:0;text-align:center; "
! colspan="18" |Functional scope per profile
|-
! colspan="2" style="text-align:center; min-width: 100px; max-width: 150px;" |Profiles
! style="width: 80px;" |Full NeTEx format
! style="width: 80px;" |EPIP**
! style="width: 80px;" |EPIAP***
! 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 (Norway, Sweden, Finland, Denmark currently)
! style="width: 80px;" |Portugal
! style="width: 80px;" |Slovenija
! style="width: 80px;" |Switzerland
! style="width: 80px;" |UK
! style="width: 80px;" |Irish
! style="width: 80px;" | German VDV
|-
| colspan="2" |Availability of NeTEx national profile
!
!
!under development
|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
!
!
!
|[[File:compliant.png|15px|link=]]
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|
|
|-
| colspan="2" |NeTEx EPIP compatible
!
!
!
|
|
|
|
|[[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
!
!
!
|
|
|
|
|
|
|
|
|
|
|
|
|
|[https://www.vdv.de/netex.aspx VDV NeTEx page]
|-
| colspan="2" |Available mappings with EPIP profile
!
!
!
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
! colspan="2" |Data categories
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
|-
| style="font-weight:bold; background-color:#efefef;" |LOS 1
| style="font-weight:bold; background-color:#efefef;" |Static data - Level of service 1
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
|-
|LOS 1-1
| 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
|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
|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
|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
|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
|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
|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
|Network topology and routes/lines (topology)
|[[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-9
|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
|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
|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
|Hours of operation
|[[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-13
|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
|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
|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=]]
|
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|-
|LOS 1-17
|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
|Pedestrian network and accessibility facilities
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|-
|
|Framework data
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|-
| style="font-weight:bold; background-color:#efefef;" |LOS 2
! style="font-weight:bold; background-color:#efefef;" |Static data - Level of service 2
!
!
!
!in progress
!
!
!
!
!
!
!
!
!
!
!
!
!
|-
|LOS 2-1
| 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
| 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
|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
|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
|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
|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=]]
|
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|-
|LOS 2-8
|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
|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=]]
|
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|[[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
|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
|How to pay tolls (incl. retail channels, fulfilment methods, payment methods)
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|
|
|
|-
|LOS 3-6
| How to book car sharing, taxis, cycle hire etc. (incl. retail channels, fulfilment methods, payment methods)
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
|LOS 3-7
|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
| 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
|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
|Parameters such as fuel consumption needed to calculate cost
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|-
|LOS 3-11
|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=]]
|
|
|
|
|
|
|-
|
!'''Links to the available documentation<ref>https://github.com/nick-knowles/NeTEx/wiki/NationalProfiles</ref>'''
|
|
|
|
[https://arge-oevv.atlassian.net/wiki/spaces/NET/overview Austrian profile]
|
|
|Denmark implements currently the [https://enturas.atlassian.net/wiki/spaces/PUBLIC/pages/728891481/Nordic+NeTEx+Profile Nordic Profile] and the EU profiles
|
*[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]
*[http://www.normes-donnees-tc.org/wp-content/uploads/2014/05/NF_Profil_NeTEx_pour_les_arrets-_F-_-_v2.pdf Stop Profile]
*[http://www.normes-donnees-tc.org/wp-content/uploads/2019/11/NF_Profil-NeTEx-pour-les-R%C3%A9seauxF-v2.1.pdf Network Profile]
*[http://www.normes-donnees-tc.org/wp-content/uploads/2019/11/NF Profil-NeTEx-pour-les-HorairesF-v2.1.pdf Timetable Profile]
*[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]
|
[http://netex-cen.eu/?page_id=237 Italian Profile]
|
*[https://bison.dova.nu/standaarden/nederlands-netex-profiel Netherlands profile]
*[https://bison.dova.nu/sites/default/files/bison_prijzen_producten_en_tarieven_v8.1.3.0_release.pdf Bison Fares]
|[https://enturas.atlassian.net/wiki/spaces/PUBLIC/pages/728891481/Nordic+NeTEx+Profile Nordic Profile]
|
[https://ptprofiles.azurewebsites.net/netex-profile Portuguese Profile]
|
[https://www.nap.si/_resources/profiles/NeTEx_SI_Profile_v2.pdf Slovenian Profile]
|
[https://transportdatamanagement.ch/en/standards/ Swiss profile - Work In progress]
|
*[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]
|
*[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]
|
[https://www.vdv.de/vdv-462-netex-recommendation-v00-22-english.pdfx VDV462]
|}

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. You can also find contact details for some of the entities responsible for the profiles in the documentation list. Otherwise you can contact us in [https://data4pt-project.eu/requests-requirements/ DATA4PT].

=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"
! 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
|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/
|-
! rowspan="1" style="text-align:left;" |[[netex-gtfs-converter-java]]
|Available
|Export NeTEx data to GTFS
|Nordic
|EUPL
|https://github.com/entur/netex-gtfs-converter-java
|-
!Chimera
|Available
|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
|Framework – https://github.com/cefriel/chimera
Mapping GTFS-NeTEx – https://snap-project.eu/
|-
!'''OpenMove ATLAS'''
|Available
|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
|https://www.openmove.com/
|-
!'''GTFS2NeTEx-converter'''
|Available
|Converts GTFS data in NeTEx Italian Profile.
|EPIP
Italian
|Proprietary License
|Work in Progress
|-
|}

==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
! colspan="1" |Availability
! colspan="1" |Description
! colspan="1" | Profile
! colspan="1" |License
! colspan="1" |URL
|-
! rowspan="1" style="text-align:left;" |[[netex-java-model]]
| Available
|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. Contact DATA4PT if you have questions or have found the golden egg.
|Any
|
|
|-
! rowspan="1" style="text-align:left;" |[[netex-parser-java]]
|Available
|Parse NeTEx files and lookup entities in an index
|Nordic
|EUPL
|https://github.com/entur/netex-parser-java
|-
|}

==Editing /Management & visualisation tools for NeTEx data==
{| 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
|-
! rowspan="1" style="text-align:left;" |[[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"
! 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
!Availability
!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]]
|Available
|Planning system from Datagrafikk for public transport
|Nordic
|-
! rowspan="1" style="text-align:left;" |[[Train Plan]]
|Available
|Planning system from Trapeze for railway
|Nordic
|-
! rowspan="1" style="text-align:left;" |[[IVU]]
|In development
|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
|}

= NeTEx Part 5 for New Modes =
The NeTEx extension for New Modes addresses the development of a data exchange format dedicated to the publication of data concerning ‘Alternative Modes’ (as requested in EU COMMISSION DELEGATED REGULATION (EU) 2017/1926 of 31 May 2017). This work will generate NeTEx Part 5 focusing on (but not a limitation to) car sharing, cycle sharing, carpooling, car/cycle rental. It is primarily oriented towards static data (describing the service that is offered and associated infrastructure, more than its current running status). The corresponding real-time information is provided by SIRI. More information can be found in [https://netex-cen.eu/?page_id=534 NeTEx website]. The technical standard is now available by '''CEN/TS 16614-5:2022 (E).'''

Supportive material is already available through different channels (check below).

== Technical artefacts ==
The XML schema (XSD) for NeTEx Part 5 New Modes is available in [https://github.com/ITxPT/DATA4PTTools GitHub]. In this NeTEx - CEN GitHub channel, examples are also provided, along with other useful documentation.

== Canonical mapping with GBFS ==
Preceding the publication of the extension of the Network Timetable Exchange (NeTEx) for ‘new modes’, the EU-funded project DATA4PT and MobilityData experts release the high-level mapping between the General Bikeshare Feed Specification (GBFS) and Transmodel in order to support better interoperability of shared mobility data feeds. The mapping report is available [[Media:Canonical mapping - NeTEx and SIRI new modes with GBFS.pdf|here]].

= References =
<references />

NeTEX

2023-07-15T08:00:47Z

Admin: /* Canonical mapping with GBFS */

= 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 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.

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.

To find out more about the '''NeTEX data model''', visit the [http://netex-cen.eu/ NeTEX website].

To verify your NeTEx data, use our [https://greenlight.atomite.io/ '''free validation tool'''].

=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.
* 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].
[[File:NeTEx EPIP XSD.png|center|thumb|link=https://data4pt.org/NeTEx/GraphicKit/Documention_of_XSD_for_EPIP.html|Graphic and interactive technical presentation NeTEx XSD for EPIP]]
 NeTEx-Light[[File:NeTEx EPIP reduced XSD.png|right|thumb|link=https://data4pt.org/NeTEx/GraphicKit/Documention_of_reduced_XSD.html|Graphic and interactive technical presentation NeTEx Light (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].

= NeTEx national and EU minimum profiles inventory =
A number of national and transnational profiles have already been defined for different European countries, while there are new profiles 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. The table will be continuously updated following new implementations.

''*Data categories are identified based on [https://eur-lex.europa.eu/eli/reg_del/2017/1926/oj MMTIS EU Regulation 1926/2017]''

<nowiki>**</nowiki> European Passenger Information Profile

<nowiki>***</nowiki> European Passenger Information Accessibility Profile

{| class="wikitable filterable" style="padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;border-spacing:0;text-align:center; "
! colspan="18" |Functional scope per profile
|-
! colspan="2" style="text-align:center; min-width: 100px; max-width: 150px;" |Profiles
! style="width: 80px;" |Full NeTEx format
! style="width: 80px;" |EPIP**
! style="width: 80px;" |EPIAP***
! 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 (Norway, Sweden, Finland, Denmark currently)
! style="width: 80px;" |Portugal
! style="width: 80px;" |Slovenija
! style="width: 80px;" |Switzerland
! style="width: 80px;" |UK
! style="width: 80px;" |Irish
! style="width: 80px;" | German VDV
|-
| colspan="2" |Availability of NeTEx national profile
!
!
!under development
|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
!
!
!
|[[File:compliant.png|15px|link=]]
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|
|
|-
| colspan="2" |NeTEx EPIP compatible
!
!
!
|
|
|
|
|[[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
!
!
!
|
|
|
|
|
|
|
|
|
|
|
|
|
|[https://www.vdv.de/netex.aspx VDV NeTEx page]
|-
| colspan="2" |Available mappings with EPIP profile
!
!
!
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
! colspan="2" |Data categories
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
|-
| style="font-weight:bold; background-color:#efefef;" |LOS 1
| style="font-weight:bold; background-color:#efefef;" |Static data - Level of service 1
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
|-
|LOS 1-1
| 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
|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
|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
|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
|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
|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
|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
|Network topology and routes/lines (topology)
|[[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-9
|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
|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
|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
|Hours of operation
|[[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-13
|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
|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
|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=]]
|
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|-
|LOS 1-17
|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
|Pedestrian network and accessibility facilities
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|-
|
|Framework data
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|-
| style="font-weight:bold; background-color:#efefef;" |LOS 2
! style="font-weight:bold; background-color:#efefef;" |Static data - Level of service 2
!
!
!
!in progress
!
!
!
!
!
!
!
!
!
!
!
!
!
|-
|LOS 2-1
| 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
| 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
|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
|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
|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
|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=]]
|
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|-
|LOS 2-8
|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
|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=]]
|
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|[[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
|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
|How to pay tolls (incl. retail channels, fulfilment methods, payment methods)
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|
|
|
|-
|LOS 3-6
| How to book car sharing, taxis, cycle hire etc. (incl. retail channels, fulfilment methods, payment methods)
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
|LOS 3-7
|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
| 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
|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
|Parameters such as fuel consumption needed to calculate cost
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|-
|LOS 3-11
|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=]]
|
|
|
|
|
|
|-
|
!'''Links to the available documentation<ref>https://github.com/nick-knowles/NeTEx/wiki/NationalProfiles</ref>'''
|
|
|
|
[https://arge-oevv.atlassian.net/wiki/spaces/NET/overview Austrian profile]
|
|
|Denmark implements currently the [https://enturas.atlassian.net/wiki/spaces/PUBLIC/pages/728891481/Nordic+NeTEx+Profile Nordic Profile] and the EU profiles
|
*[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]
*[http://www.normes-donnees-tc.org/wp-content/uploads/2014/05/NF_Profil_NeTEx_pour_les_arrets-_F-_-_v2.pdf Stop Profile]
*[http://www.normes-donnees-tc.org/wp-content/uploads/2019/11/NF_Profil-NeTEx-pour-les-R%C3%A9seauxF-v2.1.pdf Network Profile]
*[http://www.normes-donnees-tc.org/wp-content/uploads/2019/11/NF Profil-NeTEx-pour-les-HorairesF-v2.1.pdf Timetable Profile]
*[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]
|
[http://netex-cen.eu/?page_id=237 Italian Profile]
|
*[https://bison.dova.nu/standaarden/nederlands-netex-profiel Netherlands profile]
*[https://bison.dova.nu/sites/default/files/bison_prijzen_producten_en_tarieven_v8.1.3.0_release.pdf Bison Fares]
|[https://enturas.atlassian.net/wiki/spaces/PUBLIC/pages/728891481/Nordic+NeTEx+Profile Nordic Profile]
|
[https://ptprofiles.azurewebsites.net/netex-profile Portuguese Profile]
|
[https://www.nap.si/_resources/profiles/NeTEx_SI_Profile_v2.pdf Slovenian Profile]
|
[https://transportdatamanagement.ch/en/standards/ Swiss profile - Work In progress]
|
*[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]
|
*[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]
|
[https://www.vdv.de/vdv-462-netex-recommendation-v00-22-english.pdfx VDV462]
|}

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. You can also find contact details for some of the entities responsible for the profiles in the documentation list. Otherwise you can contact us in [https://data4pt-project.eu/requests-requirements/ DATA4PT].

=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"
! 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
|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/
|-
! rowspan="1" style="text-align:left;" |[[netex-gtfs-converter-java]]
|Available
|Export NeTEx data to GTFS
|Nordic
|EUPL
|https://github.com/entur/netex-gtfs-converter-java
|-
!Chimera
|Available
|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
|Framework – https://github.com/cefriel/chimera
Mapping GTFS-NeTEx – https://snap-project.eu/
|-
!'''OpenMove ATLAS'''
|Available
|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
|https://www.openmove.com/
|-
!'''GTFS2NeTEx-converter'''
|Available
|Converts GTFS data in NeTEx Italian Profile.
|EPIP
Italian
|Proprietary License
|Work in Progress
|-
|}

==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
! colspan="1" |Availability
! colspan="1" |Description
! colspan="1" | Profile
! colspan="1" |License
! colspan="1" |URL
|-
! rowspan="1" style="text-align:left;" |[[netex-java-model]]
| Available
|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. Contact DATA4PT if you have questions or have found the golden egg.
|Any
|
|
|-
! rowspan="1" style="text-align:left;" |[[netex-parser-java]]
|Available
|Parse NeTEx files and lookup entities in an index
|Nordic
|EUPL
|https://github.com/entur/netex-parser-java
|-
|}

==Editing /Management & visualisation tools for NeTEx data==
{| 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
|-
! rowspan="1" style="text-align:left;" |[[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"
! 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
!Availability
!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]]
|Available
|Planning system from Datagrafikk for public transport
|Nordic
|-
! rowspan="1" style="text-align:left;" |[[Train Plan]]
|Available
|Planning system from Trapeze for railway
|Nordic
|-
! rowspan="1" style="text-align:left;" |[[IVU]]
|In development
|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
|}

= NeTEx Part 5 for New Modes =
The NeTEx extension for New Modes addresses the development of a data exchange format dedicated to the publication of data concerning ‘Alternative Modes’ (as requested in EU COMMISSION DELEGATED REGULATION (EU) 2017/1926 of 31 May 2017). This work will generate NeTEx Part 5 focusing on (but not a limitation to) car sharing, cycle sharing, carpooling, car/cycle rental. It is primarily oriented towards static data (describing the service that is offered and associated infrastructure, more than its current running status). The corresponding real-time information is provided by SIRI. More information can be found in [https://netex-cen.eu/?page_id=534 NeTEx website]. The technical standard is now available by '''CEN/TS 16614-5:2022 (E).'''

Supportive material is already available through different channels (check below).

== Technical artefacts ==
The XML schema (XSD) for NeTEx Part 5 New Modes is available in [https://github.com/NeTEx-CEN/NeTEx/tree/new-modes GitHub]. In this NeTEx - CEN GitHub channel, examples are also provided, along with other useful documentation.

== Canonical mapping with GBFS ==
Preceding the publication of the extension of the Network Timetable Exchange (NeTEx) for ‘new modes’, the EU-funded project DATA4PT and MobilityData experts release the high-level mapping between the General Bikeshare Feed Specification (GBFS) and Transmodel in order to support better interoperability of shared mobility data feeds. The mapping report is available [[Media:Canonical mapping - NeTEx and SIRI new modes with GBFS.pdf|here]].

= References =
<references />

SIRI

2023-07-15T08:00:14Z

Admin: /* Mapping with GBFS for real time information */

= SIRI overview =
SIRI was established as European standard in October 2006. It is a CEN (Comité Européen de Normalisation) and Technical Standard that specifies a European interface standard for exchanging information about the planned, current or projected performance of real-time public transport operations between different computer systems.

SIRI allows pairs of server computers to exchange structured real-time information about schedules, vehicles, and connections, together with general informational messages related to the operation of the services. The information can be used for many different purposes, for example:

*To provide real time-departure from stop information for display on stops, internet and mobile delivery systems;
*To provide real-time progress information about individual vehicles;
*To manage the movement of buses roaming between areas covered by different servers;
*To manage the synchronisation of guaranteed connections between fetcher and feeder services;
*To exchange planned and real-time timetable updates;
*To distribute status messages about the operation of the services;
*To provide performance information to operational history and other management systems.

To find out more about the '''SIRI data model''', please visit the [http://www.transmodel-cen.eu/standards/siri/ Transmodel page] and [https://siri-cen.eu/ SIRI page].

== SIRI National and EU minimum profiles inventory ==
National profiles are specified to cover the national needs. To help implementation, DATA4PT is also in process of delivering SIRI EU minimum profile, in collaboration with relevant CEN group. DATA4PT has prepared a table with the currently available SIRI national profiles, including an overview of data categories that are currently covered. For data categories relevant to static data check the [[NeTEX#Profiles inventory|NeTEx Profiles Inventory]].

{| 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; ""
|- style="font-weight:bold;"
! colspan="2" style="text-align:center; min-width: 100px; max-width: 150px;" | SIRI Profiles
! style="width: 80px;" | Full SIRI format
! style="width: 80px;" | EU SIRI Minimum profile
! 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 Norway, Sweden, Finland, Denmark(?)
! style="width: 80px;" | Portugal
! style="width: 80px;" | Slovenija
! style="width: 80px;" | Switzerland
! style="width: 80px;" | UK
! style="width: 80px;" | Irish
! style="width: 80px;" | German - VDV
|-
| colspan="2" | Availability of SIRI national profile
!
! under development
| in progress
|
|
|
|In use in numerous cities and regions
| in progress
| specified but not yet in operation
| Specified and in use
|
|
| in progress
| Specified and in use
|
|
|-
| colspan="2" | EU Minimum SIRI profile based (applicable when EU SIRI minimum profile available)
!
!
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| colspan="2" | EU Minimum SIRI profile compatible (applicable when EU SIRI minimum profile available)
!
!
|
|
|
|
|[[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 SIRI format
!
!
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| colspan="2" | Available mappings with EU Minimum SIRI profile
!
!
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
! colspan="2" | '''Functional scope based on MMTIS EU Regulation 1926/2017'''
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
|-
| style="font-weight:bold; background-color:#efefef;" | LOS 1
| style="font-weight:bold; background-color:#efefef;" | Dynamic travel and traffic data - Level of service 1
!
!
! SIRI implementation in development by PTA
!
!
!
!
!
! specified but not yet in operation
!
!
!
!
!
!
!
|-
| LOS 1-1
| Disruptions (all modes)
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|[[File:compliant.png|15px|link=]] dynamic platform is included
|
| Bus locations for about 800 vehicles included in the integrated public passenger transport system.
|
|[[File:compliant.png|15px|link=]]
|
|
|-
| LOS 1-2
| Real-time status information — delays, cancellations, guaranteed connections monitoring (all modes)
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|[[File:compliant.png|15px|link=]] dynamic platform is included
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|-
| LOS 1-3
| Status of access node features (including dynamic platform information, operational lifts/escalators, closed entrances and exit locations — all scheduled modes)
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|[[File:compliant.png|15px|link=]]
|[[File:compliant.png|15px|link=]] dynamic platform is included
|
|
|
|
|
|
|-
| style="font-weight:bold; background-color:#efefef;" | LOS 2
| style="font-weight:bold; background-color:#efefef;" | Dynamic travel and traffic data - Level of service 2
!
!
! SIRI implementation in development by PTA
!
!
!
!
!
!
!
!
!
!
!
!
!
|-
| LOS 2-1
| Estimated departure and arrival times of services
|[[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-2
| Current road link travel times
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|-
| LOS 2-3
| Cycling network closures/diversions
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| LOS 2-4
| Availability of publicly accessible charging stations for electric vehicles and refuelling points for CNG/LNG, hydrogen, petrol and diesel powered vehicles
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
| LOS 2-5
| Car-sharing availability, bike sharing availability
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|
|-
| LOS 2-6
| Car parking spaces available (on and off-street), parking tariffs, road toll tariffs
|[[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;" | Dynamic travel and traffic data - Level of service 3
!
!
!
!
!
!
!
!
!
![[File:compliant.png|15px|link=]]
!
!
!
!
!
!
|-
|
|'''Links to the documentation'''
!
!
!
!
!
!
!
!
!
![https://enturas.atlassian.net/wiki/spaces/PUBLIC/pages/637370420/Norwegian+SIRI+profile SIRI Nordic profile]
!
!
!
!
!
!
|}

= SIRI software =

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 and connectors to SIRI software and between other formats==
{| class="wikitable"
!colspan="1"|Name
!colspan="1"|Availability
!colspan="1"|Description
!colspan="1"|Profile
!colspan="1"|License
!colspan="1"|URL
|-
!style="text-align:left;" rowspan="1"|[[Anshar]]
|Available
|Java based tool to connect, validate and redistribute SIRI. (Act as a national aggreagation hub for all SIRI feeds in Norway)
|Norwegian
|EUPL
|https://github.com/entur/anshar
|-
!style="text-align:left;" rowspan="1"|[[OneBusAway SIRI]]
|Available
|A set of tools to connect to and convert SIRI.
|
|Apache-2.0
|https://github.com/OneBusAway/onebusaway-siri
|-
!style="text-align:left;" rowspan="1"|[[ara]]
|Available
|A set of tools to connect, convert and store SIRI, SIRI-Lite.
|
|Apache-2.0
|https://bitbucket.org/enroute-mobi/ara/src/master/
|-
!style="text-align:left;" rowspan="1"|[[irys]]
|Available
|A set of tools to connect and redistribute SIRI.
|
|CeCILL-B
|https://github.com/afimb/irys
|-
!style="text-align:left;" rowspan="1"|[[Diginext/CS-Group]]
|Available
|
|
|
|https://mobilitx.diginext.fr/
|-
!style="text-align:left;" rowspan="1"|[[Soridis/Lumiplan]]
|Available
|
|
|
|https://www.lumiplan.com/produit/mobiflux/
|-
!style="text-align:left;" rowspan="1"|[[Qommute]]
|Available
|
|
|
|https://qommute.com
|-
|}

==Validators==
{| class="wikitable"
!colspan="1"|Name
!colspan="1"|Availability
!colspan="1"|Description
!colspan="1"|Profile
!colspan="1"|License
!colspan="1"|URL
|-
!style="text-align:left;" rowspan="1"|[[BODS]]
|Available
|Validator of TransXChange and SIRI-VM
|
|Open Source
|https://github.com/department-for-transport-BODS/bods
|-
|}

==Producers from CAD/AVL==
{| class="wikitable"
!colspan="1"|Name
!colspan="1"|Availability
!colspan="1"|Description
!colspan="1"|Profile
!colspan="1"|License
!colspan="1"|URL
|-
!style="text-align:left;" rowspan="1"|[[IVU.realtime]]
|Available
|Producer of realtime data.
|
|Commercial
|https://www.ivu.com/products-and-solutions/ivusuite/passenger-information.html
|-
!style="text-align:left;" rowspan="1"|[[Mobile-ITCS]]
|Available
|Producer of realtime data.
|
|Commercial
|https://www.initse.com/fileadmin/user_upload/Content/3_Solutions/3_Operations/MOBILE-ITCS_us.pdf
|-
!style="text-align:left;" rowspan="1"|[[INEO]]
|Available
|
|
|
|
|-
|-
!style="text-align:left;" rowspan="1"|[[Navocap]]
|Available
|
|
|
|
|-
!style="text-align:left;" rowspan="1"|[[ZenBus]]
|Available
|Producer of realtime data.
|
|Commercial
|https://zenbus.fr/
|-
!style="text-align:left;" rowspan="1"|[[IXXI/RATP Smart System]]
|Available
|Producer of realtime data.
|
|Commercial
|https://www.ratpsmartsystems.com/hopen-go/
|-
!style="text-align:left;" rowspan="1"|[[Alstom]]
|Available
|Producer of realtime data.
|
|Commercial
|
|-
|}

= SIRI extension for New Modes =
In line with NeTEx Part 5, corresponding extensions are made in SIRI for real time data such as current number of available vehicles, current number of spaces available to bring back a vehicle or to park, etc. SIRI also provide updates of positions (typically for free floating vehicles). The SIRI Facility Monitoring (FM) service is extended to provide this counted information. Further details are available in the relevant [https://www.netex-cen.eu/wp-content/uploads/2021/03/NeTEx-extension-for-New-Modes-Detailed-Scope-v04.pdf document].

== Mapping with GBFS for real time information ==
In the framework of the CEN work for the extension, a canonical mapping was made between NeTEx Part 5 /SIRI and GBFS. It is available ''' [[Media:Canonical mapping - NeTEx and SIRI new modes with GBFS.pdf|here]]'''.

Main Page

2023-07-03T16:21:47Z

Admin:

Welcome to the [https://data4pt-project.eu/ DATA4PT] Wiki.
{| class="wikitable"
|+
!Do you...
!Please,
|-
|
1. want to become '''aware''' of NAP and related standards?
|
browse these pages and enjoy!
|-
|
2. need to '''verify''' your NeTEx data?
|
use our [https://greenlight.atomite.io/ '''free''' validation tool!]
|-
|
3. require '''support'''?
|
fill in a [https://docs.google.com/forms/d/1xQD5pPrxOFvoQrheQ0jpnFtWR3oWdCy5DyUZBRvWr0c/viewform?edit_requested=true support request.]
|-
|
4. like to '''comment''' the available pages in the "Discussion" tab?
|
[https://docs.google.com/forms/d/1xQD5pPrxOFvoQrheQ0jpnFtWR3oWdCy5DyUZBRvWr0c/viewform?edit_requested=true contact us]!
|-
|
5. wish to '''contribute''' and create new pages?
|
be part of the [https://docs.google.com/forms/d/1xQD5pPrxOFvoQrheQ0jpnFtWR3oWdCy5DyUZBRvWr0c/viewform?edit_requested=true Expert community]!
|}
::