DATA4PT WIKI - User contributions [en]

NeTEX

2021-12-17T13:36:52Z

Aurige: updates for France

= NeTEx overview =
[[File:NeTEx.png|250px|right|link=http://netex-cen.eu/|alt=]]

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

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

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

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

=NeTEx-Light =
The normative NeTEx schema could be considered very big and extensive. Code generation tools for C# have difficulties with processing it. In order to use NeTEx within C# this derived XSD was created. This schema should be used informative, for application development, but not for validation purposes. This schema has been reduced to only match the scope of the EPIP Profile (European Passenger Information Profile) but remains compliant with the main NeTEx Schema.

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

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

= National profiles =
A number of National and international profiles have already been defined for different European countries and more are under development. In the following table, DATA4PT provides an overview of the key characteristics of the national profiles per country, including the data categories that are currently covered by each one of the profiles. The table will be continuously update following new implementations.

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

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

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

{| class="wikitable sortable zebra" style="padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;border-spacing:0;text-align:center; "
|-
! colspan="2" style="text-align:center; min-width: 100px; max-width: 150px;" |PROFILES
! style="width: 80px;" |Full NeTEx format
! style="width: 80px;" |EPIP**
! style="width: 80px;" |EPIAP***
! style="width: 80px;" |Austria
! style="width: 80px;" |Croatia
! style="width: 80px;" |Czech Republic
! style="width: 80px;" |Denmark
! style="width: 80px;" |France
! style="width: 80px;" |Italy
! style="width: 80px;" | Netherlands
! style="width: 80px;" |Nordic (Norway, Sweden, Finland, Denmark currently)
! style="width: 80px;" |Portugal
! style="width: 80px;" |Slovenija
! style="width: 80px;" |Switzerland
! style="width: 80px;" |UK
! style="width: 80px;" |Irish
! style="width: 80px;" | German VDV
|-
| colspan="2" |Availability of NeTEx national profile
!
!
!under development
|Specified but not yet in operation
| not yet specified
|not yet specified
|not yet specified
|Specified and partially in operation
|Specified but not yet in operation
| specified but not yet in operation
|Specified and in use
| Specified and in use
|specified but not yet in operation
|in progress
|Specified and in use
| specified
|
|-
| colspan="2" |NeTEx EPIP based
!
!
!
|[[File:compliant.png|15px|link=]]
|
|
|
|
|[[File:compliant.png|15px|link=]]
|
|
|
|
|
|[[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" |Functional scope based on MMTIS EU Regulation 1926/2017
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
|-
| style="font-weight:bold; background-color:#efefef;" |LOS 1
| style="font-weight:bold; background-color:#efefef;" |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=]]
|
|
|
|
|
|
|}

If you believe that your use cases are resolved in an existing profile, it is highly recommended to adopt an existing solution and cooperate with the corresponding entity. You will save resources while you will ensure that your profile is interoperable. It follows a list with links to the relevant documentation for each one the available profiles <ref>https://github.com/nick-knowles/NeTEx/wiki/NationalProfiles</ref>, where you can also find contact details for some of the entities responsible for the profiles. Otherwise you can contact us in [https://data4pt-project.eu/requests-requirements/ DATA4PT].

*ch : [https://transportdatamanagement.ch/en/standards/ Swiss profile - Work In progress.]
**[https://transportdatamanagement.ch/content/uploads/2020/11/NeTEx_Core-Realisation_Guide_TP_Suisse-v0.8.8.4.pdf Realisation directive]
*de : [https://www.vdv.de/oepnv-datenmodell.en.aspx German Profile].
**[https://www.vdv.de/vdv-462-netex-recommendation-v00-22-english.pdfx VDV462].
*dk : Denmark implements [https://enturas.atlassian.net/wiki/spaces/PUBLIC/pages/728891481/Nordic+NeTEx+Profile Nordic Profile] and the EU profiles.
*eu : Europe - Passenger Information Profile (Timetables) ([[NeTEX#NeTEx-Light and NeTEx EPIP|above]]). There is work in progress on European Accessibility Profile (EPIAP) lead by DATA4PT project. To be delivered in the 1st quarter of 2022.
*fi : Finland - [https://enturas.atlassian.net/wiki/spaces/PUBLIC/pages/728891481/Nordic+NeTEx+Profile Nordic Profile] .
*fr : [http://www.normes-donnees-tc.org/format-dechange/donnees-theoriques/netex/ French Profile].
**[http://www.normes-donnees-tc.org/wp-content/uploads/2021/01/Profil-NeTEx-elements-communsF-v2.2.pdf Common Profile specification].
**[http://www.normes-donnees-tc.org/wp-content/uploads/2014/05/NF_Profil_NeTEx_pour_les_arrets-_F-_-_v2.pdf Stop Profile specification].
**[http://www.normes-donnees-tc.org/wp-content/uploads/2019/11/NF_Profil-NeTEx-pour-les-R%C3%A9seauxF-v2.1.pdf Network Profile specification].
**[http://www.normes-donnees-tc.org/wp-content/uploads/2019/11/NF_Profil-NeTEx-pour-les-HorairesF-v2.1.pdf Timetable Profile specification].
**[http://www.normes-donnees-tc.org/wp-content/uploads/2021/11/NF_Profil-NeTEx-pour-les-TarifsF-v1.2.pdf Fare Profile].
**[http://www.normes-donnees-tc.org/wp-content/uploads/2021/10/NF_Profil-NeTEx-pour-les-ParkingsF-v1.2a.pdf Parking Profile].
**[http://www.normes-donnees-tc.org/wp-content/uploads/2021/01/Profil-NeTEx-pour-laccessibiliteF-v2.2.pdf Accessibility Profile].
*ie : [http://netex.ie/ Irish Profile].
**[http://netex.uk/netexie/doc/EIRE_NP/NTA-NeTEx-1-Spec-2020.08.12-v0.22.pdf Profile Elements].
**[http://netex.uk/netexie/doc/EIRE_NP/NTA-NeTEx-2-Mappings-2020.08.06-v0.22.pdf Profile Data Mappings]
*it : [http://netex-cen.eu/?page_id=237 Italian Profile]
*nl : [https://bison.dova.nu/standaarden/nederlands-netex-profiel Netherlands profile].
**Profile specification.
**[https://bison.dova.nu/sites/default/files/bison_prijzen_producten_en_tarieven_v8.1.3.0_release.pdf Bison Fares].
*no : [https://enturas.atlassian.net/wiki/spaces/PUBLIC/pages/728891481/Nordic+NeTEx+Profile Norway - Nordic Profile].
* pt : [https://ptprofiles.azurewebsites.net/netex-profile Portuguese Profile]
*se : [https://enturas.atlassian.net/wiki/spaces/PUBLIC/pages/728891481/Nordic+NeTEx+Profile Sweden - Nordic Profile].
*si : [https://www.nap.si/_resources/profiles/NeTEx_SI_Profile_v2.pdf Slovenian Profile]
*uk : [http://netex.uk/farexchange/ UK Profile (FareExchange].
**[http://netex.uk/farexchange/doc/uk_profile/DfT-NeTEx-1-Fares-Intro-2019.06.17-v0.09.pdf Introduction].
**[http://netex.uk/farexchange/doc/uk_profile/DfT-NeTEx-2-Base_Spec-2019.06.30-v0.14.pdf Stops and Timetables].
**[http://netex.uk/farexchange/doc/uk_profile/DfT-NeTEx-3-Fares_Spec-2019.06.17-v0.17.pdf Fares].

=NeTEx software / tools=
General purpose XML tools can be used to work with the NeTEx XML schema and XML documents that conform to it, for example either the proprietary [http://www.altova.com/xmlspy.html XML SPY] , or [http://www.oxygenxml.com/ Oxygen] or see free tools at http://www.garshol.priv.no/download/xmltools/. A wide variety of mainstream XML tools are available to validate XML and to create bindings to specific programming languages (.NET, Java, PHP, C++).<ref>http://netex-cen.eu/?page_id=258</ref>

To look at the design models, an interactive UML viewer such as [http://www.sparxsystems.com/ Enterprise Architect] is extremely helpful, although a set of static web pages is also available. Sample mappings to a variety of national formats (VDV, BISON, etc) as well as GTFS have been developed and are included in the NeTEx standard.<ref>http://netex-cen.eu/?page_id=258</ref>

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

==Conversion of NeTEx between other formats==
{| class="wikitable"
! colspan="1" | Name
! colspan="1" |Availability
! colspan="1" |Description
! colspan="1" |Profile
! colspan="1" |License
! colspan="1" |URL
|-
! rowspan="1" style="text-align:left;" |[[netex-protobuf]]
|Available
|NeTEx to protobuf converter
|all
|EUPL
|https://github.com/entur/netex-protobuf
|-
! rowspan="1" style="text-align:left;" |[[gtfs2netexfr]]
|Available
| Export GTFS data to NeTEx.
|French
|
|https://github.com/CanalTP/transit_model/tree/master/gtfs2netexfr
|-
! rowspan="1" style="text-align:left;" |[[hastus]]
|Available
|Giro Hastus OIG script to export NeTEx from a system, in addition can export crew operations.
|Dutch, Nordic(?)
|AGPL-3.0
|https://github.com/skinkie/hastus
|-
! rowspan="1" style="text-align:left;" |[[josm-plugin-netex-converter]]
|Available
|Export OpenStreetMap pedestrian routing information into NeTEx.
|
| GPL 2.0
|https://gitlab.com/labiangashi/josm-plugin-netex-converter/
|-
|}

==Data Validation tools==
{| class="wikitable"
! colspan="1" |Name
! colspan="1" |Availability
! colspan="1" | Description
! colspan="1" |Profile
! colspan="1" |License
! colspan="1" |URL
|-
! rowspan="1" style="text-align:left;" |[[XMLlint]]
|Available
|XML syntax validation, XSD schema validation and constraint checking.
|All
|MIT
|http://www.xmlsoft.org/
|-
|}

==Language bindings and software development aids==
{| class="wikitable"
! colspan="6" |NeTEx XML bindings
|-
! colspan="1" |Name
! colspan="1" |Availability
! colspan="1" |Description
! colspan="1" | Profile
! colspan="1" |License
! colspan="1" |URL
|-
! rowspan="1" style="text-align:left;" |[[netex-java-model]]
| Available
|NeTEx XML bindings for Java, with additions to map temporal types to native objects.
|Any
|EUPL
|https://github.com/entur/netex-java-model
|-
! rowspan="1" style="text-align:left;" |[[netex-csharp-model]]
|Not Available
|NeTEx XML bindings for C#. Currently being researched with a variety of tools. Contact DATA4PT if you have questions or have found the golden egg.
|Any
|
|
|-
|}

==Editing /Management & visualisation tools for NeTEx data==
{| class="wikitable"
! colspan="1" |Name
! colspan="1" |Availability
! colspan="1" |Description
! colspan="1" |Profile
! colspan="1" |License
! colspan="1" | URL
|-
! rowspan="1" style="text-align:left;" |[[Chouette|Nplan]]
|Available
|Java backend / TypeScript frontend for create/edit/export of NeTEx data (Support both Timetable based and On-demand polygon based services)
|Nordic
|EUPL
|backend - https://github.com/entur/uttu
frontend - https://github.com/entur/enki
|-
! rowspan="1" style="text-align:left;" |[[NSR]]
| Available
|Java backend / JavaScript frontend for import/creation/edit/export for NeTEx stops data. (Act as a National Stops Register for the whole of Norway)
|Nordic
|EUPL
|backend - https://github.com/entur/tiamat
frontend - https://github.com/entur/abzu
|-
! rowspan="1" style="text-align:left;" |[[Chouette]]
|Available
|Java backend / Ruby frontend for import/validation/edit/export of NeTEx data. Highly modified version of the old AFIMB version of Chouette. NOTE: Legacy software not recommended for new implemetations
|Nordic
|CeCILL-B
|backend - https://github.com/entur/chouette
frontend - https://github.com/entur/chouette2
|-
! rowspan="1" style="text-align:left;" |[[Chouette]]
|Available
|Java based NeTEx tools, transforms between profiles and standards (NeTEx, GTFS, Neptune).
|EPIP
|Apache 2.0
|https://enroute.mobi/produits/chouette/
|-
! rowspan="1" style="text-align:left;" |[[mobilitx]]
| Available
|
|
|
|https://mobilitx.diginext.fr/
|-
! rowspan="1" style="text-align:left;" |[[mobiref]]
|Available
|
|
|
|https://www.lumiplan.com/produit/mobiref/
|-
! rowspan="1" style="text-align:left;" |[[NeTEx Reader]]
| In Development
|C# based XML tool, based on Giro Hastus XSD.
|Dutch
|
|https://www.youtube.com/watch?v=mpb_1Y9uR5k
|-
! rowspan="1" style="text-align:left;" |[[netexconv2]]
|In Development
|Java based NeTEx tools, transforms between profiles and standards (NeTEx, DINO, HAFAS, KV1, GTFS).
|Dutch, EPIP, Nordic, VDV462
|
|
|-
! rowspan="1" style="text-align:left;" |[[IVU.cloud]]
|Available
|
|EPIP
|
|https://www.ivu.com/news/news/article/delfi-successfully-migrates-to-ivucloud.html
|-
|'''Motus'''
|Available
|Motus is the Fleet Scheduling Management System provided by Pluservice. The application is designed by independent and integrated modules which can be activated according to specific operational needs.

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

'''Data model:''' the database is designed according to Transmodel specifications, European reference standard (EN12896) for public transport.
|Italian
|
|https://www.pluservice.net/it/soluzioni/gestione-rete-e-turni
|-
|}

==NeTEx data enabled==
{| class="wikitable"
! colspan="1" |Name
! colspan="1" |Availability
! colspan="1" | Description
! colspan="1" |Profile
! colspan="1" |License
! colspan="1" |URL
|-
! rowspan="1" style="text-align:left;" |[[OpenTripPlanner]]
| Available
|Timetable and shortest path journey planner supporting reading various input formats including GTFS and NeTEx.
| Nordic
| Apache 2.0
|http://docs.opentripplanner.org/en/dev-2.x/Netex-Norway/
|-
|}

==Planning system supporting native NeTEx export ==
{| class="wikitable"
!Name
!Availability
!Description
!Profile
|-
! rowspan="1" style="text-align:left;" |[[Hastus]]
|Available
|Planning system from Giro for public transport
| Nordic
|-
! rowspan="1" style="text-align:left;" |[[Trapeze Cloud TP10|Trapeze]]
|Available
|Planning system from Trapeze for public transport
|Nordic
|-
! rowspan="1" style="text-align:left;" |[[DG Buss]]
|Available
|Planning system from Datagrafikk for public transport
|Nordic
|-
! rowspan="1" style="text-align:left;" |[[Train Plan]]
|Available
|Planning system from Trapeze for railway
|Nordic
|-
! rowspan="1" style="text-align:left;" |[[IVU]]
|In development
|Planning system from IVU for public transport
|Nordic
|-
! rowspan="1" style="text-align:left;" |[[IVU]]
|In development
|Planning system from IVU for railway
|Nordic
|-
! rowspan="1" style="text-align:left;" |[[Turnit]]
|Available
|Planning system from Turnit for public transport
|Nordic
|-
! rowspan="1" style="text-align:left;" |[[Nplan]]
|Available
|Planning system from Entur for public transport
|Nordic
|-
! rowspan="1" style="text-align:left;" |[[TPSI]]
|Available
|Planning system from HaCon for railway
|Nordic
|}

<references />

SIRI

2021-12-17T13:35:57Z

Aurige: Update for France

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

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

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

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

== SIRI National and EU minimum profiles ==
Similarly to NeTEx, National profiles are specified to cover the national needs. To help implementation, DATA4PT also is in process of delivering SIRI EU minimum profile, in collaboration with relevant CEN group. DATA4PT has prepared a table with the currently available SIRI national profiles, as an overview of the data categories and functional scope that they currently cover. Links to the documentation are also provided. NeTEx National Profiles overview is available [[NeTEX#National profiles|here.]]

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

= SIRI software =

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

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

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