Difference between revisions of "NeTEX"

From DATA4PT WIKI
Jump to navigation Jump to search
(125 intermediate revisions by 7 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.
  
−
= Providing NeTEx as open data on a National Access Point (NAP) =
+
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.
  
−
Ideally all member states will provide NeTEx files according to the European Passenger Information Profile (EPIP) on their respective National Access Point.
+
== Benefits of using NeTEx ==
  
−
Data4PT provides some artefacts to simplify producing and quality assure such information.
+
NeTEx offers a number of benefits, including:
  
−
First of all a simplified and EPIP-adapted version of the full NeTEx XML schema has been produced.
+
* '''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.
  
−
A graphic and interactive technical presentation of the adapted schema is available.
+
== Examples of NeTEx in use ==
  
−
Download the EPIP adapted XML-schema here
+
NeTEx is used in a variety of ways across the public transport industry. For example:
  
−
Download an EPIP example file here
+
*'''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.
  
−
== Graphic interactive documentation of NeTEx XSD adapted to EPIP profile ==
 
−
You will be able to traverse the XSD by clicking in the diagrams and on underlined texts.
 
−
Use the browser's back button if you wish to return to a previous diagram.
 
  
−
<pre>Tips: Observe that you need to click in the middle of the object (on the name of it) that you wish to expand.
+
ℹ️ To find out more about the NeTEX data model, visit the [https://netex-cen.eu/ NeTEX website].
−
It will not work if you click on the '+'</pre>
 
  
−
Start browsing the schema online by clicking HERE
+
⚙️ 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].
 +
|-
 +
|}
 +
 +
= 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) ==
−
Or download the graphic presentation for off-line browsing
 
  
−
+
{| class="wikitable" style="width:70%"
−
Download XSD - the NeTEx XSD adapted to EPIP profile
+
|-
 +
!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) ==
  
−
Download an example XML-file for the EPIP profile
+
{| 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.
  
−
This presentation should not be interpreted as being normative.
+
📄 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].
  
−
For GML parts please see ISO/DIS 19136 8.2.
+
= Software & tools 🧰 =
−
GML is an OGC Standard.
 
−
Copyright (c) 2007, 2010, 2016, 2018 Open Geospatial Consortium.
 
−
Copyright (c) 2007,2010 Open Geospatial Consortium, Inc. All Rights Reserved.
 
−
To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ .
 
−
See also https://www.ogc.org/standards/gml and http://schemas.opengis.net/gml/3.2.1/
 
  
−
For NeTEx parts note that this documentation relates to a simplified schema that represents a subset of the full NeTEx-schema covering the European Passenger Information Profile.
+
An ecosystem of NeTEx XML tools is under development, including both open-source and commercial products.
−
That XSD file should not be interpreted as being normative. Neither does that XSD replace the offical NeTEx XSD schemas. It should be used in addition to the offical NeTEx XSD schemas and not instead of.
 
−
The official NeTEx XSD schema and basic examples are available at Github https://github.com/NeTEx-CEN/NeTEx (note that this is the only source for NeTEx latest official schema) Note that parts of the content in this file consists of extracts from files in the official NeTEx XSD schema and therefore are covered by Copyright CEN, Crown Copyright 2009-2020. Any such copyrights still apply.
 
  
−
= NeTEx software details =
 
 
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.
  
−
==Conversion of NeTEx between other formats==
+
== 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"
 
{| class="wikitable"
−
!colspan="1"|Name
+
 
−
!colspan="1"|Availability
+
== Conversion tools ==
−
!colspan="1"|Description
+
 
−
!colspan="1"|Profile
+
{| class="wikitable" style="width:80%"
−
!colspan="1"|License
+
! colspan="1" | Name
−
!colspan="1"|URL
+
! Availability
 +
! width="40%" | |Description
 +
! colspan="1" |Profile
 +
!width="20%"| colspan="1" |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 |'''GTFS2NeTEx-converter''' ||style="text-align:center |✅ || Converts GTFS data in NeTEx Italian Profile. || EPIP  Italian  ||Proprietary License
 +
|-
 +
|}
 +
 
 +
== 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:left;" rowspan="1"|[[gtfs2netexfr]]
+
| style="text-align:center |'''[http://www.xmlsoft.org/ XMLlint]''' || style="text-align:center |✅ ||XML syntax validation, XSD schema validation and constraint checking. ||All ||MIT 
−
|Available
 
−
|Export GTFS data to NeTEx.
 
−
|French
 
−
|
 
−
|https://github.com/CanalTP/transit_model/tree/master/gtfs2netexfr
 
 
|-
 
|-
−
!style="text-align:left;" rowspan="1"|[[hastus]]
+
|style="text-align:center | '''[https://github.com/ITxPT/DATA4PTTools Greenlight - The Data4PT Validation tool]''' ||style="text-align:center |✅||Validating NeTEx data. ||All ||
−
|Available
 
−
|Giro Hastus OIG script to export NeTEx from a system, in addition can export crew operations.
 
−
|Dutch, Norwegian(?)
 
−
|AGPL-3.0
 
−
|https://github.com/skinkie/hastus
 
 
|-
 
|-
−
!style="text-align:left;" rowspan="1"|[[josm-plugin-netex-converter]]
+
| 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
 
−
|Export OpenStreetMap pedestrian routing information into NeTEx.
 
−
|
 
−
|GPL 2.0
 
−
|https://gitlab.com/labiangashi/josm-plugin-netex-converter/
 
 
|-
 
|-
 +
| style="text-align:center |'''[https://github.com/entur/antu Antu]''' ||style="text-align:center |✅|| Validate NeTEx datasets against the Nordic NeTEx Profile. ||Nordic ||
 
|}
 
|}
  
−
==Data Validation tools==
+
== Language bindings ==
−
{| class="wikitable"
+
{| class="wikitable" style="width: 45%;"
−
!colspan="1"|Name
+
! Name
−
!colspan="1"|Availability
+
! Availability
−
!colspan="1"|Description
+
! Description
−
!colspan="1"|Profile
+
! Profile
−
!colspan="1"|License
+
! License
−
!colspan="1"|URL
+
|-
 +
| 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.<br>Contact DATA4PT if you have questions or have found the golden egg. ||All ||
 
|-
 
|-
−
!style="text-align:left;" rowspan="1"|[[XMLlint]]
+
|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
−
|Available
 
−
|XML syntax validation, XSD schema validation and constraint checking.
 
−
|All
 
−
|MIT
 
−
|http://www.xmlsoft.org/
 
 
|-
 
|-
 
|}
 
|}
  
−
==Language bindings and software development aids==
+
== Editing /Management & visualisation tools ==
−
{| class="wikitable"
+
 
−
!colspan="6"|NeTEx XML bindings
+
{| 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 <br> 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 <br> 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 <br> 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. <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 || ||
 
|-
 
|-
−
!colspan="1"|Name
+
|}
−
!colspan="1"|Availability
+
 
−
!colspan="1"|Description
+
== Journey planning engine ==
−
!colspan="1"|Profile
+
 
−
!colspan="1"|License
+
{| class="wikitable" style="width: 60%;"
−
!colspan="1"|URL
+
!  Name
 +
! Availability
 +
! Description
 +
! Profile
 +
! License
 
|-
 
|-
−
!style="text-align:left;" rowspan="1"|[[netex-java-model]]
+
| 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
−
|Available
 
−
|NeTEx XML bindings for Java, with additions to map temporal types to native objects.
 
−
|Any
 
−
|EUPL
 
−
|https://github.com/entur/netex-java-model
 
 
|-
 
|-
−
!style="text-align:left;" rowspan="1"|[[netex-csharp-model]]
+
| 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. || ||
−
|Not Available
 
−
|NeTEx XML bindings for C#. Currently being researched with a variety of tools.<br>Contact DATA4PT if you have questions or have found the golden egg.
 
−
|Any
 
−
|
 
−
|
 
 
|-
 
|-
 
|}
 
|}
  
−
==Editing /Management  & visuallisation tools for  NeTEx data==
+
==Planning system supporting native NeTEx export ==
−
{| class="wikitable"
+
 
−
!colspan="1"|Name
+
{| class="wikitable" style="width: 25%;"
−
!colspan="1"|Availability
+
!Name
−
!colspan="1"|Description
+
!Availability
−
!colspan="1"|Profile
+
!Developped by
−
!colspan="1"|License
+
!Profile
−
!colspan="1"|URL
+
!Additional documentation
 +
|-
 +
|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
 +
|-
 +
|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:left;" rowspan="1"|[[Chouette]]
+
| style="text-align:center | [https://turnit.com/ Turnit Ride] ||style="text-align:center |✅ ||Turnit for public transport ||Nordic ||
−
|Available
 
−
|Java based NeTEx tools, transforms between profiles and standards (NeTEx, GTFS, Neptune).
 
−
|EPIP
 
−
|Apache 2.0
 
−
|https://enroute.mobi/produits/chouette/
 
 
|-
 
|-
−
!style="text-align:left;" rowspan="1"|[[mobilitx]]
+
|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
 
−
|
 
−
|
 
−
|
 
−
|https://mobilitx.diginext.fr/
 
 
|-
 
|-
−
!style="text-align:left;" rowspan="1"|[[mobiref]]
+
| style="text-align:center | [https://www.hacon.de/en/portfolio/timetable-construction-disposition/  TPs Suite] ||style="text-align:center | ✅ ||Hacon ||Nordic ||
−
|Available
+
|}
−
|
+
 
−
|
+
= NeTEx part 5 for 🆕 modes =
−
|
+
 
−
|https://www.lumiplan.com/produit/mobiref/
+
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%;"
 
|-
 
|-
−
!style="text-align:left;" rowspan="1"|[[NeTEx Reader]]
+
!
−
|In Development
+
!Description
−
|C# based XML tool, based on Giro Hastus XSD.
 
−
|Dutch
 
−
|
 
−
|https://www.youtube.com/watch?v=mpb_1Y9uR5k
 
 
|-
 
|-
−
!style="text-align:left;" rowspan="1"|[[netexconv2]]
+
| '''[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.
−
|In Development
 
−
|Java based NeTEx tools, transforms between profiles and standards (NeTEx, DINO, HAFAS, KV1, GTFS).
 
−
|Dutch, Norwegian
 
−
|
 
−
|
 
 
|-
 
|-
−
!style="text-align:left;" rowspan="1"|[[IVU.cloud]]
+
| '''[https://data4pt.org/w/images/5/5b/Canonical_mapping_-_NeTEx_and_SIRI_new_modes_with_GBFS.pdf Canonical mapping with GBFS]'''
−
|Available
+
| The EU-funded project DATA4PT and MobilityData experts have released a high-level mapping between the General Bikeshare Feed Specification (GBFS) and Transmodel to support better interoperability of shared mobility data feeds.
−
|
 
−
|EPIP
 
−
|
 
−
|https://www.ivu.com/news/news/article/delfi-successfully-migrates-to-ivucloud.html
 
 
|-
 
|-
 
|}
 
|}
  
−
==NeTEx data enabled==
+
= References =
−
{| class="wikitable"
+
 
−
!colspan="1"|Name
+
{| class="wikitable" style="width: 35%;"
−
!colspan="1"|Availability
+
|-
−
!colspan="1"|Description
+
!Name
−
!colspan="1"|Profile
+
!Description
−
!colspan="1"|License
+
|-
−
!colspan="1"|URL
+
| '''[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
 
|-
 
|-
−
!style="text-align:left;" rowspan="1"|[[OpenTripPlanner]]
+
| '''[https://netex-cen.eu/ NeTEx Website]'''
−
|Available
+
| Find general information on NeTEx project
−
|Timetable and shortest path journey planner supporting reading various input formats including GTFS and NeTEx.
 
−
|Norwegian
 
−
|Apache 2.0
 
−
|http://docs.opentripplanner.org/en/dev-2.x/Netex-Norway/
 
 
|-
 
|-
 
|}
 
|}

Revision as of 14:06, 12 March 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.

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

Profile Name NeTEx EPIP Based* NeTEx EPIP Compatible** Documentation
Austria (AT) ✅ Austrian profile
Denmark (DK) ✅ Denmark profile - NAP in Denmark
France (FR) ✅ French profile - Common profil - Stop Profile - Network Profil - Timetable profile - Fare Profile - Parking profile - Accessibility Profile
Italy (IT) ✅ Italian profile
Netherlands (NL) ✅ Netherlands profile - Bison Fares
Nordic (Norway, Sweden, Finland, Denmark) ✅ Nordic profile
Portugal (PT) Portuguese profile
Slovenija (SI) ✅ Slovenian profile
UK (GB) ✅ UK profile - Introduction - Stop and Timetables - Fares
Ireland (IE) Irish profile - Profile Elements - Profile Data Mappings
Czech Republic (CZ) ✅

*Profiles of this category have been specified based on EU Minimum profile.

** 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 MMTIS EU Regulation 1926/2017

Data categories table.
Level of service (LOS) Static data
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
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.
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)

Data Categories EPIP AT DK FR IT NL Nordic (SE, NOR, DK, FIN) PT SI GB
LOS 1-1 ✅ ✅ ✅
LOS 1-2 ✅ ✅ ✅ ✅
LOS 1-3 ✅ ✅ ✅
LOS 1-4 ✅ ✅ ✅ ✅ ✅ ✅ ✅
LOS 1-5 ✅ ✅ ✅ ✅ ✅ ✅
LOS 1-6 ✅ ✅ ✅ ✅ ✅
LOS 1-7 ✅ ✅ ✅ ✅ ✅
LOS 1-8 ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅
LOS 1-9 ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅
LOS 1-10 ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅
LOS 1-11 ✅ not existent ✅ ✅ For connection links we use journey planner based on OSM map data, road, cycle, and pedestrian network is based on OpenStreetMap ✅ ✅
LOS 1-12 ✅ ✅ ✅ ✅ ✅
LOS 1-13 ✅ ✅ ✅ ✅ ✅ ✅
LOS 1-14 ✅ ✅ ✅ ✅ ✅
LOS 1-15 ✅ ✅ ✅ ✅
LOS 1-16 ✅ ✅ ✅
LOS 1-17 ✅ ✅ ✅
LOS 1-18 ✅ ✅ ✅
Framework data ✅

Static data - Level of service 2 (LOS 2)

Data Categories EPIP AT DK FR IT NL Nordic (SE, NOR, DK, FIN) PT SI GB
LOS 2-1 ✅ ✅ ✅ ✅
LOS 2-2 ✅ ✅ ✅ ✅
LOS 2-3 ✅ ✅ ✅ ✅
LOS 2-4 Only charging stations for electric vehicles ✅
LOS 2-5 ✅ ✅ ✅ ✅
LOS 2-6 ✅ ✅ ✅ ✅
LOS 2-7 ✅ ✅ ✅
LOS 2-8 ✅ ✅ ✅
LOS 2-9 ✅ ✅ ✅ ✅ ✅
LOS 2-10 ✅ ✅ ✅ ✅
LOS 2-11 ✅ ✅ ✅ ✅
LOS 2-12 ✅ ✅ ✅ ✅ ✅

Static data - Level of service 3 (LOS 3)

Data Categories EPIP AT DK FR IT NL Nordic (SE, NOR, DK, FIN) PT SI GB
LOS 3-1 ✅ ✅ ✅
LOS 3-2 ✅ ✅ ✅
LOS 3-3 ✅ ✅ ✅
LOS 3-4 ✅ ✅
LOS 3-5 ✅
LOS 3-6
LOS 3-7 ✅
LOS 3-8 ✅
LOS 3-9 ✅
LOS 3-10 ✅
LOS 3-11 ✅

⚠️ If you believe that your use cases are resolved in an existing profile, it is highly recommended to adopt an existing solutionand 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 DATA4PT.

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 colspan="1" |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 Proprietary License

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=483"