Difference between revisions of "NeTEX"

From DATA4PT WIKI
Jump to navigation Jump to search
(46 intermediate revisions by 4 users not shown)
Line 10: Line 10:
 
To find out more about the '''NeTEX data model''', visit the [http://netex-cen.eu/ NeTEX website].
 
To find out more about the '''NeTEX data model''', visit the [http://netex-cen.eu/ NeTEX website].
  
−
=NeTEx-light=
+
=NeTEx-Light  =
−
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.
+
[[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.
  
−
First of all a simplified and EPIP-adapted version of the full NeTEx XML schema has been produced.
+
The '''graphic interactive technical presentation''' and the technical artefacts are available [https://data4pt.org/NeTEx/GraphicKit/Documention_of_reduced_XSD.html here].
−
* [https://data4pt.org/NeTEx/GraphicKit/Documention_of_XSD_for_EPIP.html Browse] the '''graphic and interactive''' technical presentation of the adapted schema.
 
−
**[[Media:XSD EPIP.zip|<u>Download EPIP adapted XML-schema</u>]]
 
−
** [[Media:XML Example EPIP.zip|<u>Download EPIP example file</u>]]
 
−
* [https://github.com/NeTEx-CEN/NeTEx-light Browse] the '''dedicated Github repository''' for the EPIP Reduced XSD  [[File:Github-icon.png|30px|link=https://github.com/NeTEx-CEN/NeTEx-light]]
 
  
−
= National profiles =
+
=NeTEx EPIP =
−
A number of National and international profiles have already been defined for different European countries and more are under development.  A list of these profiles with links to the relevant documentation is available here:  
+
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>
  
−
https://github.com/nick-knowles/NeTEx/wiki/NationalProfiles
+
= NeTEx national and EU minimum profiles inventory =
 +
A number of national and transnational profiles have already been defined for different European countries, while there are new profiles under development. In the following table, DATA4PT provides an overview of the key characteristics of the national profiles per country, including the data categories that are currently covered. The table will be continuously updated following new implementations.  
  
−
If your use cases are resolved in an existing profile, try using it instead of reinventing the wheel. If every country makes its own profile, we don't reach interoperable data. You will probably save time and money by cooperate with an existing one.
+
''*Data categories are identified based on [https://eur-lex.europa.eu/eli/reg_del/2017/1926/oj MMTIS EU Regulation 1926/2017]''  
  
−
= NeTEx software / tools =
+
<nowiki>**</nowiki> European Passenger Information Profile
 +
 
 +
<nowiki>***</nowiki> European Passenger Information Accessibility Profile   
 +
 
 +
{| class="wikitable filterable" style="padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;border-spacing:0;text-align:center; "
 +
! colspan="18" |Functional scope per profile
 +
|-
 +
! colspan="2" style="text-align:center; min-width: 100px; max-width: 150px;" |Profiles
 +
! style="width: 80px;" |Full NeTEx format
 +
! style="width: 80px;" |EPIP**
 +
! style="width: 80px;" |EPIAP***
 +
! style="width: 80px;" |Austria
 +
! style="width: 80px;" |Croatia
 +
! style="width: 80px;" |Czech Republic
 +
! style="width: 80px;" |Denmark
 +
! style="width: 80px;" |France
 +
! style="width: 80px;" |Italy
 +
! style="width: 80px;" | Netherlands
 +
! style="width: 80px;" |Nordic <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
 +
!
 +
!
 +
!under development
 +
|Specified but  not yet in operation
 +
| not yet specified
 +
|not yet specified
 +
|not yet specified
 +
|Specified and partially in operation
 +
|Specified but not yet in operation
 +
| specified but not yet in  operation
 +
|Specified and in use
 +
| Specified and in use
 +
|specified but not yet in operation
 +
|in progress
 +
|Specified and in use
 +
| specified
 +
|
 +
|-
 +
| colspan="2" |NeTEx EPIP based
 +
!
 +
!
 +
!
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|-
 +
| colspan="2" |NeTEx EPIP compatible
 +
!
 +
!
 +
!
 +
|
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|-
 +
| colspan="2" |Available mappings with full NeTEx profile
 +
!
 +
!
 +
!
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|[https://www.vdv.de/netex.aspx VDV NeTEx page]
 +
|-
 +
| colspan="2" |Available mappings with EPIP profile
 +
!
 +
!
 +
!
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|-
 +
! colspan="2" |Data categories
 +
!
 +
!
 +
!
 +
!
 +
!
 +
!
 +
!
 +
!
 +
!
 +
!
 +
!
 +
!
 +
!
 +
!
 +
!
 +
!
 +
!
 +
|-
 +
| style="font-weight:bold; background-color:#efefef;" |LOS 1
 +
| style="font-weight:bold; background-color:#efefef;" |Static data -  Level of service 1
 +
!
 +
!
 +
!
 +
!
 +
!
 +
!
 +
!
 +
!
 +
!
 +
!
 +
!
 +
!
 +
!
 +
!
 +
!
 +
!
 +
!
 +
|-
 +
|LOS 1-1
 +
| Address identifiers (building  number, street name, postcode)
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|-
 +
|LOS 1-2
 +
|Topographic places (city, town,  village, suburb, administrative unit)
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|-
 +
|LOS 1-3
 +
|Points of interest (related to transport information) to which  people may wish to travel
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|-
 +
|LOS 1-4
 +
|Operational Calendar, mapping  day types to calendar dates
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|-
 +
|LOS 1-5
 +
|Identified access nodes (all  scheduled modes)
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|-
 +
|LOS 1-6
 +
|Geometry/map layout structure of  access nodes (all scheduled modes)
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|-
 +
|LOS 1-7
 +
|Connection links where  interchanges may be made, default transfer times between modes at  interchanges
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|-
 +
|LOS 1-8
 +
|Network topology and  routes/lines (topology)
 +
|[[File:compliant.png|15px|link=]]
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|[[File:compliant.png|15px|link=]]
 +
|[[File:compliant.png|15px|link=]]
 +
|[[File:compliant.png|15px|link=]]
 +
|[[File:compliant.png|15px|link=]]
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|-
 +
|LOS 1-9
 +
|Transport operators
 +
|[[File:compliant.png|15px|link=]]
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|[[File:compliant.png|15px|link=]]
 +
|[[File:compliant.png|15px|link=]]
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|-
 +
|LOS 1-10
 +
|Timetables
 +
|[[File:compliant.png|15px|link=]]
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|[[File:compliant.png|15px|link=]]
 +
|[[File:compliant.png|15px|link=]]
 +
|[[File:compliant.png|15px|link=]]
 +
|[[File:compliant.png|15px|link=]]
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|-
 +
|LOS 1-11
 +
|Planned interchanges between  guaranteed scheduled services
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|For connection links we use  journeyplanner based on OSM map data, road, cycle and pedestrian network is  based on OpenStreetMap
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|-
 +
|LOS 1-12
 +
|Hours of operation
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|-
 +
|LOS 1-13
 +
|Vehicles (low floor; wheelchair  accessible.)
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|-
 +
|LOS 1-14
 +
|Accessibility of access nodes,  and paths within an interchange (such as existence of lifts, escalators)
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|-
 +
|LOS 1-15
 +
|Existence of assistance services  (such as existence of on-site assistance)
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|-
 +
|LOS 1-16
 +
|Road network
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|-
 +
|LOS 1-17
 +
|Cycle network (segregated cycle  lanes, on-road shared with vehicles, on-path shared with pedestrians)
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|-
 +
|LOS 1-18
 +
|Pedestrian network and  accessibility facilities
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|-
 +
|
 +
|Framework data
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|-
 +
| style="font-weight:bold; background-color:#efefef;" |LOS 2
 +
! style="font-weight:bold; background-color:#efefef;" |Static data - Level of service  2
 +
!
 +
!
 +
!
 +
!in progress
 +
!
 +
!
 +
!
 +
!
 +
!
 +
!
 +
!
 +
!
 +
!
 +
!
 +
!
 +
!
 +
!
 +
|-
 +
|LOS 2-1
 +
| Park & Ride stops
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|-
 +
|LOS 2-2
 +
| Bike sharing stations
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|-
 +
|LOS 2-3
 +
|Car-sharing stations
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|-
 +
|LOS 2-4
 +
|Publicly accessible refuelling  stations for petrol, diesel, CNG/LNG, hydrogen powered vehicles, charging  stations for electric vehicles
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|Only charging stations for  electric vehicles
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|-
 +
|LOS 2-5
 +
|Secure bike parking (such as  locked bike garages)
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|-
 +
| LOS 2-6
 +
|Information service
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|-
 +
|LOS 2-7
 +
| Where and how to buy tickets for  scheduled modes, demand responsive modes and car parking (all scheduled modes  and demand-responsive incl. retail channels, fulfilment methods, payment  methods)
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|-
 +
|LOS 2-8
 +
|Trip plans, auxiliary  information, availability check
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|-
 +
|LOS 2-9
 +
|Basic common standard fares (all  scheduled modes)
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|-
 +
|LOS 2-10
 +
|Fare network data (fare  zones/stops and fare stages)
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|-
 +
|LOS 2-11
 +
|Standard fare structures (point  to point including daily and weekly fares, zonal fares, flat fares)
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|-
 +
|LOS 2-12
 +
|Vehicle facilities such as  classes of carriage, on-board Wi-Fi.
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|-
 +
| style="font-weight:bold; background-color:#efefef;" | LOS 3
 +
! style="font-weight:bold; background-color:#efefef;" |Static data - Level of service  3
 +
!
 +
!
 +
!
 +
!
 +
!
 +
!
 +
!
 +
!
 +
!
 +
!
 +
!
 +
!
 +
!
 +
!
 +
!
 +
!
 +
!
 +
|-
 +
|LOS 3-1
 +
|Passenger classes (classes of  user such as adult, child, student, veteran, impaired access and qualifying  conditions and classes of travel such as 1st, 2nd.)
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|-
 +
|LOS 3-2
 +
| Common fare products (access  rights such as zone/point-to-point including daily and weekly  tickets/single/return, eligibility of access, basic usage conditions such as  validity period/operator/time of travel/interchanging, standard point to  point fares prices for different point to point pairs including daily and  weekly fares/zonal fare prices/flat fare prices)
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|-
 +
|LOS 3-3
 +
| Special Fare Products: offers  with additional special conditions such as promotional fares, group fares,  season passes, aggregated products combining different products and add on  products such as parking and travel, minimum stay
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|-
 +
|LOS 3-4
 +
|Basic commercial conditions such  as refunding/replacing/exchanging/transferring and basic booking conditions  such as purchase windows, validity periods, routing restrictions zonal  sequence fares, minimum stay.
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|-
 +
|LOS 3-5
 +
|How to pay tolls (incl. retail  channels, fulfilment methods, payment methods)
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|-
 +
|LOS 3-6
 +
| How to book car sharing, taxis,  cycle hire etc. (incl. retail channels, fulfilment methods, payment methods)
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|-
 +
|LOS 3-7
 +
|Where how to pay for car  parking, public charging stations for electric vehicles and refuelling points  for CNG/LNG, hydrogen, petrol and diesel powered vehicles (incl. retail  channels, fulfilment methods, payment methods)
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|-
 +
|LOS 3-8
 +
| Detailed cycle network  attributes (surface quality, side-by-side cycling, shared surface, on/off  road, scenic route, ‘walk only’, turn or access restrictions (e.g. against  flow of traffic)
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|-
 +
|LOS 3-9
 +
|Parameters needed to calculate  an environmental factor such as carbon per vehicle type or passenger mile or  per distance walked
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|-
 +
|LOS 3-10
 +
|Parameters such as fuel  consumption needed to calculate cost
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|-
 +
|LOS 3-11
 +
|Estimated travel times by day  type and time-band by transport mode/combination of transport modes
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|[[File:compliant.png|15px|link=]]
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|-
 +
|
 +
!'''Links to the available documentation<ref>https://github.com/nick-knowles/NeTEx/wiki/NationalProfiles</ref>'''
 +
|
 +
|
 +
|
 +
|
 +
[https://arge-oevv.atlassian.net/wiki/spaces/NET/overview Austrian profile]
 +
|
 +
|
 +
|Denmark implements currently the [https://enturas.atlassian.net/wiki/spaces/PUBLIC/pages/728891481/Nordic+NeTEx+Profile Nordic Profile] and the EU profiles
 +
|
 +
*[http://www.normes-donnees-tc.org/format-dechange/donnees-theoriques/netex/ French Profile]
 +
*[http://www.normes-donnees-tc.org/wp-content/uploads/2021/01/Profil-NeTEx-elements-communsF-v2.2.pdf Common Profile]
 +
*[http://www.normes-donnees-tc.org/wp-content/uploads/2014/05/NF_Profil_NeTEx_pour_les_arrets-_F-_-_v2.pdf Stop Profile]
 +
*[http://www.normes-donnees-tc.org/wp-content/uploads/2019/11/NF_Profil-NeTEx-pour-les-R%C3%A9seauxF-v2.1.pdf Network Profile]
 +
*[http://www.normes-donnees-tc.org/wp-content/uploads/2019/11/NF&#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].
 +
 
 +
=NeTEx software / tools=
 
General purpose XML tools can be used to work with the NeTEx XML schema and XML documents that conform to it, for example either the proprietary [http://www.altova.com/xmlspy.html XML SPY] , or [http://www.oxygenxml.com/ Oxygen] or see free tools at http://www.garshol.priv.no/download/xmltools/. A wide variety of mainstream XML tools are available to validate XML and to create bindings to specific programming languages (.NET, Java, PHP, C++).<ref>http://netex-cen.eu/?page_id=258</ref>
 
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>
  
Line 35: Line 1,123:
 
==Conversion of NeTEx between other formats==
 
==Conversion of NeTEx between other formats==
 
{| class="wikitable"
 
{| class="wikitable"
−
!colspan="1"|Name
+
! colspan="1" | Name
−
!colspan="1"|Availability
+
! colspan="1" |Availability
−
!colspan="1"|Description
+
! colspan="1" |Description
−
!colspan="1"|Profile
+
! colspan="1" |Profile
−
!colspan="1"|License
+
! colspan="1" |License
−
!colspan="1"|URL
+
! colspan="1" |URL
 
|-
 
|-
−
!style="text-align:left;" rowspan="1"|[[netex-protobuf]]
+
! rowspan="1" style="text-align:left;" |[[netex-protobuf]]
 
|Available
 
|Available
 
|NeTEx to protobuf converter
 
|NeTEx to protobuf converter
Line 49: Line 1,137:
 
|https://github.com/entur/netex-protobuf
 
|https://github.com/entur/netex-protobuf
 
|-
 
|-
−
!style="text-align:left;" rowspan="1"|[[gtfs2netexfr]]
+
! rowspan="1" style="text-align:left;" |[[gtfs2netexfr]]
 
|Available
 
|Available
−
|Export GTFS data to NeTEx.
+
| Export GTFS data to NeTEx.
 
|French
 
|French
 
|
 
|
 
|https://github.com/CanalTP/transit_model/tree/master/gtfs2netexfr
 
|https://github.com/CanalTP/transit_model/tree/master/gtfs2netexfr
 
|-
 
|-
−
!style="text-align:left;" rowspan="1"|[[hastus]]
+
! rowspan="1" style="text-align:left;" |[[hastus]]
 
|Available
 
|Available
 
|Giro Hastus OIG script to export NeTEx from a system, in addition can export crew operations.
 
|Giro Hastus OIG script to export NeTEx from a system, in addition can export crew operations.
Line 63: Line 1,151:
 
|https://github.com/skinkie/hastus
 
|https://github.com/skinkie/hastus
 
|-
 
|-
−
!style="text-align:left;" rowspan="1"|[[josm-plugin-netex-converter]]
+
! rowspan="1" style="text-align:left;" |[[josm-plugin-netex-converter]]
 
|Available
 
|Available
 
|Export OpenStreetMap pedestrian routing information into NeTEx.
 
|Export OpenStreetMap pedestrian routing information into NeTEx.
 
|
 
|
−
|GPL 2.0
+
| GPL 2.0
 
|https://gitlab.com/labiangashi/josm-plugin-netex-converter/
 
|https://gitlab.com/labiangashi/josm-plugin-netex-converter/
 +
|-
 +
! rowspan="1" style="text-align:left;" |[[netex-gtfs-converter-java]]
 +
|Available
 +
|Export NeTEx data to GTFS
 +
|Nordic
 +
|EUPL
 +
|https://github.com/entur/netex-gtfs-converter-java
 
|-
 
|-
 
|}
 
|}
Line 74: Line 1,169:
 
==Data Validation tools==
 
==Data Validation tools==
 
{| class="wikitable"
 
{| class="wikitable"
−
!colspan="1"|Name
+
! colspan="1" |Name
−
!colspan="1"|Availability
+
! colspan="1" |Availability
−
!colspan="1"|Description
+
! colspan="1" | Description
−
!colspan="1"|Profile
+
! colspan="1" |Profile
−
!colspan="1"|License
+
! colspan="1" |License
−
!colspan="1"|URL
+
! colspan="1" |URL
 
|-
 
|-
−
!style="text-align:left;" rowspan="1"|[[XMLlint]]
+
! rowspan="1" style="text-align:left;" |[[XMLlint]]
 
|Available
 
|Available
 
|XML syntax validation, XSD schema validation and constraint checking.
 
|XML syntax validation, XSD schema validation and constraint checking.
Line 92: Line 1,187:
 
==Language bindings and software development aids==
 
==Language bindings and software development aids==
 
{| class="wikitable"
 
{| class="wikitable"
−
!colspan="6"|NeTEx XML bindings
+
! colspan="6" |NeTEx XML bindings
 
|-
 
|-
−
!colspan="1"|Name
+
! colspan="1" |Name
−
!colspan="1"|Availability
+
! colspan="1" |Availability
−
!colspan="1"|Description
+
! colspan="1" |Description
−
!colspan="1"|Profile
+
! colspan="1" | Profile
−
!colspan="1"|License
+
! colspan="1" |License
−
!colspan="1"|URL
+
! colspan="1" |URL
 
|-
 
|-
−
!style="text-align:left;" rowspan="1"|[[netex-java-model]]
+
! rowspan="1" style="text-align:left;" |[[netex-java-model]]
−
|Available
+
| Available
 
|NeTEx XML bindings for Java, with additions to map temporal types to native objects.
 
|NeTEx XML bindings for Java, with additions to map temporal types to native objects.
 
|Any
 
|Any
Line 108: Line 1,203:
 
|https://github.com/entur/netex-java-model
 
|https://github.com/entur/netex-java-model
 
|-
 
|-
−
!style="text-align:left;" rowspan="1"|[[netex-csharp-model]]
+
! rowspan="1" style="text-align:left;" |[[netex-csharp-model]]
 
|Not Available
 
|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.
 
|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.
Line 114: Line 1,209:
 
|
 
|
 
|
 
|
 +
|-
 +
! 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
 
|-
 
|-
 
|}
 
|}
Line 119: Line 1,221:
 
==Editing /Management  & visualisation tools for  NeTEx data==
 
==Editing /Management  & visualisation tools for  NeTEx data==
 
{| class="wikitable"
 
{| class="wikitable"
−
!colspan="1"|Name
+
! colspan="1" |Name
−
!colspan="1"|Availability
+
! colspan="1" |Availability
−
!colspan="1"|Description
+
! colspan="1" |Description
−
!colspan="1"|Profile
+
! colspan="1" |Profile
−
!colspan="1"|License
+
! colspan="1" |License
−
!colspan="1"|URL
+
! colspan="1" | URL
 
|-
 
|-
−
!style="text-align:left;" rowspan="1"|[[Chouette|Nplan]]
+
! rowspan="1" style="text-align:left;" |[[Chouette|Nplan]]
 
|Available
 
|Available
 
|Java backend / TypeScript frontend for create/edit/export of NeTEx data (Support both Timetable based and On-demand polygon based services)
 
|Java backend / TypeScript frontend for create/edit/export of NeTEx data (Support both Timetable based and On-demand polygon based services)
Line 134: Line 1,236:
 
frontend - https://github.com/entur/enki
 
frontend - https://github.com/entur/enki
 
|-
 
|-
−
!style="text-align:left;" rowspan="1"|[[NSR]]
+
! rowspan="1" style="text-align:left;" |[[NSR]]
−
|Available
+
| 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)
 
|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
 
|Nordic
Line 142: Line 1,244:
 
frontend - https://github.com/entur/abzu
 
frontend - https://github.com/entur/abzu
 
|-
 
|-
−
!style="text-align:left;" rowspan="1"|[[Chouette]]
+
! rowspan="1" style="text-align:left;" |[[Chouette]]
 
|Available
 
|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
 
|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
Line 150: Line 1,252:
 
frontend -  https://github.com/entur/chouette2
 
frontend -  https://github.com/entur/chouette2
 
|-
 
|-
−
!style="text-align:left;" rowspan="1"|[[Chouette]]
+
! rowspan="1" style="text-align:left;" |[[Chouette]]
 
|Available
 
|Available
 
|Java based NeTEx tools, transforms between profiles and standards (NeTEx, GTFS, Neptune).
 
|Java based NeTEx tools, transforms between profiles and standards (NeTEx, GTFS, Neptune).
Line 157: Line 1,259:
 
|https://enroute.mobi/produits/chouette/
 
|https://enroute.mobi/produits/chouette/
 
|-
 
|-
−
!style="text-align:left;" rowspan="1"|[[mobilitx]]
+
! rowspan="1" style="text-align:left;" |[[mobilitx]]
−
|Available
+
| Available
 
|
 
|
 
|
 
|
Line 164: Line 1,266:
 
|https://mobilitx.diginext.fr/
 
|https://mobilitx.diginext.fr/
 
|-
 
|-
−
!style="text-align:left;" rowspan="1"|[[mobiref]]
+
! rowspan="1" style="text-align:left;" |[[mobiref]]
 
|Available
 
|Available
 
|
 
|
Line 171: Line 1,273:
 
|https://www.lumiplan.com/produit/mobiref/
 
|https://www.lumiplan.com/produit/mobiref/
 
|-
 
|-
−
!style="text-align:left;" rowspan="1"|[[NeTEx Reader]]
+
! rowspan="1" style="text-align:left;" |[[NeTEx Reader]]
−
|In Development
+
| In Development
 
|C# based XML tool, based on Giro Hastus XSD.
 
|C# based XML tool, based on Giro Hastus XSD.
 
|Dutch
 
|Dutch
Line 178: Line 1,280:
 
|https://www.youtube.com/watch?v=mpb_1Y9uR5k
 
|https://www.youtube.com/watch?v=mpb_1Y9uR5k
 
|-
 
|-
−
!style="text-align:left;" rowspan="1"|[[netexconv2]]
+
! rowspan="1" style="text-align:left;" |[[netexconv2]]
 
|In Development
 
|In Development
 
|Java based NeTEx tools, transforms between profiles and standards (NeTEx, DINO, HAFAS, KV1, GTFS).
 
|Java based NeTEx tools, transforms between profiles and standards (NeTEx, DINO, HAFAS, KV1, GTFS).
Line 185: Line 1,287:
 
|
 
|
 
|-
 
|-
−
!style="text-align:left;" rowspan="1"|[[IVU.cloud]]
+
! rowspan="1" style="text-align:left;" |[[IVU.cloud]]
 
|Available
 
|Available
 
|
 
|
Line 191: Line 1,293:
 
|
 
|
 
|https://www.ivu.com/news/news/article/delfi-successfully-migrates-to-ivucloud.html
 
|https://www.ivu.com/news/news/article/delfi-successfully-migrates-to-ivucloud.html
 +
|-
 +
! rowspan="1" style="text-align:left;" |[[Motus]]
 +
|Available
 +
|Motus is the Fleet Scheduling Management System provided by Pluservice. The application is designed by independent and integrated modules which can be activated according to specific operational needs.
 +
 +
One of the latest module created and already available is the generation of NeTEx datasets starting from the operational data collected by public transport operators. For this purpose, Motus receives the input data starting from a GTFS and it is able to enrich  these data with further relevant information such as contracts, vehicles. Then Motus transforms these data into the NeTEx Italian profile.
 +
 +
'''Data model:''' the database is designed according to Transmodel specifications, European reference standard (EN12896) for public  transport.
 +
|Italian
 +
|
 +
|https://www.pluservice.net/it/soluzioni/gestione-rete-e-turni
 
|-
 
|-
 
|}
 
|}
Line 196: Line 1,309:
 
==NeTEx data enabled==
 
==NeTEx data enabled==
 
{| class="wikitable"
 
{| class="wikitable"
−
!colspan="1"|Name
+
! colspan="1" |Name
−
!colspan="1"|Availability
+
! colspan="1" |Availability
−
!colspan="1"|Description
+
! colspan="1" | Description
−
!colspan="1"|Profile
+
! colspan="1" |Profile
−
!colspan="1"|License
+
! colspan="1" |License
−
!colspan="1"|URL
+
! colspan="1" |URL
 
|-
 
|-
−
!style="text-align:left;" rowspan="1"|[[OpenTripPlanner]]
+
! rowspan="1" style="text-align:left;" |[[OpenTripPlanner]]
−
|Available
+
| Available
 
|Timetable and shortest path journey planner supporting reading various input formats including GTFS and NeTEx.
 
|Timetable and shortest path journey planner supporting reading various input formats including GTFS and NeTEx.
−
|Nordic
+
| Nordic
−
|Apache 2.0
+
| Apache 2.0
 
|http://docs.opentripplanner.org/en/dev-2.x/Netex-Norway/
 
|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"
 
!Name
 
!Name
Line 222: Line 1,335:
 
|Available
 
|Available
 
|Planning system from Giro for public transport
 
|Planning system from Giro for public transport
−
|Nordic
+
| Nordic
 
|-
 
|-
 
! rowspan="1" style="text-align:left;" |[[Trapeze Cloud TP10|Trapeze]]
 
! rowspan="1" style="text-align:left;" |[[Trapeze Cloud TP10|Trapeze]]
 
|Available
 
|Available
−
| Planning system from Trapeze for public transport
+
|Planning system from Trapeze for public transport
 
|Nordic
 
|Nordic
 
|-
 
|-
 
! rowspan="1" style="text-align:left;" |[[DG Buss]]
 
! rowspan="1" style="text-align:left;" |[[DG Buss]]
 
|Available
 
|Available
−
| Planning system from Datagrafikk for public transport
+
|Planning system from Datagrafikk for public transport
 
|Nordic
 
|Nordic
 
|-
 
|-
 
! rowspan="1" style="text-align:left;" |[[Train Plan]]
 
! rowspan="1" style="text-align:left;" |[[Train Plan]]
 
|Available
 
|Available
−
| Planning system from Trapeze for railway
+
|Planning system from Trapeze for railway
 
|Nordic
 
|Nordic
 
|-
 
|-
 
! rowspan="1" style="text-align:left;" |[[IVU]]
 
! rowspan="1" style="text-align:left;" |[[IVU]]
 
|In development
 
|In development
−
| Planning system from IVU for public transport
+
|Planning system from IVU for public transport
 
|Nordic
 
|Nordic
 
|-
 
|-
 
! rowspan="1" style="text-align:left;" |[[IVU]]
 
! rowspan="1" style="text-align:left;" |[[IVU]]
 
|In development
 
|In development
−
| Planning system from IVU for railway
+
|Planning system from IVU for railway
 
|Nordic
 
|Nordic
 
|-
 
|-
Line 264: Line 1,377:
 
|Nordic
 
|Nordic
 
|}
 
|}
 +
 +
= NeTEx Part 5 for New Modes =
 +
The NeTEx extension for New Modes addresses the development of a data exchange format dedicated to the publication of data concerning ‘Alternative Modes’ (as requested in EU COMMISSION DELEGATED REGULATION (EU) 2017/1926 of 31 May 2017). This work will generate NeTEx Part 5 focusing on (but not a limitation to) car sharing, cycle sharing, carpooling, car/cycle rental. It is primarily oriented towards static data (describing the service that is offered and associated infrastructure, more than its current running status). The corresponding real-time information is provided by SIRI. More information can be found in [https://netex-cen.eu/?page_id=534 NeTEx website].'''''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).
 +
 +
== Technical artefacts ==
 +
The XML schema (XSD) for NeTEx Part 5 New Modes is available in [https://github.com/NeTEx-CEN/NeTEx/tree/new-modes GitHub]. In this NeTEx - CEN GitHub channel, examples are also provided, along with other useful documentation.
 +
 +
== Canonical mapping with GBFS ==
 +
Preceding the publication of the extension of the Network Timetable Exchange (NeTEx) for ‘new modes’, the EU-funded project DATA4PT and MobilityData experts release the high-level mapping between the General Bikeshare Feed Specification (GBFS) and Transmodel in order to support better interoperability of shared mobility data feeds. The mapping report is available [[Media:Canonical mapping - NeTEx and SIRI new modes with GBFS.pdf|here]]. 
 +
 +
= References =
 +
<references />

Revision as of 18:53, 16 March 2022

NeTEx overview

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

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

NeTEx is intended to be a general purpose XML format, designed for the efficient, updateable exchange of complex transport data among distributed systems. This allows the data to be used in modern web services architectures and to support a wide range of passenger information and operational applications.

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

NeTEx-Light

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

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.
Graphic and interactive technical presentation NeTEx XSD for EPIP


NeTEx national and EU minimum profiles inventory

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

*Data categories are identified based on MMTIS EU Regulation 1926/2017

** European Passenger Information Profile

*** European Passenger Information Accessibility Profile

Functional scope per profile
Profiles Full NeTEx format EPIP** EPIAP*** Austria Croatia Czech Republic Denmark France Italy Netherlands Nordic (Norway, Sweden, Finland, Denmark currently) Portugal Slovenija Switzerland UK Irish German
VDV
Availability of NeTEx national profile under development Specified but not yet in operation not yet specified not yet specified not yet specified Specified and partially in operation Specified but not yet in operation specified but not yet in operation Specified and in use Specified and in use specified but not yet in operation in progress Specified and in use specified
NeTEx EPIP based Compliant.png Compliant.png
NeTEx EPIP compatible Compliant.png Compliant.png Compliant.png Compliant.png Compliant.png
Available mappings with full NeTEx profile VDV NeTEx page
Available mappings with EPIP profile
Data categories
LOS 1 Static data - Level of service 1
LOS 1-1 Address identifiers (building number, street name, postcode) Compliant.png Compliant.png Compliant.png Compliant.png
LOS 1-2 Topographic places (city, town, village, suburb, administrative unit) Compliant.png Compliant.png Compliant.png Compliant.png Compliant.png
LOS 1-3 Points of interest (related to transport information) to which people may wish to travel Compliant.png Compliant.png Compliant.png Compliant.png
LOS 1-4 Operational Calendar, mapping day types to calendar dates Compliant.png Compliant.png Compliant.png Compliant.png Compliant.png Compliant.png
LOS 1-5 Identified access nodes (all scheduled modes) Compliant.png Compliant.png Compliant.png Compliant.png Compliant.png
LOS 1-6 Geometry/map layout structure of access nodes (all scheduled modes) Compliant.png Compliant.png Compliant.png Compliant.png Compliant.png
LOS 1-7 Connection links where interchanges may be made, default transfer times between modes at interchanges Compliant.png Compliant.png Compliant.png Compliant.png Compliant.png
LOS 1-8 Network topology and routes/lines (topology) Compliant.png Compliant.png Compliant.png Compliant.png Compliant.png Compliant.png Compliant.png Compliant.png Compliant.png Compliant.png
LOS 1-9 Transport operators Compliant.png Compliant.png Compliant.png Compliant.png Compliant.png Compliant.png Compliant.png Compliant.png Compliant.png
LOS 1-10 Timetables Compliant.png Compliant.png Compliant.png Compliant.png Compliant.png Compliant.png Compliant.png Compliant.png Compliant.png Compliant.png
LOS 1-11 Planned interchanges between guaranteed scheduled services Compliant.png Compliant.png Compliant.png Compliant.png For connection links we use journeyplanner based on OSM map data, road, cycle and pedestrian network is based on OpenStreetMap Compliant.png Compliant.png
LOS 1-12 Hours of operation Compliant.png Compliant.png Compliant.png Compliant.png Compliant.png
LOS 1-13 Vehicles (low floor; wheelchair accessible.) Compliant.png Compliant.png Compliant.png Compliant.png Compliant.png Compliant.png
LOS 1-14 Accessibility of access nodes, and paths within an interchange (such as existence of lifts, escalators) Compliant.png Compliant.png Compliant.png Compliant.png Compliant.png
LOS 1-15 Existence of assistance services (such as existence of on-site assistance) Compliant.png Compliant.png Compliant.png Compliant.png
LOS 1-16 Road network Compliant.png Compliant.png Compliant.png
LOS 1-17 Cycle network (segregated cycle lanes, on-road shared with vehicles, on-path shared with pedestrians) Compliant.png Compliant.png Compliant.png
LOS 1-18 Pedestrian network and accessibility facilities Compliant.png Compliant.png Compliant.png
Framework data Compliant.png Compliant.png
LOS 2 Static data - Level of service 2 in progress
LOS 2-1 Park & Ride stops Compliant.png Compliant.png Compliant.png Compliant.png
LOS 2-2 Bike sharing stations Compliant.png Compliant.png Compliant.png Compliant.png
LOS 2-3 Car-sharing stations Compliant.png Compliant.png Compliant.png Compliant.png
LOS 2-4 Publicly accessible refuelling stations for petrol, diesel, CNG/LNG, hydrogen powered vehicles, charging stations for electric vehicles Compliant.png Only charging stations for electric vehicles Compliant.png
LOS 2-5 Secure bike parking (such as locked bike garages) Compliant.png Compliant.png Compliant.png Compliant.png
LOS 2-6 Information service Compliant.png Compliant.png Compliant.png Compliant.png
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) Compliant.png Compliant.png Compliant.png Compliant.png
LOS 2-8 Trip plans, auxiliary information, availability check Compliant.png Compliant.png Compliant.png Compliant.png
LOS 2-9 Basic common standard fares (all scheduled modes) Compliant.png Compliant.png Compliant.png Compliant.png Compliant.png Compliant.png
LOS 2-10 Fare network data (fare zones/stops and fare stages) Compliant.png Compliant.png Compliant.png Compliant.png Compliant.png
LOS 2-11 Standard fare structures (point to point including daily and weekly fares, zonal fares, flat fares) Compliant.png Compliant.png Compliant.png Compliant.png Compliant.png
LOS 2-12 Vehicle facilities such as classes of carriage, on-board Wi-Fi. Compliant.png Compliant.png Compliant.png Compliant.png Compliant.png
LOS 3 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.) Compliant.png Compliant.png Compliant.png Compliant.png
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) Compliant.png Compliant.png Compliant.png Compliant.png
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 Compliant.png Compliant.png Compliant.png Compliant.png
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. Compliant.png Compliant.png Compliant.png
LOS 3-5 How to pay tolls (incl. retail channels, fulfilment methods, payment methods) Compliant.png Compliant.png
LOS 3-6 How to book car sharing, taxis, cycle hire etc. (incl. retail channels, fulfilment methods, payment methods) Compliant.png
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) Compliant.png Compliant.png
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) Compliant.png Compliant.png
LOS 3-9 Parameters needed to calculate an environmental factor such as carbon per vehicle type or passenger mile or per distance walked Compliant.png Compliant.png
LOS 3-10 Parameters such as fuel consumption needed to calculate cost Compliant.png Compliant.png
LOS 3-11 Estimated travel times by day type and time-band by transport mode/combination of transport modes Compliant.png Compliant.png
Links to the available documentation[1]

Austrian profile

Denmark implements currently the Nordic Profile and the EU profiles

Italian Profile

Nordic Profile

Portuguese Profile

Slovenian Profile

Swiss profile - Work In progress

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

NeTEx software / tools

General purpose XML tools can be used to work with the NeTEx XML schema and XML documents that conform to it, for example either the proprietary XML SPY , or 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++).[2]

To look at the design models, an interactive UML viewer such as 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.[3]

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

Name Availability Description Profile License URL
netex-protobuf Available NeTEx to protobuf converter all EUPL https://github.com/entur/netex-protobuf
gtfs2netexfr Available Export GTFS data to NeTEx. French https://github.com/CanalTP/transit_model/tree/master/gtfs2netexfr
hastus Available Giro Hastus OIG script to export NeTEx from a system, in addition can export crew operations. Dutch, Nordic(?) AGPL-3.0 https://github.com/skinkie/hastus
josm-plugin-netex-converter Available Export OpenStreetMap pedestrian routing information into NeTEx. GPL 2.0 https://gitlab.com/labiangashi/josm-plugin-netex-converter/
netex-gtfs-converter-java Available Export NeTEx data to GTFS Nordic EUPL https://github.com/entur/netex-gtfs-converter-java

Data Validation tools

Name Availability Description Profile License URL
XMLlint Available XML syntax validation, XSD schema validation and constraint checking. All MIT http://www.xmlsoft.org/

Language bindings and software development aids

NeTEx XML bindings
Name Availability Description Profile License URL
netex-java-model Available NeTEx XML bindings for Java, with additions to map temporal types to native objects. Any EUPL https://github.com/entur/netex-java-model
netex-csharp-model Not Available NeTEx XML bindings for C#. Currently being researched with a variety of tools.
Contact DATA4PT if you have questions or have found the golden egg. 		Any
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

Name Availability Description Profile License URL
Nplan Available Java backend / TypeScript frontend for create/edit/export of NeTEx data (Support both Timetable based and On-demand polygon based services) Nordic EUPL backend - https://github.com/entur/uttu

frontend - https://github.com/entur/enki

NSR Available Java backend / JavaScript frontend for import/creation/edit/export for NeTEx stops data. (Act as a National Stops Register for the whole of Norway) Nordic EUPL backend - https://github.com/entur/tiamat

frontend - https://github.com/entur/abzu

Chouette Available Java backend / Ruby frontend for import/validation/edit/export of NeTEx data. Highly modified version of the old AFIMB version of Chouette. NOTE: Legacy software not recommended for new implemetations Nordic CeCILL-B backend - https://github.com/entur/chouette

frontend - https://github.com/entur/chouette2

Chouette Available Java based NeTEx tools, transforms between profiles and standards (NeTEx, GTFS, Neptune). EPIP Apache 2.0 https://enroute.mobi/produits/chouette/
mobilitx Available https://mobilitx.diginext.fr/
mobiref Available https://www.lumiplan.com/produit/mobiref/
NeTEx Reader In Development C# based XML tool, based on Giro Hastus XSD. Dutch https://www.youtube.com/watch?v=mpb_1Y9uR5k
netexconv2 In Development Java based NeTEx tools, transforms between profiles and standards (NeTEx, DINO, HAFAS, KV1, GTFS). Dutch, EPIP, Nordic, VDV462
IVU.cloud Available EPIP https://www.ivu.com/news/news/article/delfi-successfully-migrates-to-ivucloud.html
Motus Available Motus is the Fleet Scheduling Management System provided by Pluservice. The application is designed by independent and integrated modules which can be activated according to specific operational needs.

One of the latest module created and already available is the generation of NeTEx datasets starting from the operational data collected by public transport operators. For this purpose, Motus receives the input data starting from a GTFS and it is able to enrich these data with further relevant information such as contracts, vehicles. Then Motus transforms these data into the NeTEx Italian profile.

Data model: the database is designed according to Transmodel specifications, European reference standard (EN12896) for public transport.

Italian https://www.pluservice.net/it/soluzioni/gestione-rete-e-turni

NeTEx data enabled

Name Availability Description Profile License URL
OpenTripPlanner Available Timetable and shortest path journey planner supporting reading various input formats including GTFS and NeTEx. Nordic Apache 2.0 http://docs.opentripplanner.org/en/dev-2.x/Netex-Norway/

Planning system supporting native NeTEx export

Name Availability Description Profile
Hastus Available Planning system from Giro for public transport Nordic
Trapeze Available Planning system from Trapeze for public transport Nordic
DG Buss Available Planning system from Datagrafikk for public transport Nordic
Train Plan Available Planning system from Trapeze for railway Nordic
IVU In development Planning system from IVU for public transport Nordic
IVU In development Planning system from IVU for railway Nordic
Turnit Available Planning system from Turnit for public transport Nordic
Nplan Available Planning system from Entur for public transport Nordic
TPSI Available Planning system from HaCon for railway Nordic

NeTEx Part 5 for New Modes

The NeTEx extension for New Modes addresses the development of a data exchange format dedicated to the publication of data concerning ‘Alternative Modes’ (as requested in EU COMMISSION DELEGATED REGULATION (EU) 2017/1926 of 31 May 2017). This work will generate NeTEx Part 5 focusing on (but not a limitation to) car sharing, cycle sharing, carpooling, car/cycle rental. It is primarily oriented towards static data (describing the service that is offered and associated infrastructure, more than its current running status). The corresponding real-time information is provided by SIRI. More information can be found in 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).

Technical artefacts

The XML schema (XSD) for NeTEx Part 5 New Modes is available in GitHub. In this NeTEx - CEN GitHub channel, examples are also provided, along with other useful documentation.

Canonical mapping with GBFS

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

References

  1. ↑ https://github.com/nick-knowles/NeTEx/wiki/NationalProfiles
  2. ↑ http://netex-cen.eu/?page_id=258
  3. ↑ http://netex-cen.eu/?page_id=258
Retrieved from "https://data4pt.org/w/index.php?title=NeTEX&oldid=259"