NeTEX: Difference between revisions

From DATA4PT WIKI
Jump to navigation Jump to search
 
(57 intermediate revisions by 4 users not shown)
Line 1: Line 1:
= NeTEx overview =
[[File:NeTEx.png|250px|right|link=http://netex-cen.eu/|alt=]]


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


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


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


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


=NeTEx-Light  =
NeTEx can be used to collect and integrate data from many different stakeholders, and to reintegrate it as it evolves through successive versions. It is used by public transport operators and IT providers across Europe to support a wide range of passenger information and operational applications.
[[File:NeTEx EPIP reduced XSD.png|right|thumb|link=https://data4pt.org/NeTEx/GraphicKit/Documention_of_reduced_XSD.html|Graphic and interactive technical presentation 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].
== Benefits of using NeTEx ==


=NeTEx EPIP =
NeTEx offers a number of benefits, including:
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]]
<br clear=all>


= NeTEx national and EU minimum profiles inventory =
* '''Flexibility''': NeTEx can be used to represent a wide range of public transport data, including networks, schedules, fares, and real-time information.
A number of national and 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.  
* '''Extensibility''': NeTEx can be extended to support new types of data and functionality.
* '''Interoperability''': NeTEx is a standard format, which means that data can be exchanged between different systems without the need for custom development.
* '''Support for modern web services architectures''' : NeTEx can be used to develop modern, web-based passenger information and operational applications.


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


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


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


{| class="wikitable 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
ℹ️ To find out more about the NeTEX data model, visit the [https://netex-cen.eu/ NeTEX website].
|-
 
! colspan="2" style="text-align:center; min-width: 100px; max-width: 150px;" |Profiles
⚙️ To verify your NeTEx data, use our '''[https://greenlight.atomite.io free validation tool]'''.
! style="width: 80px;" |Full NeTEx format
 
! style="width: 80px;" |EPIP**
= NeTEx European Passenger Information Profile 🇪🇺 =
! style="width: 80px;" |EPIAP***
 
! style="width: 80px;" |Austria
{| class="wikitable"
! style="width: 80px;" |Croatia
! style="width: 80px;" |Czech Republic
! style="width: 80px;" |Denmark
! style="width: 80px;" |France
! style="width: 80px;" |Italy
! style="width: 80px;" | Netherlands
! style="width: 80px;" |Nordic <small><small>(Norway, Sweden, Finland, Denmark currently)</small></small>
! style="width: 80px;" |Portugal
! style="width: 80px;" |Slovenija
! style="width: 80px;" |Switzerland
! style="width: 80px;" |UK
! style="width: 80px;" |Irish
! style="width: 80px;" | German<br> VDV
|-
| colspan="2" |Availability of NeTEx national profile
!
!
!
! Description
!under development
! Documentation
|Specified but  not yet in operation
| not yet specified
|not yet specified
|not yet specified
|Specified and partially in operation
|Specified but not yet in operation
| specified but not yet in  operation
|Specified and in use
| Specified and in use
|specified but not yet in operation
|in progress
|Specified and in use
| specified
|
|-
|-
| colspan="2" |NeTEx EPIP based
|width="150px" style="text-align:center |'''NeTEx EPIP'''|| Ideally, all member states will provide NeTEx files according to the European Passenger Information Profile (EPIP) on their respective National Access Point. Data4PT provides some artefacts to simplify producing and quality assure such information. EPIP-adapted version of the full NeTEx XML schema has been produced. || 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: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
|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].
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
|-
|-
| 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&#x20;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].
= Software & tools 🧰 =


=NeTEx software / tools=
An ecosystem of NeTEx XML tools is under development, including both open-source and commercial products.
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.


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.


==Conversion of NeTEx between other formats==
{| 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"
{| class="wikitable"
== Conversion tools ==
{| class="wikitable" style="width:80%"
! colspan="1" | Name
! colspan="1" | Name
! colspan="1" |Availability
! Availability
! colspan="1" |Description
! width="40%" | |Description
! colspan="1" |Profile
! colspan="1" |Profile
! colspan="1" |License
!width="20%"| License
! colspan="1" |URL
|-
|-
! rowspan="1" style="text-align:left;" |[[netex-protobuf]]
| style="text-align:center |'''[https://github.com/entur/netex-protobuf netex-protobuf]''' ||style="text-align:center |✅ || NeTEx to protobuf converter || All ||EUPL
|Available
|NeTEx to protobuf converter
|all
|EUPL
|https://github.com/entur/netex-protobuf
|-
|-
! rowspan="1" style="text-align:left;" |[[gtfs2netexfr]]
|style="text-align:center | '''[https://github.com/CanalTP/transit_model/tree/master/gtfs2netexfr gtfs2netexfr]''' || style="text-align:center |✅ ||Export GTFS data to NeTEx. ||French    ||   
|Available
| Export GTFS data to NeTEx.
|French
|
|https://github.com/CanalTP/transit_model/tree/master/gtfs2netexfr
|-
|-
! rowspan="1" style="text-align:left;" |[[hastus]]
| 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
|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]]
| 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  
|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]]
| 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
|Available
|Export NeTEx data to GTFS
|Nordic
|EUPL
|https://github.com/entur/netex-gtfs-converter-java
|-
|-
!Chimera
|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
|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/
|-
|-
|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==
== Data validation tools ==
{| class="wikitable"
 
! colspan="1" |Name
{| class="wikitable" style="width:40%;"
! colspan="1" |Availability
! width="25%" | Name
! colspan="1" | Description
!width="10%" | Availability
! colspan="1" |Profile
! width="40%"| Description
! colspan="1" |License
!width="10%" | Profile
! colspan="1" |URL
!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 | '''[https://github.com/ITxPT/DATA4PTTools Greenlight - The Data4PT Validation tool]''' ||style="text-align:center |✅||Validating NeTEx data. ||All ||
|-
|-
! rowspan="1" style="text-align:left;" |[[XMLlint]]
| 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 ||
|Available
|XML syntax validation, XSD schema validation and constraint checking.
|All
|MIT
|http://www.xmlsoft.org/
|-
|-
| 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 and software development aids==
== Language bindings ==
{| class="wikitable"
{| class="wikitable" style="width: 45%;"
! colspan="6" |NeTEx XML bindings
! Name
! Availability
! Description
! Profile
! License
|-
|-
! colspan="1" |Name
| 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
! colspan="1" |Availability
! colspan="1" |Description
! colspan="1" | Profile
! colspan="1" |License
! colspan="1" |URL
|-
|-
! rowspan="1" style="text-align:left;" |[[netex-java-model]]
|style="text-align:center | '''netex-csharp-model''' ||style="text-align:center |❌ || NeTEx XML bindings for C#. Currently being researched with a variety of tools.<br>Contact DATA4PT if you have questions or have found the golden egg. ||All ||
| 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]]
|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
|Not Available
|NeTEx XML bindings for C#. Currently being researched with a variety of tools.<br>Contact DATA4PT if you have questions or have found the golden egg.
|Any
|
|
|-
! 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==
== Editing /Management & visualisation tools ==
{| class="wikitable"
 
! colspan="1" |Name
{| class="wikitable" style="width: 75%;"
! colspan="1" |Availability
! Name
! colspan="1" |Description
! Availability
! colspan="1" |Profile
! Description
! colspan="1" |License
! Profile
! colspan="1" | URL
! 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 <br> frontend - https://github.com/entur/enki
|-
|-
! rowspan="1" style="text-align:left;" |[[Chouette|Nplan]]
|style="text-align:center |'''NSR''' ||style="text-align:center | ✅|| Java backend / JavaScript frontend for import/creation/edit/export for NeTEx stops data. (Act as a National Stops Register for the whole of Norway) || Nordic ||EUPL ||backend - https://github.com/entur/tiamat <br> frontend - https://github.com/entur/abzu
|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]]
| style="text-align:center |'''Chouette'''|| style="text-align:center |✅|| Java backend / Ruby frontend for import/validation/edit/export of NeTEx data. Highly modified version of the old AFIMB version of Chouette. NOTE: Legacy software not recommended for new implemetations ||Nordic ||CeCILL-B ||backend - https://github.com/entur/chouette <br> frontend - https://github.com/entur/chouette2
| 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]]
|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 ||
|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]]
|style="text-align:center |'''[https://mobilitx.diginext.fr/ mobilitx]''' || style="text-align:center |✅|| || || ||
|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]]
|style="text-align:center |'''[https://www.lumiplan.com/produit/mobiref/ mobiref]''' ||style="text-align:center | ✅ || || || ||
| Available
|
|
|
|https://mobilitx.diginext.fr/
|-
|-
! rowspan="1" style="text-align:left;" |[[mobiref]]
|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
|Available
|
|
|
|https://www.lumiplan.com/produit/mobiref/
|-
|-
! rowspan="1" style="text-align:left;" |[[NeTEx Reader]]
|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 || ||
| 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]]
|style="text-align:center | '''[https://www.ivu.com/news/news/article/delfi-successfully-migrates-to-ivucloud.html IVU.cloud]''' || style="text-align:center |✅|| ||EPIP || ||
|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]]
|style="text-align:center |'''[https://www.pluservice.net/it/soluzioni/gestione-rete-e-turni Motus]''' ||style="text-align:center | ✅|| 4Motus is the Fleet Scheduling Management System provided by Pluservice. The application is designed by independent and integrated modules which can be activated according to specific operational needs. <br> One of the latest module created and already available is the generation of NeTEx datasets starting from the operational data collected by public transport operators. For this purpose, Motus receives the input data starting from a GTFS and it is able to enrich  these data with further relevant information such as contracts, vehicles. Then Motus transforms these data into the NeTEx Italian profile.<br> '''Data model:''' the database is designed according to Transmodel specifications, European reference standard (EN12896) for public  transport. ||Italian || ||
|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.
== Journey planning engine ==


'''Data model:''' the database is designed according to Transmodel specifications, European reference standard (EN12896) for public transport.
{| class="wikitable" style="width: 60%;"
|Italian
! Name
|
! Availability
|https://www.pluservice.net/it/soluzioni/gestione-rete-e-turni
! 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
 
==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]]
| 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. || ||
| 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 ==
==Planning system supporting native NeTEx export ==
{| class="wikitable"
 
{| class="wikitable" style="width: 25%;"
!Name
!Name
!Availability
!Availability
!Description
!Developped by
!Profile
!Profile
!Additional documentation
|-
|-
! rowspan="1" style="text-align:left;" |[[Hastus]]
|style="text-align:center | [https://www.giro.ca/en-ca/our-solutions/segments/public-transport/ Hastus] || style="text-align:center |✅ || Giro || Nordic <br> Dutch || Dutch patch: https://github.com/skinkie/hastus
|Available
|Planning system from Giro for public transport
| Nordic
|-
|-
! rowspan="1" style="text-align:left;" |[[Trapeze Cloud TP10|Trapeze]]
|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
|Available
|Planning system from Trapeze for public transport
|Nordic
|-
|-
! rowspan="1" style="text-align:left;" |[[DG Buss]]
| style="text-align:center | [https://www.datagrafikk.no/?tag=dgbuss  DG Buss] || style="text-align:center |✅ || Datagrafikk || Nordic ||
|Available
|Planning system from Datagrafikk for public transport
|Nordic
|-
|-
! rowspan="1" style="text-align:left;" |[[Train Plan]]
| style="text-align:center | [https://www.trapezegroup.com.au/solutions/planning-and-scheduling-rail  Planning & Scheduling for Train] ||style="text-align:center |✅ || Trapeze ||Nordic ||
|Available
|Planning system from Trapeze for railway
|Nordic
|-
|-
! rowspan="1" style="text-align:left;" |[[IVU]]
| 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
|In development
|Planning system from IVU for public transport
|Nordic
|-
|-
! rowspan="1" style="text-align:left;" |[[IVU]]
| style="text-align:center | [https://turnit.com/ Turnit Ride] ||style="text-align:center |✅ ||Turnit for public transport ||Nordic ||
|In development
|Planning system from IVU for railway
|Nordic
|-
|-
! rowspan="1" style="text-align:left;" |[[Turnit]]
|style="text-align:center | Nplan ||style="text-align:center |✅ ||Entur for public transport ||Nordic || backend: https://github.com/entur/uttu  <br> frontend: https://github.com/entur/enki
|Available
|Planning system from Turnit for public transport
|Nordic
|-
|-
! rowspan="1" style="text-align:left;" |[[Nplan]]
| style="text-align:center | [https://www.hacon.de/en/portfolio/timetable-construction-disposition/  TPs Suite] ||style="text-align:center | ✅ ||Hacon ||Nordic ||
|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 =
= NeTEx part 5 for 🆕 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].'''''This work is currently under CEN voting and it is expected to be published by the end of March.'''''


Nevertheless, supportive material is already available through different channels (check below).  
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.


== Technical artefacts ==
''NeTEx Part 5 is now available as '''CEN/TS 16614-5:2022 (E)'''''
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.  
[[File:NeTEx-part5.png|400px|right|]]


== Canonical mapping with GBFS ==
{| class="wikitable" style="width: 50%;"
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]]. 
|-
!
!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 =
= References =
<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
|-
|}

Latest revision as of 10:39, 10 October 2024

NeTEx overview 🔍

What is NeTEx?

NeTEx.png

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 NeTEX website.

⚙️ To verify your NeTEx data, use our free validation tool.

NeTEx European Passenger Information Profile 🇪🇺

Description Documentation
NeTEx EPIP Ideally, all member states will provide NeTEx files according to the European Passenger Information Profile (EPIP) on their respective National Access Point. Data4PT provides some artefacts to simplify producing and quality assure such information. EPIP-adapted version of the full NeTEx XML schema has been produced. Browse the graphic and interactive technical presentation and download the relevant artefacts and available example here.
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 here.


Software & tools 🧰

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

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

XML tools

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

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

Conversion tools

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

Data validation tools

Name Availability Description Profile License
XMLlint ✅ XML syntax validation, XSD schema validation and constraint checking. All MIT
Greenlight - The Data4PT Validation tool ✅ Validating NeTEx data. All
NeTEx validator java ✅ Validation library for NeTEx data, analyzing and reporting schema compliance. Nordic
Antu ✅ Validate NeTEx datasets against the Nordic NeTEx Profile. Nordic

Language bindings

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

Editing /Management & visualisation tools

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

Journey planning engine

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

Planning system supporting native NeTEx export

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

NeTEx part 5 for 🆕 modes

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

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

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

References

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