DATA4PT WIKI - User contributions [en]

National Implementations

2024-12-11T13:37:01Z

Anonymous: added austria link

= NeTEx national profiles inventory 🌐 =

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

== Published profiles ==

{| class="wikitable" style="width : 60%"
|-
! width="150px"| Profile Name
!Status/
Availability
! width="100px" | NeTEx EPIP Based* !! width="100px" | NeTEx EPIP Compatible**
! width="300px" | Documentation
|-
| Australia - Victoria (AU)
|Specified but not yet in operation
| style="text-align:center;" |✅
| style="text-align:center;" |✅
|
|-
|Austria (AT)
|Specified but not yet in operation|| style="text-align:center;" |✅|| ||[https://mobilitaetsverbuende.atlassian.net/wiki/spaces/NET/overview Austrian profile]
|-
|Belgium (BE)
|Specified but not yet in operation|| style="text-align:center;" |✅|| ||[https://github.com/Informatievlaanderen/OSLOthema-mobiliteitDienstregelingEnPlanning GitHUb]
[https://purl.eu/doc/applicationprofile/netex-belgium/timetables-ap/ AP-Timetables]

[https://purl.eu/doc/applicationprofile/netex-belgium/stopplaces-ap/ AP-Stops]

[https://purl.eu/doc/applicationprofile/netex-belgium/vehiclescheduling-ap/ AP-Vehicle Scheduling]

[https://purl.eu/ns/mobility/timetables-and-planning/ AP-TimetablesAndPlanning]

[https://github.com/Informatievlaanderen/OSLOthema-mobiliteitDienstregelingEnPlanning/tree/master/resources/DataExamples Data examples]
|-
|Croatia (HR)
|Specified and in use
| style="text-align:center;" | ✅
| style="text-align:center;" |✅
|[https://www.promet-info.hr/en NPT - Croatian NAP]
|-
|Denmark (DK)
|Specified but not yet in operation|| style="text-align:center;" |✅|| ||[https://www.trafikstyrelsen.dk/Media/638013312835439194/Vejledning%20om%20brug%20af%20NeTEx.pdf Denmark profile] - [https://www.trafikstyrelsen.dk/arbejdsomraader/kollektiv-trafik/statistik-og-data/krav-til-udstilling-af-data-til-rejseplanlaegning NAP in Denmark]
|-
|France (FR)
|Specified and in use|| || style="text-align:center;" |✅||[https://normes.transport.data.gouv.fr/normes/netex/ French profile] - [https://normes.transport.data.gouv.fr/normes/netex/elements_communs/ Common profile] - [https://normes.transport.data.gouv.fr/normes/netex/arrets/ Stop profile] - [https://normes.transport.data.gouv.fr/normes/netex/reseaux/ Network profile] - [https://normes.transport.data.gouv.fr/normes/netex/horaires/ Timetable profile] - [https://normes.transport.data.gouv.fr/normes/netex/tarifs/ Fare profile] - [https://normes.transport.data.gouv.fr/normes/netex/parkings/ Parking profile] - [https://normes.transport.data.gouv.fr/normes/netex/accessibilite/ Accessibility profile]
|-
|Italy (IT)
|Specified and in use|| style="text-align:center;" |✅||
|[https://github.com/5Tsrl/netex-italian-profile/tree/main/Linee%20guida Italian profile]
|-
|Netherlands (NL)
|Specified but not yet in operation|| style="text-align:center;" |✅|| ||[https://bison.dova.nu/standaarden/nederlands-netex-profiel Netherlands profile] - [https://bison.dova.nu/sites/default/files/bison_prijzen_producten_en_tarieven_v8.1.3.0_release.pdf Bison Fares]
|-
| Nordic (Norway, Sweden, Finland, Denmark)
|Specified and in use|| || style="text-align:center;" |✅||[https://enturas.atlassian.net/wiki/spaces/PUBLIC/pages/728891481/Nordic+NeTEx+Profile Nordic profile]
|-
|Portugal (PT)
|Specified and in use|| || ||[https://ptprofiles.azurewebsites.net/netex-profile Portuguese profile]
|-
| Slovenia (SI)
|Specified but not yet in operation|| || style="text-align:center " |✅||[https://www.nap.si/_resources/profiles/NeTEx_SI_Profile_v2.pdf Slovenian profile]
|-
|Switzerland (CH)
|Specified and in use
|
|
|[https://www.oev-info.ch/sites/default/files/2024-05/NeTEx_Core-Realisation_Guide_TP_Suisse-v1.00.pdf Swiss profile]
|-
|UK (GB)
|Specified and in use|| || style="text-align:center " |✅||[http://netex.uk/farexchange/ UK profile] - [http://netex.uk/farexchange/doc/uk_profile/DfT-NeTEx-1-Fares-Intro-2019.06.17-v0.09.pdf Introduction] - [http://netex.uk/farexchange/doc/uk_profile/DfT-NeTEx-2-Base_Spec-2019.06.30-v0.14.pdf Stop and Timetables] - [http://netex.uk/farexchange/doc/uk_profile/DfT-NeTEx-3-Fares_Spec-2019.06.17-v0.17.pdf Fares]
|-
|Ireland (IE)
|Specified and in use|| || ||[https://netex.ie/ Irish profile] - [http://netex.uk/netexie/doc/EIRE_NP/NTA-NeTEx-1-Spec-2020.08.12-v0.22.pdf Profile Elements] - [http://netex.uk/netexie/doc/EIRE_NP/NTA-NeTEx-2-Mappings-2020.08.06-v0.22.pdf Profile Data Mappings]
|-
|Czech Republic (CZ)
|Specified but not yet in operation
| style="text-align:center " |✅
|
|
|}
<nowiki>*</nowiki>Profiles of this category have been specified based on EU Minimum profile and are based on XML technology as EU profiles.

<nowiki>**</nowiki> Profiles of this category have been specified either before the definition of EU Minimum profile, but they have been used to define the EU one, and/or after EU profiles and need conversion or adaptation to be interoperable.
==Data categories==

''Data categories are identified based on [https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex%3A32024R0490 MMTIS EU Regulation 490/2024]''
{| class="mw-collapsible mw-collapsed wikitable" style="width:70%"
|+ style="white-space:nowrap; border:1px solid; padding:3px;" | Data categories table.
|-
!Level of service (LOS)!!Static data
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Static data - Level of service 1 (LOS 1 )'''
|-
| colspan="2" |'''a. Location search (origin/destination)'''
|-
|LOS 1-1||Address identifiers (building number, street name, postcode)
|-
| LOS 1-2||Topographic places (city, town, village, suburb, administrative unit)
|-
|LOS 1-3||Points of interest (related to transport information) to which people may wish to travel
|-
|LOS 1-4||'''b. Trip plans: operational calendar, mapping day types to calendar dates'''
|-
| colspan="2" |'''c. Location search (access nodes) – for scheduled transport and transport on demand where relevant'''
|-
|LOS 1-5
| Identified access nodes
|-
|LOS 1-6 ||Geometry/map layout structure of access nodes

|-
| colspan="2" |'''d. Trip plan computation – for scheduled transport and transport on demand where relevant'''
|-
|LOS 1-7||Connection where interchanges may be made
|-
|LOS 1-8
|Default transfer times at interchanges
|-
|LOS 1-9||Network topology and routes/lines (topology)
|-
| LOS 1-10|| Transport operators
|-
|LOS 1-11|| Timetables
|-
|LOS 1-12||Planned interchanges between guaranteed scheduled services
|-
|LOS 1-13||Hours of operation
|-
| LOS 1-14
|Facilities of access nodes (including platform information, help desk/information points, ticket booths, lifts/stairs, entrances and exit locations)
|-
|LOS 1-15||Vehicles, including their accessibility (such as low floor, wheelchair accessible, pram accessible) and accessibility of on-board services (such as toilets)
|-
|LOS 1-16||Accessibility of access nodes, and paths within an interchange (such as existence of lifts, escalators)
|-
|LOS 1-17||Existence of assistance services (such as existence of on-site assistance)
|-
| colspan="2" |'''e. Trip plan computation'''
|-
|LOS 1-18||Road network (including segregated lanes for bus/taxi)
|-
|LOS 1-19||Cycle network (cycle tracks, cycle lanes, bus-and-cycle lanes, on-road shared with vehicles, on-path shared with pedestrians)
|-
|LOS 1-20||Pedestrian network and accessibility facilities
|-
| ||Framework data
|-
|
|
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Static data - Level of service 2 (LOS 2)'''
|-
| colspan="2" |'''a. Location search – for transport on demand and personal transport'''
|-
|LOS 2-1
|Location of parking places (on and off-street), including accessible parking places for persons with disabilities and persons with reduced mobility
|-
|LOS 2-2||Park & Ride stops
|-
|LOS 2-3
| Park & Drive stops
|-
|LOS 2-4||Bike sharing stations
|-
|LOS 2-5||Car-sharing stations
|-
| LOS 2-6
|Secure bike parking (such as locked bike garages)
|-
|LOS 2-7
|Scooter parking zones
|-
| colspan="2" |'''b. Information service'''
|-
|LOS 2-8||Where and how to buy tickets for scheduled transport, including retail channels, fulfilment methods, payment methods
|-
|LOS 2-9||Where and how to pay for parking, including retail channels, fulfilment methods, payment methods
|-
| colspan="2" |'''c. Auxiliary information – for scheduled transport and transport on demand where relevant'''
|-
|LOS 2-10 ||Basic common standard fares
- fare network data (fare zones/stops and fare stages)

- standard fare structures (point to point including daily and weekly fares, zonal fares, flat fares)
|-
|LOS 2-11||Vehicle facilities such as classes of carriage, on-board Wi-Fi.
|-
| ||
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Static data - Level of service 3 (LOS 3''')
|-
| colspan="2" |'''a. Detailed common standard and special fare query – for scheduled transport and transport on demand where relevant'''
|-
|LOS 3-1||Passenger classes (classes of passenger such as adult, child, senior, student, military/veteran, passenger with disability and passenger with reduced mobility, and qualifying conditions, and classes of travel)
|-
|LOS 3-2|| Common fare products (access rights such as zone/point-to-point including daily and weekly tickets/single/return, eligibility of access, basic usage conditions such as validity period/operator/time of travel/interchanging, standard point-to-point fares prices for different point-to-point pairs including daily and weekly fares/zonal fare prices/flat fare prices)
|-
|LOS 3-3||Special fare products (offers with additional special conditions such as promotional fares, group fares, season passes, aggregated products combining different products, and add-on products such as parking and travel, minimum stay)
|-
|LOS 3-4|| Basic commercial conditions such as refunding, replacing, exchanging or transferring
|-
|LOS 3-5||Basic booking conditions such as purchase windows, validity periods, routing restrictions zonal sequence fares, minimum stay
|-
|LOS 3-6||'''b. Information service – for transport on demand: how to book demand-responsive transport services, including retail channels, fulfilment methods, payment methods'''
|-
| colspan="2" |'''c. Trip plans'''
|-
|LOS 3-7||Detailed cycle network attributes (surface quality, side-by-side cycling, shared surface, on/off road, scenic route, “walk only”, turn or access restrictions, e.g. against flow of traffic)
|-
|LOS 3-8 ||Parameters needed to calculate an environmental factor such as greenhouse gas emissions per vehicle type or passenger mile or per distance walked
|-
|LOS 3-9||Parameters needed to calculate fuel consumption of conventional and alternative fuels
|-
|LOS 3-10
|'''d. Trip plan computation: estimated travel times by day type and time-band by transport mode/combination of transport mode'''
|-
| colspan="2" |
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Static data - Level of service 4 (LOS 4 )'''
|-
| LOS 4-1
|'''a. Historic travel and traffic data on delays – for scheduled transport and transport on demand where relevant'''
|-
| colspan="2" |'''b. Observed data on delays and passing time – for scheduled transport'''
|-
|LOS 4-2
|Length of, and when possible the reason for, delays of at least 60 minutes for rail passenger services (in accordance with Article 19 of Regulation (EU) 2021/782)
|-
|LOS 4-3
|Length of, and when possible the reason for, delays in departure of more than 90 minutes for sea and inland waterways passenger services (in accordance with Article 18 of Regulation (EU) No 1177/2010)
|-
|LOS 4-4
| Length of, and when possible the reason for, delays in departure from a terminal of more than 120 minutes for regular bus and coach passenger services with a scheduled distance of 250 km or more (in accordance with Article 19 of Regulation (EU) No 181/2011)
|-
|LOS 4-5
|Length of, and when possible the reason for, flight delays at departure of at least 120 minutes; and flight delays at arrival of at least 180 minutes (in accordance with Articles 5 and 6 of Regulation (EC) No 261/2004)
|-
| colspan="2" |'''c. Observed data on cancellations – for scheduled transport'''
|-
|LOS 4-6
|Cancellations, and when possible the reason, of rail passenger services
|-
|LOS 4-7
|Cancellations, and when possible the reason, of sea and inland waterways passenger services
|-
|LOS 4-8
|Cancellations, and when possible the reason, of regular bus and coach services with a scheduled distance of 250 km or more
|-
|LOS 4-9
|Cancellations, and when possible the reason, of flights
|-
|LOS 4-10
|'''d. Information on parking tariffs'''
|}

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

{| class="wikitable" style="width:70%"
|-
! width="80px" |Data Categories

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

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

{| class="wikitable" style="width:70%"
|-
! width="80px" |Data Categories
! width="80px" style="text-align:center " |EPIP
! width="80px" | AU
! width="80px" |AT
! width="80px" |ΒΕ
! width="80px" |HR
! width="80px" |DK
! width="80px" |FR
! width="80px" |IT
! width="80px" |NL
! width="150px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |PT
! width="80px" |SI
! width="80px" |CH
! width="80px" |GB
|-
|[[#Data categories|LOS 2-1]]
|
|
|
|
| style="text-align:center;" |✅
|
| style="text-align:center;" |for off-street only
| style="text-align:center " |✅
|
|
|
| |
| style="text-align:center;" |partially covered
|
|-
|[[#Data categories|LOS 2-2]]||
| ||
|
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
| style="text-align:center;" |partially covered||
|-
|[[#Data categories|LOS 2-3]]
|
|
|
|
| style="text-align:center " |✅
|
|
| style="text-align:center " |✅
|
|
|
|
| style="text-align:center;" |partially covered
|
|-
|[[#Data categories|LOS 2-4]]||
| ||
|
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " | ✅
| style="text-align:center;" |partially covered||
|-
|[[#Data categories|LOS 2-5]]||
| ||
|
| style="text-align:center " |✅|| style="text-align:center " |✅
| style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
| style="text-align:center;" |partially covered||
|-
|[[#Data categories|LOS 2-6]]||
| ||
|
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |in off-street car parks only|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
|
|
|-
|[[#Data categories|LOS 2-7]]
|
|
|
|
| style="text-align:center " |✅
|
|
| style="text-align:center " |✅
|
|
|
|
|
|
|-
|[[#Data categories|LOS 2-8]]||
| ||
|
| style="text-align:center " |✅|| || style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
| ||
|-
|[[#Data categories|LOS 2-9]]
|
|
|
|
| style="text-align:center " |✅
|
| style="text-align:center " |✅
| style="text-align:center " |✅
|
| style="text-align:center " | ✅
|
| style="text-align:center " |✅
|
|
|-
|[[#Data categories|LOS 2-10]]||
| style="text-align:center;" |✅||
|
| || || style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " | ✅
| || style="text-align:center " |✅
|-
|[[#Data categories|LOS 2-11]]||
| style="text-align:center;" |✅||
| style="text-align:center " |✅
| || || style="text-align:center " | ✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
| || style="text-align:center " |✅
|-
|[[#Data categories|LOS 2-12]]||
| ||
|
| || || style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
| || style="text-align:center " | ✅
|-
|[[#Data categories|LOS 2-13]]||
| ||
| style="text-align:center " |✅
| || style="text-align:center " |✅|| style="text-align:center " | ✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
| || style="text-align:center " |✅
|-
|}

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

{| class="wikitable" style="width:70%"
|-
! width="80px" |Data Categories
! width="80px" style="text-align:center " |EPIP
! width="80px" |AU
! width="80px" |AT
! width="80px" |BE
! width="80px" |HR
! width="80px" |DK
! width="80px" |FR
! width="80px" |IT
! width="80px" |NL
! width="150px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |PT
! width="80px" |SI
! width="80px" |CH
! width="80px" |GB
|-
|[[#Data categories|LOS 3-1]]||
| ||
| style="text-align:center " |✅

| style="text-align:center " | ✅|| || style="text-align:center " |✅ || style="text-align:center " |✅|| || style="text-align:center " |✅|| ||
| || style="text-align:center " | ✅
|-
|[[#Data categories|LOS 3-2]]||
| ||
|
| style="text-align:center " |✅|| || style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| ||
| || style="text-align:center " |✅
|-
|[[#Data categories|LOS 3-3]]||
| ||
|
| || || style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| ||
| || style="text-align:center " |✅
|-
|[[#Data categories|LOS 3-4]]
|
|
|
|
|
|
| style="text-align:center;" |✅
| style="text-align:center " |✅
|
|
|
|
|
|
|-
|[[#Data categories|LOS 3-5]]
|
|
|
|
|
|
| style="text-align:center;" |✅
|
|
|
|
|
|
|
|-
|[[#Data categories|LOS 3-6]]
|
|
|
|
|
|
| style="text-align:center;" |✅
|
|
|
|
|
| style="text-align:center;" |✅
|
|-
|[[#Data categories|LOS 3-7]]||
| ||
|
| || || || || || style="text-align:center " |✅|| ||
| ||
|-
|[[#Data categories|LOS 3-8]]||
| ||
|
| || || style="text-align:center;" |✅|| || || style="text-align:center " |✅|| ||
| ||
|-
|[[#Data categories|LOS 3-9]]||
| ||
|
| || || style="text-align:center;" |✅|| || || style="text-align:center " |✅|| ||
| ||
|-
|[[#Data categories|LOS 3-10]]||
| ||
|
| || || || || || style="text-align:center " |✅|| ||
| style="text-align:center;" |N/A||
|-
|}

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

⚠️ If you believe that your use cases are resolved in an existing profile, it is highly recommended to '''adopt an existing solution''' and cooperate with the corresponding entity. You will save resources while you will ensure that your profile is interoperable.

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

=SIRI National profiles inventory 🌐=

National profiles are specified to cover the national needs. To help implementation, DATA4PT is also in process of delivering SIRI EU minimum profile, in collaboration with relevant CEN group. DATA4PT has prepared a table with the currently available SIRI national profiles, including an overview of data categories that are currently covered. For data categories relevant to static data check the [NeTEx Profiles Inventory https://data4pt.org/w/index.php?title=NeTEX#NeTEx_national_and_EU_minimum_profiles_inventory].

==Published profiles==

{| class="wikitable" style="width : 50%"
|-
!Profile Name!!Status/
Availability
!EU Minimum profile based*!!EU Minimum SIRI profile compatible** !!Documentation
|-
|Australia - Victoria (AU)
|Specified but not yet in operation
| style="text-align:center " |✅
| style="text-align:center " |✅
|
|-
|Croatia (HR)
|Using an existing profile
|
| style="text-align:center " |✅
|
|-
|France (FR)||Specified and in use
| style="text-align:center " |✅|| style="text-align:center;" | ||[https://normes.transport.data.gouv.fr/normes/siri/profil-france/ French SIRI profile]
|-
|Italy (IT)
| Specified and in use
| style="text-align:center " |✅
|
|[https://github.com/5Tsrl/siri-italian-profile/tree/main/Linee%20guida Italian SIRI profile]
|-
|Netherlands (NL)||Specified but not yet in operation
| || style="text-align:center;" |✅||
|-
|Nordic (Norway, Sweden, Finland, Denmark)|| Specified and in use
| || style="text-align:center;" |✅||[https://enturas.atlassian.net/wiki/spaces/PUBLIC/pages/637370420/Nordic+SIRI+Profile Nordic SIRI profile]
|-
|UK (GB) ||Specified and in use
| || style="text-align:center;" |✅||
|-
|Switzerland (CH)
|Specified and in use
| style="text-align:center;" |✅
| style="text-align:center;" |✅
|[https://www.oev-info.ch/sites/default/files/2023-04/siri_realisation-guide_pt_ch_v0.9.0.pdf SIRI-ET/PT][https://www.oev-info.ch/sites/default/files/2024-07/realization_guide_siri-sx_oev_schweiz_v1.0.pdf SIRI-SX]
|}
<nowiki>*</nowiki>Profiles of this category have been specified based on EU Minimum profile and are based on XML technology as EU profiles.

<nowiki>**</nowiki> Profiles of this category have been specified either before the definition of EU Minimum profile, but they have been used to define the EU one, and/or after EU profiles and need conversion or adaptation to be interoperable.
==Data categories==

''Data categories are identified based on [https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex%3A32024R0490 MMTIS EU Regulation 490/2024]''
{| class="mw-collapsible mw-collapsed wikitable" style="width : 60%"
|+ style="white-space:nowrap; border:1px solid; padding:3px;" |Data categories table.
|-
!Level of service (LOS)!!Types of the dynamic travel and traffic data
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Dynamic data - Level of service 1 (LOS 1 )'''
|-
| colspan="2" |'''a. Passing times, trip plans and auxiliary information'''
|-
| LOS 1-1||Disruptions, such as network closures and/or diversions, and when possible, the reason
|-
|LOS 1-2||Real-time status information, such as estimated departure and arrival times of services, delays, cancellations, guaranteed connections monitoring
|-
|LOS 1-3||Status of access node features (including dynamic platform information, operational lifts/escalators, closed entrances and exit locations) – for scheduled transport
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Dynamic data - Level of service 2 (LOS 2)'''
|-
|LOS 2-1||'''a. Information service on parking tariffs – for transport on demand and personal transport'''
|-
| colspan="2" |'''b. Availability check and location – for transport on demand and personal transport where relevant'''
|-
|LOS 2-2||Car-sharing availability and location, bike-sharing availability and location, scooter-sharing availability and location, and other vehicle-sharing availability and location
|-
|LOS 2-3||Car parking spaces available (on and off-street)
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Dynamic data - Level of service 3 (LOS 3''')
|-
|LOS 3-1|| Occupancy information of the vehicle – for scheduled transport and transport on demand where relevant
|}

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

{| class="wikitable" style="width : 30%"
|-
!Data Categories
! width="80px" |AU
! width="80px" |HR
! width="80px" |FR
! width="80px" |IT
! width="80px" |NL
! width="300px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |GB
! width="80px" |CH
|-
|[[#Data categories|LOS 1-1]]
| style="text-align:center " |✅|| || style="text-align:center " |✅
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅ dynamic platform is included || style="text-align:center " |✅
| style="text-align:center;" |✅
|-
|[[#Data categories|LOS 1-2]]
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅ dynamic platform is included || style="text-align:center " |✅
| style="text-align:center;" |✅
|-
|[[#Data categories|LOS 1-3]]
| || || style="text-align:center " |✅
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅ dynamic platform is included || style="text-align:center " |
| style="text-align:center;" |✅
via SX
|-
|}

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

{| class="wikitable" style="width : 30%"
|-
!Data Categories
! width="80px" |AU
! width="80px" |HR
! width="80px" | FR
! width="80px" |IT
! width="80px" |NL
! width="300px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |GB
! width="80px" |CH
|-
|[[#Data categories|LOS 2-1]]
|
|
|
|
|
|
|
|
|-
|[[#Data categories|LOS 2-2]]
| || || style="text-align:center " |only for car sharing and bike sharing
| style="text-align:center " |✅|| || style="text-align:center " |✅||
|
|-
|[[#Data categories|LOS 2-3]]
| || || style="text-align:center " |off-street only
| style="text-align:center " |✅|| || style="text-align:center " |✅||
|
|-
|}

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

{| class="wikitable" style="width : 30%"
|-
!Data Categories
! width="80px" |AU
! width="80px" |FR
! width="80px" |IT
! width="80px" |NL
! width="300px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |GB
! width="80px" |CH
|-
|[[#Data categories|LOS 3-1]]
| style="text-align:center " |✅
| style="text-align:center " |✅
| style="text-align:center " |✅
|
|
|
|
|}

⚠️ If you believe that your use cases are resolved in an existing profile, it is highly recommended to '''adopt an existing solution''' and cooperate with the corresponding entity. You will save resources while you will ensure that your profile is interoperable.

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

=Implementations per Country=
Currently, the implementations of NeTEx and SIRI are documented for the following countries:

====== [[Australia]] ======

====== [[Austria]] ======

====== [[Belgium]] ======

====== [[Croatia]] ======

====== [[Denmark]] ======

====== [[France]] ======

====== [[Italy]] ======

====== [[Portugal]] ======

====== [[Slovenia]] ======

====== [[Sweden]] ======

====== [[Switzerland]] ======

Austria

2024-12-11T12:26:28Z

Anonymous: added short description of wiener linien

== Overview in the National Level ==
For many implementations, the VDV standards (incl. VDV736) are preferred over other options, for them being tailored to the regional specifics.

[https://data.mobilitaetsverbuende.at/en MVO] publishes NeTEx data and preferably uses VDV736 (SIRI-SX) for situation information.

== Use cases ==

=== Description ===
'''Wiener Linien''' (Viennese Lines) is the company running most of the public transit network in the city of Vienna, Austria. Thus, it is responsible for managing the city's extensive network of buses, trams, and metro systems. It was established in 1978, and is part of the city corporation Wiener Stadtwerke.

For the purposes of operating and maintaining customer information channels (such as the WienMobil app, digital signage and departure boards, the website, on-board information, etc.), Wiener Linien has introduced an API gateway as a middleware component. This ensures that all customer-facing channels source their information from a single system (the API gateway), providing consistent information across all available platforms.

=== Architecture ===
Since the data sources connected to the API Gateway may provide different formats, or the data required for "customer information" may be scattered across various independent sources, Wiener Linien has implemented SIRI and/or NeTEx as the canonical data formats within the API Gateway. This approach facilitates the consolidation of information within the API Gateway, ensuring it serves as the single point of truth for all customer information channels.

The API Gateway can provide customer information channels with data in the canonical format (SIRI or NeTEx) or transform the data into any format required by the consuming system.

For specific use cases, the data can be enriched before being provided to the customer information channels:

* Automatic translation of SIRI-SX Situation Descriptions
* Generation of sign language videos
* Creation of workload or delay estimates using machine learning

=== Implementation ===
The following use cases illustrate how Wiener Linien utilizes the API Gateway and data standards to operate and maintain customer information channels:

* '''FIS+''' involves on-board information screens in the latest subway rolling stock (X-Wagen). The necessary data, including station departures and current situations, is retrieved from internal data sources, transformed into the SIRI-SM and SIRI-SX canonical formats, and then converted into a proprietary format that contains only the most relevant information. This format is extremely lightweight due to limited bandwidth, and the information is subsequently forwarded to the rolling stock.

* For the '''WienMobil App and WienMobil Monitor''', the relevant information (station departures and current situations) is pulled from multiple data sources, including external sources from other transport operators like ÖBB. This data is transformed into the canonical SIRI-SM and SIRI-SX formats, cached within the API Gateway, and then delivered on demand to the app backend. The format is optimized by omitting redundant overhead to improve efficiency.
* The '''e-Paper timetable''' follows a similar process. Station departure and current situation data are pulled from internal data sources, transformed into SIRI-SM and SIRI-SX, cached within the API Gateway, and sent to the e-Paper backend as needed.
* For the generation of sign language videos, current situation data is regularly retrieved from internal sources, transformed into SIRI-SX, and sent a third party API. The thrid party system processes the situation descriptions, generating a sign language video for each relevant entry. A link to the video is returned and can be added as a custom field in any subsequent SIRI-SX messages.
* In the case of the WienMobil Alexa Skill, the required information (station departures) is sourced from internal and external data sources (such as ÖBB), transformed into SIRI-SM, cached in the API Gateway, and provided on demand to the backend system of the Alexa Skill.

=== Outcome ===
The chosen data standard framework is highly robust, accommodating virtually any use case. However, this flexibility introduces significant complexity, which can be challenging for some colleagues and implementers. Despite this, it is well-suited as a canonical data format for these reasons. With this framework in place, Wiener Linien is well-prepared to meet the requirements of EU Regulation 2017/1926.

NeTEX

2024-10-10T09:39:32Z

Anonymous: /* Conversion tools */

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

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

NeTEx (Network Exchange format) is a standard for exchanging public transport network, schedules, and related data. It is a general-purpose XML format designed for the efficient exchange of complex transport data among distributed systems.

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

NeTEx can be used to collect and integrate data from many different stakeholders, and to reintegrate it as it evolves through successive versions. It is used by public transport operators and IT providers across Europe to support a wide range of passenger information and operational applications.

== Benefits of using NeTEx ==

NeTEx offers a number of benefits, including:

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

== Examples of NeTEx in use ==

NeTEx is used in a variety of ways across the public transport industry. For example:

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

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

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

= NeTEx European Passenger Information Profile 🇪🇺 =

{| class="wikitable"
!
! Description
! Documentation
|-
|width="150px" style="text-align:center |'''NeTEx EPIP'''|| Ideally, all member states will provide NeTEx files according to the European Passenger Information Profile (EPIP) on their respective National Access Point. Data4PT provides some artefacts to simplify producing and quality assure such information. EPIP-adapted version of the full NeTEx XML schema has been produced. || Browse the '''graphic and interactive''' technical presentation and download the relevant artefacts and available example [https://data4pt.org/NeTEx/GraphicKit/Documention_of_XSD_for_EPIP.html here].
|-
|width="150px" style="text-align:center |'''NeTEx EPIP Light''' || The official NeTEx schema is too large and complex for C# code generation tools to handle, so a simplified version was created for application development. This schema has been reduced to only match the scope of the EPIP Profile (European Passenger Information Profile). It is compliant with the main NeTEx schema, but does not contain constraint checks and should not be used for validation. || The '''graphic interactive technical presentation''' and the technical artefacts are available [https://data4pt.org/NeTEx/GraphicKit/Documention_of_reduced_XSD.html here].
|-
|}

= Software & tools 🧰 =

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

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

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

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

== Conversion tools ==

{| class="wikitable" style="width:80%"
! colspan="1" | Name
! Availability
! width="40%" | |Description
! colspan="1" |Profile
!width="20%"| License
|-
| style="text-align:center |'''[https://github.com/entur/netex-protobuf netex-protobuf]''' ||style="text-align:center |✅ || NeTEx to protobuf converter || All ||EUPL
|-
|style="text-align:center | '''[https://github.com/CanalTP/transit_model/tree/master/gtfs2netexfr gtfs2netexfr]''' || style="text-align:center |✅ ||Export GTFS data to NeTEx. ||French ||
|-
| style="text-align:center |'''[https://github.com/skinkie/hastus hastus]''' || style="text-align:center |✅ ||Giro Hastus OIG script to export NeTEx from a system, in addition can export crew operations. ||Dutch, Nordic(?) || AGPL-3.0
|-
| style="text-align:center |'''[https://gitlab.com/labiangashi/josm-plugin-netex-converter/ josm-plugin-netex-converter]''' ||style="text-align:center |✅ || Export OpenStreetMap pedestrian routing information into NeTEx.|| || GPL 2.0
|-
| style="text-align:center |'''[https://github.com/entur/netex-gtfs-converter-java netex-gtfs-converter-java]''' ||style="text-align:center |✅ || Export NeTEx data to GTFS ||Nordic ||EUPL
|-
|style="text-align:center |'''[https://github.com/cefriel/chimera Chimera]''' ||style="text-align:center |✅ || Chimera is a framework for semantic data transformation pipelines. A converter between GTFS and NeTEx has been implemented adopting an intermediate Transmodel representation. ||Nordic (ready), EPIP/Italian (ongoing) || Framework – Apache License 2.0, Mapping GTFS-NeTEx – Proprietary license
|-
|style="text-align:center |'''[https://www.openmove.com/ OpenMove ATLAS]''' || style="text-align:center |✅ || The management platform OpenMove ATLAS allows import and editing of data in GTFS format and export also in GTFS or NeTEx format (currently the Italian Profile is supported, other profiles can be implemented on request). || EPIP Italian ||Proprietary license
|-
|style="text-align:center |'''[https://developers.italia.it/it/software/a4c48ddf-7156-4327-a62b-66fc15f1c6f3 GTFS2NeTEx-converter]''' ||style="text-align:center |✅ || Converts GTFS data in NeTEx Italian Profile. || EPIP Italian Profile ||EUPL 1.2
|}

== Data validation tools ==

{| class="wikitable" style="width:40%;"
! width="25%" | Name
!width="10%" | Availability
! width="40%"| Description
!width="10%" | Profile
!width="10%" | License
|-
| style="text-align:center |'''[http://www.xmlsoft.org/ XMLlint]''' || style="text-align:center |✅ ||XML syntax validation, XSD schema validation and constraint checking. ||All ||MIT
|-
|style="text-align:center | '''[https://github.com/ITxPT/DATA4PTTools Greenlight - The Data4PT Validation tool]''' ||style="text-align:center |✅||Validating NeTEx data. ||All ||
|-
| style="text-align:center |'''[https://github.com/entur/netex-validator-java NeTEx validator java]''' ||style="text-align:center |✅|| Validation library for NeTEx data, analyzing and reporting schema compliance. ||Nordic ||
|-
| style="text-align:center |'''[https://github.com/entur/antu Antu]''' ||style="text-align:center |✅|| Validate NeTEx datasets against the Nordic NeTEx Profile. ||Nordic ||
|}

== Language bindings ==
{| class="wikitable" style="width: 45%;"
! Name
! Availability
! Description
! Profile
! License
|-
| style="text-align:center |'''[https://github.com/entur/netex-java-model netex-java-model]''' || style="text-align:center |✅ ||NeTEx XML bindings for Java, with additions to map temporal types to native objects. ||All ||EUPL
|-
|style="text-align:center | '''netex-csharp-model''' ||style="text-align:center |❌ || NeTEx XML bindings for C#. Currently being researched with a variety of tools. Contact DATA4PT if you have questions or have found the golden egg. ||All ||
|-
|style="text-align:center | '''[https://github.com/entur/netex-parser-java netex-parser-java]''' ||style="text-align:center |✅||Parse NeTEx files and lookup entities in an index ||Nordic ||EUPL
|-
|}

== Editing /Management & visualisation tools ==

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

== Journey planning engine ==

{| class="wikitable" style="width: 60%;"
! Name
! Availability
! Description
! Profile
! License
|-
| style="text-align:center | '''[http://docs.opentripplanner.org/en/dev-2.x/Netex-Norway/ OpenTripPlanner]''' || style="text-align:center |✅||Timetable and shortest path journey planner supporting reading various input formats including GTFS and NeTEx. || Nordic || Apache 2.0
|-
| style="text-align:center | '''[https://openmove.com/technology/trip-planning/ OpenMove]''' ||style="text-align:center | ✅ ||Multimodal, intermodal trip planner with real-time capabilities, step-by-step instructions, fare system, and compatibility with market standards. || ||
|-
|}

==Planning system supporting native NeTEx export ==

{| class="wikitable" style="width: 25%;"
!Name
!Availability
!Developped by
!Profile
!Additional documentation
|-
|style="text-align:center | [https://www.giro.ca/en-ca/our-solutions/segments/public-transport/ Hastus] || style="text-align:center |✅ || Giro || Nordic Dutch || Dutch patch: https://github.com/skinkie/hastus
|-
|style="text-align:center | [https://www.trapezegroup.com.au/solutions/intelligent-transport-systems-bus Intelligent Transport Systems (ITS) for Bus] || style="text-align:center |✅|| Trapeze ||EPIP Nordic || Blog post: https://www.trapezegroup.com.au/blog/its-netex-bus-data-transfer-exchange
|-
| style="text-align:center | [https://www.datagrafikk.no/?tag=dgbuss DG Buss] || style="text-align:center |✅ || Datagrafikk || Nordic ||
|-
| style="text-align:center | [https://www.trapezegroup.com.au/solutions/planning-and-scheduling-rail Planning & Scheduling for Train] ||style="text-align:center |✅ || Trapeze ||Nordic ||
|-
| style="text-align:center | [https://www.ivu.com/solutions#c4826 IVU.suite] || style="text-align:center |⏳ || IVU for public transport ||Nordic ||Blog post: https://www.ivu.com/all-references/references/delfi-migrates-to-ivucloud
|-
| style="text-align:center | [https://turnit.com/ Turnit Ride] ||style="text-align:center |✅ ||Turnit for public transport ||Nordic ||
|-
|style="text-align:center | Nplan ||style="text-align:center |✅ ||Entur for public transport ||Nordic || backend: https://github.com/entur/uttu frontend: https://github.com/entur/enki
|-
| style="text-align:center | [https://www.hacon.de/en/portfolio/timetable-construction-disposition/ TPs Suite] ||style="text-align:center | ✅ ||Hacon ||Nordic ||
|}

= NeTEx part 5 for 🆕 modes =

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

''NeTEx Part 5 is now available as '''CEN/TS 16614-5:2022 (E)'''''
[[File:NeTEx-part5.png|400px|right|]]

{| class="wikitable" style="width: 50%;"
|-
!
!Description
|-
| '''[https://github.com/NeTEx-CEN/NeTEx/tree/master/xsd/netex_part_5 Technical artefacts]''' || The XML schema (XSD) for NeTEx Part 5 New Modes. Examples are also provided, along with other useful documentation.
|-
| '''[https://data4pt.org/w/images/5/5b/Canonical_mapping_-_NeTEx_and_SIRI_new_modes_with_GBFS.pdf Canonical mapping with GBFS]'''
| The EU-funded project DATA4PT and MobilityData experts have released a high-level mapping between the General Bikeshare Feed Specification (GBFS) and Transmodel to support better interoperability of shared mobility data feeds.
|-
|}

= References =

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

NeTEX

2024-10-10T06:03:02Z

Anonymous: /* Conversion tools */

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

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

NeTEx (Network Exchange format) is a standard for exchanging public transport network, schedules, and related data. It is a general-purpose XML format designed for the efficient exchange of complex transport data among distributed systems.

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

NeTEx can be used to collect and integrate data from many different stakeholders, and to reintegrate it as it evolves through successive versions. It is used by public transport operators and IT providers across Europe to support a wide range of passenger information and operational applications.

== Benefits of using NeTEx ==

NeTEx offers a number of benefits, including:

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

== Examples of NeTEx in use ==

NeTEx is used in a variety of ways across the public transport industry. For example:

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

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

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

= NeTEx European Passenger Information Profile 🇪🇺 =

{| class="wikitable"
!
! Description
! Documentation
|-
|width="150px" style="text-align:center |'''NeTEx EPIP'''|| Ideally, all member states will provide NeTEx files according to the European Passenger Information Profile (EPIP) on their respective National Access Point. Data4PT provides some artefacts to simplify producing and quality assure such information. EPIP-adapted version of the full NeTEx XML schema has been produced. || Browse the '''graphic and interactive''' technical presentation and download the relevant artefacts and available example [https://data4pt.org/NeTEx/GraphicKit/Documention_of_XSD_for_EPIP.html here].
|-
|width="150px" style="text-align:center |'''NeTEx EPIP Light''' || The official NeTEx schema is too large and complex for C# code generation tools to handle, so a simplified version was created for application development. This schema has been reduced to only match the scope of the EPIP Profile (European Passenger Information Profile). It is compliant with the main NeTEx schema, but does not contain constraint checks and should not be used for validation. || The '''graphic interactive technical presentation''' and the technical artefacts are available [https://data4pt.org/NeTEx/GraphicKit/Documention_of_reduced_XSD.html here].
|-
|}

= Software & tools 🧰 =

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

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

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

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

== Conversion tools ==

{| class="wikitable" style="width:80%"
! colspan="1" | Name
! Availability
! width="40%" | |Description
! colspan="1" |Profile
!width="20%"| License
!URL
|-
| style="text-align:center |'''[https://github.com/entur/netex-protobuf netex-protobuf]''' ||style="text-align:center |✅ || NeTEx to protobuf converter || All ||EUPL
|
|-
|style="text-align:center | '''[https://github.com/CanalTP/transit_model/tree/master/gtfs2netexfr gtfs2netexfr]''' || style="text-align:center |✅ ||Export GTFS data to NeTEx. ||French ||
|
|-
| style="text-align:center |'''[https://github.com/skinkie/hastus hastus]''' || style="text-align:center |✅ ||Giro Hastus OIG script to export NeTEx from a system, in addition can export crew operations. ||Dutch, Nordic(?) || AGPL-3.0
|
|-
| style="text-align:center |'''[https://gitlab.com/labiangashi/josm-plugin-netex-converter/ josm-plugin-netex-converter]''' ||style="text-align:center |✅ || Export OpenStreetMap pedestrian routing information into NeTEx.|| || GPL 2.0
|
|-
| style="text-align:center |'''[https://github.com/entur/netex-gtfs-converter-java netex-gtfs-converter-java]''' ||style="text-align:center |✅ || Export NeTEx data to GTFS ||Nordic ||EUPL
|
|-
|style="text-align:center |'''[https://github.com/cefriel/chimera Chimera]''' ||style="text-align:center |✅ || Chimera is a framework for semantic data transformation pipelines. A converter between GTFS and NeTEx has been implemented adopting an intermediate Transmodel representation. ||Nordic (ready), EPIP/Italian (ongoing) || Framework – Apache License 2.0, Mapping GTFS-NeTEx – Proprietary license
|
|-
|style="text-align:center |'''[https://www.openmove.com/ OpenMove ATLAS]''' || style="text-align:center |✅ || The management platform OpenMove ATLAS allows import and editing of data in GTFS format and export also in GTFS or NeTEx format (currently the Italian Profile is supported, other profiles can be implemented on request). || EPIP Italian ||Proprietary license
|
|-
|style="text-align:center |'''GTFS2NeTEx-converter''' ||style="text-align:center |✅ || Converts GTFS data in NeTEx Italian Profile. || EPIP Italian Profile ||EUPL 1.2
|https://developers.italia.it/it/software/a4c48ddf-7156-4327-a62b-66fc15f1c6f3
|}

== Data validation tools ==

{| class="wikitable" style="width:40%;"
! width="25%" | Name
!width="10%" | Availability
! width="40%"| Description
!width="10%" | Profile
!width="10%" | License
|-
| style="text-align:center |'''[http://www.xmlsoft.org/ XMLlint]''' || style="text-align:center |✅ ||XML syntax validation, XSD schema validation and constraint checking. ||All ||MIT
|-
|style="text-align:center | '''[https://github.com/ITxPT/DATA4PTTools Greenlight - The Data4PT Validation tool]''' ||style="text-align:center |✅||Validating NeTEx data. ||All ||
|-
| style="text-align:center |'''[https://github.com/entur/netex-validator-java NeTEx validator java]''' ||style="text-align:center |✅|| Validation library for NeTEx data, analyzing and reporting schema compliance. ||Nordic ||
|-
| style="text-align:center |'''[https://github.com/entur/antu Antu]''' ||style="text-align:center |✅|| Validate NeTEx datasets against the Nordic NeTEx Profile. ||Nordic ||
|}

== Language bindings ==
{| class="wikitable" style="width: 45%;"
! Name
! Availability
! Description
! Profile
! License
|-
| style="text-align:center |'''[https://github.com/entur/netex-java-model netex-java-model]''' || style="text-align:center |✅ ||NeTEx XML bindings for Java, with additions to map temporal types to native objects. ||All ||EUPL
|-
|style="text-align:center | '''netex-csharp-model''' ||style="text-align:center |❌ || NeTEx XML bindings for C#. Currently being researched with a variety of tools. Contact DATA4PT if you have questions or have found the golden egg. ||All ||
|-
|style="text-align:center | '''[https://github.com/entur/netex-parser-java netex-parser-java]''' ||style="text-align:center |✅||Parse NeTEx files and lookup entities in an index ||Nordic ||EUPL
|-
|}

== Editing /Management & visualisation tools ==

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

== Journey planning engine ==

{| class="wikitable" style="width: 60%;"
! Name
! Availability
! Description
! Profile
! License
|-
| style="text-align:center | '''[http://docs.opentripplanner.org/en/dev-2.x/Netex-Norway/ OpenTripPlanner]''' || style="text-align:center |✅||Timetable and shortest path journey planner supporting reading various input formats including GTFS and NeTEx. || Nordic || Apache 2.0
|-
| style="text-align:center | '''[https://openmove.com/technology/trip-planning/ OpenMove]''' ||style="text-align:center | ✅ ||Multimodal, intermodal trip planner with real-time capabilities, step-by-step instructions, fare system, and compatibility with market standards. || ||
|-
|}

==Planning system supporting native NeTEx export ==

{| class="wikitable" style="width: 25%;"
!Name
!Availability
!Developped by
!Profile
!Additional documentation
|-
|style="text-align:center | [https://www.giro.ca/en-ca/our-solutions/segments/public-transport/ Hastus] || style="text-align:center |✅ || Giro || Nordic Dutch || Dutch patch: https://github.com/skinkie/hastus
|-
|style="text-align:center | [https://www.trapezegroup.com.au/solutions/intelligent-transport-systems-bus Intelligent Transport Systems (ITS) for Bus] || style="text-align:center |✅|| Trapeze ||EPIP Nordic || Blog post: https://www.trapezegroup.com.au/blog/its-netex-bus-data-transfer-exchange
|-
| style="text-align:center | [https://www.datagrafikk.no/?tag=dgbuss DG Buss] || style="text-align:center |✅ || Datagrafikk || Nordic ||
|-
| style="text-align:center | [https://www.trapezegroup.com.au/solutions/planning-and-scheduling-rail Planning & Scheduling for Train] ||style="text-align:center |✅ || Trapeze ||Nordic ||
|-
| style="text-align:center | [https://www.ivu.com/solutions#c4826 IVU.suite] || style="text-align:center |⏳ || IVU for public transport ||Nordic ||Blog post: https://www.ivu.com/all-references/references/delfi-migrates-to-ivucloud
|-
| style="text-align:center | [https://turnit.com/ Turnit Ride] ||style="text-align:center |✅ ||Turnit for public transport ||Nordic ||
|-
|style="text-align:center | Nplan ||style="text-align:center |✅ ||Entur for public transport ||Nordic || backend: https://github.com/entur/uttu frontend: https://github.com/entur/enki
|-
| style="text-align:center | [https://www.hacon.de/en/portfolio/timetable-construction-disposition/ TPs Suite] ||style="text-align:center | ✅ ||Hacon ||Nordic ||
|}

= NeTEx part 5 for 🆕 modes =

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

''NeTEx Part 5 is now available as '''CEN/TS 16614-5:2022 (E)'''''
[[File:NeTEx-part5.png|400px|right|]]

{| class="wikitable" style="width: 50%;"
|-
!
!Description
|-
| '''[https://github.com/NeTEx-CEN/NeTEx/tree/master/xsd/netex_part_5 Technical artefacts]''' || The XML schema (XSD) for NeTEx Part 5 New Modes. Examples are also provided, along with other useful documentation.
|-
| '''[https://data4pt.org/w/images/5/5b/Canonical_mapping_-_NeTEx_and_SIRI_new_modes_with_GBFS.pdf Canonical mapping with GBFS]'''
| The EU-funded project DATA4PT and MobilityData experts have released a high-level mapping between the General Bikeshare Feed Specification (GBFS) and Transmodel to support better interoperability of shared mobility data feeds.
|-
|}

= References =

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

NeTEX

2024-10-10T06:01:02Z

Anonymous: /* Conversion tools */

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

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

NeTEx (Network Exchange format) is a standard for exchanging public transport network, schedules, and related data. It is a general-purpose XML format designed for the efficient exchange of complex transport data among distributed systems.

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

NeTEx can be used to collect and integrate data from many different stakeholders, and to reintegrate it as it evolves through successive versions. It is used by public transport operators and IT providers across Europe to support a wide range of passenger information and operational applications.

== Benefits of using NeTEx ==

NeTEx offers a number of benefits, including:

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

== Examples of NeTEx in use ==

NeTEx is used in a variety of ways across the public transport industry. For example:

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

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

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

= NeTEx European Passenger Information Profile 🇪🇺 =

{| class="wikitable"
!
! Description
! Documentation
|-
|width="150px" style="text-align:center |'''NeTEx EPIP'''|| Ideally, all member states will provide NeTEx files according to the European Passenger Information Profile (EPIP) on their respective National Access Point. Data4PT provides some artefacts to simplify producing and quality assure such information. EPIP-adapted version of the full NeTEx XML schema has been produced. || Browse the '''graphic and interactive''' technical presentation and download the relevant artefacts and available example [https://data4pt.org/NeTEx/GraphicKit/Documention_of_XSD_for_EPIP.html here].
|-
|width="150px" style="text-align:center |'''NeTEx EPIP Light''' || The official NeTEx schema is too large and complex for C# code generation tools to handle, so a simplified version was created for application development. This schema has been reduced to only match the scope of the EPIP Profile (European Passenger Information Profile). It is compliant with the main NeTEx schema, but does not contain constraint checks and should not be used for validation. || The '''graphic interactive technical presentation''' and the technical artefacts are available [https://data4pt.org/NeTEx/GraphicKit/Documention_of_reduced_XSD.html here].
|-
|}

= Software & tools 🧰 =

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

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

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

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

== Conversion tools ==

{| class="wikitable" style="width:80%"
! colspan="1" | Name
! Availability
! width="40%" | |Description
! colspan="1" |Profile
!width="20%"| colspan="1" |License
|-
| style="text-align:center |'''[https://github.com/entur/netex-protobuf netex-protobuf]''' ||style="text-align:center |✅ || NeTEx to protobuf converter || All ||EUPL
|-
|style="text-align:center | '''[https://github.com/CanalTP/transit_model/tree/master/gtfs2netexfr gtfs2netexfr]''' || style="text-align:center |✅ ||Export GTFS data to NeTEx. ||French ||
|-
| style="text-align:center |'''[https://github.com/skinkie/hastus hastus]''' || style="text-align:center |✅ ||Giro Hastus OIG script to export NeTEx from a system, in addition can export crew operations. ||Dutch, Nordic(?) || AGPL-3.0
|-
| style="text-align:center |'''[https://gitlab.com/labiangashi/josm-plugin-netex-converter/ josm-plugin-netex-converter]''' ||style="text-align:center |✅ || Export OpenStreetMap pedestrian routing information into NeTEx.|| || GPL 2.0
|-
| style="text-align:center |'''[https://github.com/entur/netex-gtfs-converter-java netex-gtfs-converter-java]''' ||style="text-align:center |✅ || Export NeTEx data to GTFS ||Nordic ||EUPL
|-
|style="text-align:center |'''[https://github.com/cefriel/chimera Chimera]''' ||style="text-align:center |✅ || Chimera is a framework for semantic data transformation pipelines. A converter between GTFS and NeTEx has been implemented adopting an intermediate Transmodel representation. ||Nordic (ready), EPIP/Italian (ongoing) || Framework – Apache License 2.0, Mapping GTFS-NeTEx – Proprietary license
|-
|style="text-align:center |'''[https://www.openmove.com/ OpenMove ATLAS]''' || style="text-align:center |✅ || The management platform OpenMove ATLAS allows import and editing of data in GTFS format and export also in GTFS or NeTEx format (currently the Italian Profile is supported, other profiles can be implemented on request). || EPIP Italian ||Proprietary license
|-
|style="text-align:center |'''GTFS2NeTEx-converter''' ||style="text-align:center |✅ || Converts GTFS data in NeTEx Italian Profile. || EPIP Italian Profile ||EUPL 1.2
|}

== Data validation tools ==

{| class="wikitable" style="width:40%;"
! width="25%" | Name
!width="10%" | Availability
! width="40%"| Description
!width="10%" | Profile
!width="10%" | License
|-
| style="text-align:center |'''[http://www.xmlsoft.org/ XMLlint]''' || style="text-align:center |✅ ||XML syntax validation, XSD schema validation and constraint checking. ||All ||MIT
|-
|style="text-align:center | '''[https://github.com/ITxPT/DATA4PTTools Greenlight - The Data4PT Validation tool]''' ||style="text-align:center |✅||Validating NeTEx data. ||All ||
|-
| style="text-align:center |'''[https://github.com/entur/netex-validator-java NeTEx validator java]''' ||style="text-align:center |✅|| Validation library for NeTEx data, analyzing and reporting schema compliance. ||Nordic ||
|-
| style="text-align:center |'''[https://github.com/entur/antu Antu]''' ||style="text-align:center |✅|| Validate NeTEx datasets against the Nordic NeTEx Profile. ||Nordic ||
|}

== Language bindings ==
{| class="wikitable" style="width: 45%;"
! Name
! Availability
! Description
! Profile
! License
|-
| style="text-align:center |'''[https://github.com/entur/netex-java-model netex-java-model]''' || style="text-align:center |✅ ||NeTEx XML bindings for Java, with additions to map temporal types to native objects. ||All ||EUPL
|-
|style="text-align:center | '''netex-csharp-model''' ||style="text-align:center |❌ || NeTEx XML bindings for C#. Currently being researched with a variety of tools. Contact DATA4PT if you have questions or have found the golden egg. ||All ||
|-
|style="text-align:center | '''[https://github.com/entur/netex-parser-java netex-parser-java]''' ||style="text-align:center |✅||Parse NeTEx files and lookup entities in an index ||Nordic ||EUPL
|-
|}

== Editing /Management & visualisation tools ==

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

== Journey planning engine ==

{| class="wikitable" style="width: 60%;"
! Name
! Availability
! Description
! Profile
! License
|-
| style="text-align:center | '''[http://docs.opentripplanner.org/en/dev-2.x/Netex-Norway/ OpenTripPlanner]''' || style="text-align:center |✅||Timetable and shortest path journey planner supporting reading various input formats including GTFS and NeTEx. || Nordic || Apache 2.0
|-
| style="text-align:center | '''[https://openmove.com/technology/trip-planning/ OpenMove]''' ||style="text-align:center | ✅ ||Multimodal, intermodal trip planner with real-time capabilities, step-by-step instructions, fare system, and compatibility with market standards. || ||
|-
|}

==Planning system supporting native NeTEx export ==

{| class="wikitable" style="width: 25%;"
!Name
!Availability
!Developped by
!Profile
!Additional documentation
|-
|style="text-align:center | [https://www.giro.ca/en-ca/our-solutions/segments/public-transport/ Hastus] || style="text-align:center |✅ || Giro || Nordic Dutch || Dutch patch: https://github.com/skinkie/hastus
|-
|style="text-align:center | [https://www.trapezegroup.com.au/solutions/intelligent-transport-systems-bus Intelligent Transport Systems (ITS) for Bus] || style="text-align:center |✅|| Trapeze ||EPIP Nordic || Blog post: https://www.trapezegroup.com.au/blog/its-netex-bus-data-transfer-exchange
|-
| style="text-align:center | [https://www.datagrafikk.no/?tag=dgbuss DG Buss] || style="text-align:center |✅ || Datagrafikk || Nordic ||
|-
| style="text-align:center | [https://www.trapezegroup.com.au/solutions/planning-and-scheduling-rail Planning & Scheduling for Train] ||style="text-align:center |✅ || Trapeze ||Nordic ||
|-
| style="text-align:center | [https://www.ivu.com/solutions#c4826 IVU.suite] || style="text-align:center |⏳ || IVU for public transport ||Nordic ||Blog post: https://www.ivu.com/all-references/references/delfi-migrates-to-ivucloud
|-
| style="text-align:center | [https://turnit.com/ Turnit Ride] ||style="text-align:center |✅ ||Turnit for public transport ||Nordic ||
|-
|style="text-align:center | Nplan ||style="text-align:center |✅ ||Entur for public transport ||Nordic || backend: https://github.com/entur/uttu frontend: https://github.com/entur/enki
|-
| style="text-align:center | [https://www.hacon.de/en/portfolio/timetable-construction-disposition/ TPs Suite] ||style="text-align:center | ✅ ||Hacon ||Nordic ||
|}

= NeTEx part 5 for 🆕 modes =

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

''NeTEx Part 5 is now available as '''CEN/TS 16614-5:2022 (E)'''''
[[File:NeTEx-part5.png|400px|right|]]

{| class="wikitable" style="width: 50%;"
|-
!
!Description
|-
| '''[https://github.com/NeTEx-CEN/NeTEx/tree/master/xsd/netex_part_5 Technical artefacts]''' || The XML schema (XSD) for NeTEx Part 5 New Modes. Examples are also provided, along with other useful documentation.
|-
| '''[https://data4pt.org/w/images/5/5b/Canonical_mapping_-_NeTEx_and_SIRI_new_modes_with_GBFS.pdf Canonical mapping with GBFS]'''
| The EU-funded project DATA4PT and MobilityData experts have released a high-level mapping between the General Bikeshare Feed Specification (GBFS) and Transmodel to support better interoperability of shared mobility data feeds.
|-
|}

= References =

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

National Implementations

2024-10-08T14:18:08Z

Anonymous:

= NeTEx national profiles inventory 🌐 =

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

== Published profiles ==

{| class="wikitable" style="width : 60%"
|-
! width="150px"| Profile Name
!Status/
Availability
! width="100px" | NeTEx EPIP Based* !! width="100px" | NeTEx EPIP Compatible**
! width="300px" | Documentation
|-
| Australia - Victoria (AU)
|Specified but not yet in operation
| style="text-align:center;" |✅
| style="text-align:center;" |✅
|
|-
|Austria (AT)
|Specified but not yet in operation|| style="text-align:center;" |✅|| ||[https://mobilitaetsverbuende.atlassian.net/wiki/spaces/NET/overview Austrian profile]
|-
|Belgium (BE)
|Specified but not yet in operation|| style="text-align:center;" |✅|| ||[https://github.com/Informatievlaanderen/OSLOthema-mobiliteitDienstregelingEnPlanning GitHUb]
[https://purl.eu/doc/applicationprofile/netex-belgium/timetables-ap/ AP-Timetables]

[https://purl.eu/doc/applicationprofile/netex-belgium/stopplaces-ap/ AP-Stops]

[https://purl.eu/doc/applicationprofile/netex-belgium/vehiclescheduling-ap/ AP-Vehicle Scheduling]

[https://purl.eu/ns/mobility/timetables-and-planning/ AP-TimetablesAndPlanning]

[https://github.com/Informatievlaanderen/OSLOthema-mobiliteitDienstregelingEnPlanning/tree/master/resources/DataExamples Data examples]
|-
|Croatia (HR)
|Specified and in use
| style="text-align:center;" | ✅
| style="text-align:center;" |✅
|[https://www.promet-info.hr/en NPT - Croatian NAP]
|-
|Denmark (DK)
|Specified but not yet in operation|| style="text-align:center;" |✅|| ||[https://www.trafikstyrelsen.dk/Media/638013312835439194/Vejledning%20om%20brug%20af%20NeTEx.pdf Denmark profile] - [https://www.trafikstyrelsen.dk/arbejdsomraader/kollektiv-trafik/statistik-og-data/krav-til-udstilling-af-data-til-rejseplanlaegning NAP in Denmark]
|-
|France (FR)
|Specified and in use|| || style="text-align:center;" |✅||[https://normes.transport.data.gouv.fr/normes/netex/ French profile] - [https://normes.transport.data.gouv.fr/normes/netex/elements_communs/ Common profile] - [https://normes.transport.data.gouv.fr/normes/netex/arrets/ Stop profile] - [https://normes.transport.data.gouv.fr/normes/netex/reseaux/ Network profile] - [https://normes.transport.data.gouv.fr/normes/netex/horaires/ Timetable profile] - [https://normes.transport.data.gouv.fr/normes/netex/tarifs/ Fare profile] - [https://normes.transport.data.gouv.fr/normes/netex/parkings/ Parking profile] - [https://normes.transport.data.gouv.fr/normes/netex/accessibilite/ Accessibility profile]
|-
|Italy (IT)
|Specified and in use|| style="text-align:center;" |✅||
|[https://github.com/5Tsrl/netex-italian-profile/tree/main/Linee%20guida Italian profile]
|-
|Netherlands (NL)
|Specified but not yet in operation|| style="text-align:center;" |✅|| ||[https://bison.dova.nu/standaarden/nederlands-netex-profiel Netherlands profile] - [https://bison.dova.nu/sites/default/files/bison_prijzen_producten_en_tarieven_v8.1.3.0_release.pdf Bison Fares]
|-
| Nordic (Norway, Sweden, Finland, Denmark)
|Specified and in use|| || style="text-align:center;" |✅||[https://enturas.atlassian.net/wiki/spaces/PUBLIC/pages/728891481/Nordic+NeTEx+Profile Nordic profile]
|-
|Portugal (PT)
|Specified and in use|| || ||[https://ptprofiles.azurewebsites.net/netex-profile Portuguese profile]
|-
| Slovenia (SI)
|Specified but not yet in operation|| || style="text-align:center " |✅||[https://www.nap.si/_resources/profiles/NeTEx_SI_Profile_v2.pdf Slovenian profile]
|-
|Switzerland (CH)
|Specified and in use
|
|
|[https://www.oev-info.ch/sites/default/files/2024-05/NeTEx_Core-Realisation_Guide_TP_Suisse-v1.00.pdf Swiss profile]
|-
|UK (GB)
|Specified and in use|| || style="text-align:center " |✅||[http://netex.uk/farexchange/ UK profile] - [http://netex.uk/farexchange/doc/uk_profile/DfT-NeTEx-1-Fares-Intro-2019.06.17-v0.09.pdf Introduction] - [http://netex.uk/farexchange/doc/uk_profile/DfT-NeTEx-2-Base_Spec-2019.06.30-v0.14.pdf Stop and Timetables] - [http://netex.uk/farexchange/doc/uk_profile/DfT-NeTEx-3-Fares_Spec-2019.06.17-v0.17.pdf Fares]
|-
|Ireland (IE)
|Specified and in use|| || ||[https://netex.ie/ Irish profile] - [http://netex.uk/netexie/doc/EIRE_NP/NTA-NeTEx-1-Spec-2020.08.12-v0.22.pdf Profile Elements] - [http://netex.uk/netexie/doc/EIRE_NP/NTA-NeTEx-2-Mappings-2020.08.06-v0.22.pdf Profile Data Mappings]
|-
|Czech Republic (CZ)
|Specified but not yet in operation
| style="text-align:center " |✅
|
|
|}
<nowiki>*</nowiki>Profiles of this category have been specified based on EU Minimum profile and are based on XML technology as EU profiles.

<nowiki>**</nowiki> Profiles of this category have been specified either before the definition of EU Minimum profile, but they have been used to define the EU one, and/or after EU profiles and need conversion or adaptation to be interoperable.
==Data categories==

''Data categories are identified based on [https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex%3A32024R0490 MMTIS EU Regulation 490/2024]''
{| class="mw-collapsible mw-collapsed wikitable" style="width:70%"
|+ style="white-space:nowrap; border:1px solid; padding:3px;" | Data categories table.
|-
!Level of service (LOS)!!Static data
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Static data - Level of service 1 (LOS 1 )'''
|-
| colspan="2" |'''a. Location search (origin/destination)'''
|-
|LOS 1-1||Address identifiers (building number, street name, postcode)
|-
| LOS 1-2||Topographic places (city, town, village, suburb, administrative unit)
|-
|LOS 1-3||Points of interest (related to transport information) to which people may wish to travel
|-
|LOS 1-4||'''b. Trip plans: operational calendar, mapping day types to calendar dates'''
|-
| colspan="2" |'''c. Location search (access nodes) – for scheduled transport and transport on demand where relevant'''
|-
|LOS 1-5
| Identified access nodes
|-
|LOS 1-6 ||Geometry/map layout structure of access nodes

|-
| colspan="2" |'''d. Trip plan computation – for scheduled transport and transport on demand where relevant'''
|-
|LOS 1-7||Connection where interchanges may be made
|-
|LOS 1-8
|Default transfer times at interchanges
|-
|LOS 1-9||Network topology and routes/lines (topology)
|-
| LOS 1-10|| Transport operators
|-
|LOS 1-11|| Timetables
|-
|LOS 1-12||Planned interchanges between guaranteed scheduled services
|-
|LOS 1-13||Hours of operation
|-
| LOS 1-14
|Facilities of access nodes (including platform information, help desk/information points, ticket booths, lifts/stairs, entrances and exit locations)
|-
|LOS 1-15||Vehicles, including their accessibility (such as low floor, wheelchair accessible, pram accessible) and accessibility of on-board services (such as toilets)
|-
|LOS 1-16||Accessibility of access nodes, and paths within an interchange (such as existence of lifts, escalators)
|-
|LOS 1-17||Existence of assistance services (such as existence of on-site assistance)
|-
| colspan="2" |'''e. Trip plan computation'''
|-
|LOS 1-18||Road network (including segregated lanes for bus/taxi)
|-
|LOS 1-19||Cycle network (cycle tracks, cycle lanes, bus-and-cycle lanes, on-road shared with vehicles, on-path shared with pedestrians)
|-
|LOS 1-20||Pedestrian network and accessibility facilities
|-
| ||Framework data
|-
|
|
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Static data - Level of service 2 (LOS 2)'''
|-
| colspan="2" |'''a. Location search – for transport on demand and personal transport'''
|-
|LOS 2-1
|Location of parking places (on and off-street), including accessible parking places for persons with disabilities and persons with reduced mobility
|-
|LOS 2-2||Park & Ride stops
|-
|LOS 2-3
| Park & Drive stops
|-
|LOS 2-4||Bike sharing stations
|-
|LOS 2-5||Car-sharing stations
|-
| LOS 2-6
|Secure bike parking (such as locked bike garages)
|-
|LOS 2-7
|Scooter parking zones
|-
| colspan="2" |'''b. Information service'''
|-
|LOS 2-8||Where and how to buy tickets for scheduled transport, including retail channels, fulfilment methods, payment methods
|-
|LOS 2-9||Where and how to pay for parking, including retail channels, fulfilment methods, payment methods
|-
| colspan="2" |'''c. Auxiliary information – for scheduled transport and transport on demand where relevant'''
|-
|LOS 2-10 ||Basic common standard fares
- fare network data (fare zones/stops and fare stages)

- standard fare structures (point to point including daily and weekly fares, zonal fares, flat fares)
|-
|LOS 2-11||Vehicle facilities such as classes of carriage, on-board Wi-Fi.
|-
| ||
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Static data - Level of service 3 (LOS 3''')
|-
| colspan="2" |'''a. Detailed common standard and special fare query – for scheduled transport and transport on demand where relevant'''
|-
|LOS 3-1||Passenger classes (classes of passenger such as adult, child, senior, student, military/veteran, passenger with disability and passenger with reduced mobility, and qualifying conditions, and classes of travel)
|-
|LOS 3-2|| Common fare products (access rights such as zone/point-to-point including daily and weekly tickets/single/return, eligibility of access, basic usage conditions such as validity period/operator/time of travel/interchanging, standard point-to-point fares prices for different point-to-point pairs including daily and weekly fares/zonal fare prices/flat fare prices)
|-
|LOS 3-3||Special fare products (offers with additional special conditions such as promotional fares, group fares, season passes, aggregated products combining different products, and add-on products such as parking and travel, minimum stay)
|-
|LOS 3-4|| Basic commercial conditions such as refunding, replacing, exchanging or transferring
|-
|LOS 3-5||Basic booking conditions such as purchase windows, validity periods, routing restrictions zonal sequence fares, minimum stay
|-
|LOS 3-6||'''b. Information service – for transport on demand: how to book demand-responsive transport services, including retail channels, fulfilment methods, payment methods'''
|-
| colspan="2" |'''c. Trip plans'''
|-
|LOS 3-7||Detailed cycle network attributes (surface quality, side-by-side cycling, shared surface, on/off road, scenic route, “walk only”, turn or access restrictions, e.g. against flow of traffic)
|-
|LOS 3-8 ||Parameters needed to calculate an environmental factor such as greenhouse gas emissions per vehicle type or passenger mile or per distance walked
|-
|LOS 3-9||Parameters needed to calculate fuel consumption of conventional and alternative fuels
|-
|LOS 3-10
|'''d. Trip plan computation: estimated travel times by day type and time-band by transport mode/combination of transport mode'''
|-
| colspan="2" |
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Static data - Level of service 4 (LOS 4 )'''
|-
| LOS 4-1
|'''a. Historic travel and traffic data on delays – for scheduled transport and transport on demand where relevant'''
|-
| colspan="2" |'''b. Observed data on delays and passing time – for scheduled transport'''
|-
|LOS 4-2
|Length of, and when possible the reason for, delays of at least 60 minutes for rail passenger services (in accordance with Article 19 of Regulation (EU) 2021/782)
|-
|LOS 4-3
|Length of, and when possible the reason for, delays in departure of more than 90 minutes for sea and inland waterways passenger services (in accordance with Article 18 of Regulation (EU) No 1177/2010)
|-
|LOS 4-4
| Length of, and when possible the reason for, delays in departure from a terminal of more than 120 minutes for regular bus and coach passenger services with a scheduled distance of 250 km or more (in accordance with Article 19 of Regulation (EU) No 181/2011)
|-
|LOS 4-5
|Length of, and when possible the reason for, flight delays at departure of at least 120 minutes; and flight delays at arrival of at least 180 minutes (in accordance with Articles 5 and 6 of Regulation (EC) No 261/2004)
|-
| colspan="2" |'''c. Observed data on cancellations – for scheduled transport'''
|-
|LOS 4-6
|Cancellations, and when possible the reason, of rail passenger services
|-
|LOS 4-7
|Cancellations, and when possible the reason, of sea and inland waterways passenger services
|-
|LOS 4-8
|Cancellations, and when possible the reason, of regular bus and coach services with a scheduled distance of 250 km or more
|-
|LOS 4-9
|Cancellations, and when possible the reason, of flights
|-
|LOS 4-10
|'''d. Information on parking tariffs'''
|}

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

{| class="wikitable" style="width:70%"
|-
! width="80px" |Data Categories

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

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

{| class="wikitable" style="width:70%"
|-
! width="80px" |Data Categories
! width="80px" style="text-align:center " |EPIP
! width="80px" | AU
! width="80px" |AT
! width="80px" |ΒΕ
! width="80px" |HR
! width="80px" |DK
! width="80px" |FR
! width="80px" |IT
! width="80px" |NL
! width="150px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |PT
! width="80px" |SI
! width="80px" |CH
! width="80px" |GB
|-
|[[#Data categories|LOS 2-1]]
|
|
|
|
| style="text-align:center;" |✅
|
| style="text-align:center;" |for off-street only
| style="text-align:center " |✅
|
|
|
| |
| style="text-align:center;" |partially covered
|
|-
|[[#Data categories|LOS 2-2]]||
| ||
|
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
| style="text-align:center;" |partially covered||
|-
|[[#Data categories|LOS 2-3]]
|
|
|
|
| style="text-align:center " |✅
|
|
| style="text-align:center " |✅
|
|
|
|
| style="text-align:center;" |partially covered
|
|-
|[[#Data categories|LOS 2-4]]||
| ||
|
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " | ✅
| style="text-align:center;" |partially covered||
|-
|[[#Data categories|LOS 2-5]]||
| ||
|
| style="text-align:center " |✅|| style="text-align:center " |✅
| style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
| style="text-align:center;" |partially covered||
|-
|[[#Data categories|LOS 2-6]]||
| ||
|
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |in off-street car parks only|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
|
|
|-
|[[#Data categories|LOS 2-7]]
|
|
|
|
| style="text-align:center " |✅
|
|
| style="text-align:center " |✅
|
|
|
|
|
|
|-
|[[#Data categories|LOS 2-8]]||
| ||
|
| style="text-align:center " |✅|| || style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
| ||
|-
|[[#Data categories|LOS 2-9]]
|
|
|
|
| style="text-align:center " |✅
|
| style="text-align:center " |✅
| style="text-align:center " |✅
|
| style="text-align:center " | ✅
|
| style="text-align:center " |✅
|
|
|-
|[[#Data categories|LOS 2-10]]||
| style="text-align:center;" |✅||
|
| || || style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " | ✅
| || style="text-align:center " |✅
|-
|[[#Data categories|LOS 2-11]]||
| style="text-align:center;" |✅||
| style="text-align:center " |✅
| || || style="text-align:center " | ✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
| || style="text-align:center " |✅
|-
|[[#Data categories|LOS 2-12]]||
| ||
|
| || || style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
| || style="text-align:center " | ✅
|-
|[[#Data categories|LOS 2-13]]||
| ||
| style="text-align:center " |✅
| || style="text-align:center " |✅|| style="text-align:center " | ✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
| || style="text-align:center " |✅
|-
|}

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

{| class="wikitable" style="width:70%"
|-
! width="80px" |Data Categories
! width="80px" style="text-align:center " |EPIP
! width="80px" |AU
! width="80px" |AT
! width="80px" |BE
! width="80px" |HR
! width="80px" |DK
! width="80px" |FR
! width="80px" |IT
! width="80px" |NL
! width="150px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |PT
! width="80px" |SI
! width="80px" |CH
! width="80px" |GB
|-
|[[#Data categories|LOS 3-1]]||
| ||
| style="text-align:center " |✅

| style="text-align:center " | ✅|| || style="text-align:center " |✅ || style="text-align:center " |✅|| || style="text-align:center " |✅|| ||
| || style="text-align:center " | ✅
|-
|[[#Data categories|LOS 3-2]]||
| ||
|
| style="text-align:center " |✅|| || style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| ||
| || style="text-align:center " |✅
|-
|[[#Data categories|LOS 3-3]]||
| ||
|
| || || style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| ||
| || style="text-align:center " |✅
|-
|[[#Data categories|LOS 3-4]]
|
|
|
|
|
|
| style="text-align:center;" |✅
| style="text-align:center " |✅
|
|
|
|
|
|
|-
|[[#Data categories|LOS 3-5]]
|
|
|
|
|
|
| style="text-align:center;" |✅
|
|
|
|
|
|
|
|-
|[[#Data categories|LOS 3-6]]
|
|
|
|
|
|
| style="text-align:center;" |✅
|
|
|
|
|
| style="text-align:center;" |✅
|
|-
|[[#Data categories|LOS 3-7]]||
| ||
|
| || || || || || style="text-align:center " |✅|| ||
| ||
|-
|[[#Data categories|LOS 3-8]]||
| ||
|
| || || style="text-align:center;" |✅|| || || style="text-align:center " |✅|| ||
| ||
|-
|[[#Data categories|LOS 3-9]]||
| ||
|
| || || style="text-align:center;" |✅|| || || style="text-align:center " |✅|| ||
| ||
|-
|[[#Data categories|LOS 3-10]]||
| ||
|
| || || || || || style="text-align:center " |✅|| ||
| style="text-align:center;" |N/A||
|-
|}

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

⚠️ If you believe that your use cases are resolved in an existing profile, it is highly recommended to '''adopt an existing solution''' and cooperate with the corresponding entity. You will save resources while you will ensure that your profile is interoperable.

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

=SIRI National profiles inventory 🌐=

National profiles are specified to cover the national needs. To help implementation, DATA4PT is also in process of delivering SIRI EU minimum profile, in collaboration with relevant CEN group. DATA4PT has prepared a table with the currently available SIRI national profiles, including an overview of data categories that are currently covered. For data categories relevant to static data check the [NeTEx Profiles Inventory https://data4pt.org/w/index.php?title=NeTEX#NeTEx_national_and_EU_minimum_profiles_inventory].

==Published profiles==

{| class="wikitable" style="width : 50%"
|-
!Profile Name!!Status/
Availability
!EU Minimum profile based*!!EU Minimum SIRI profile compatible** !!Documentation
|-
|Australia - Victoria (AU)
|Specified but not yet in operation
| style="text-align:center " |✅
| style="text-align:center " |✅
|
|-
|Croatia (HR)
|Using an existing profile
|
| style="text-align:center " |✅
|
|-
|France (FR)||Specified and in use
| style="text-align:center " |✅|| style="text-align:center;" | ||[https://normes.transport.data.gouv.fr/normes/siri/profil-france/ French SIRI profile]
|-
|Italy (IT)
| Specified and in use
| style="text-align:center " |✅
|
|[https://github.com/5Tsrl/siri-italian-profile/tree/main/Linee%20guida Italian SIRI profile]
|-
|Netherlands (NL)||Specified but not yet in operation
| || style="text-align:center;" |✅||
|-
|Nordic (Norway, Sweden, Finland, Denmark)|| Specified and in use
| || style="text-align:center;" |✅||[https://enturas.atlassian.net/wiki/spaces/PUBLIC/pages/637370420/Nordic+SIRI+Profile Nordic SIRI profile]
|-
|UK (GB) ||Specified and in use
| || style="text-align:center;" |✅||
|-
|Switzerland (CH)
|Specified and in use
| style="text-align:center;" |✅
| style="text-align:center;" |✅
|[https://www.oev-info.ch/sites/default/files/2023-04/siri_realisation-guide_pt_ch_v0.9.0.pdf SIRI-ET/PT][https://www.oev-info.ch/sites/default/files/2024-07/realization_guide_siri-sx_oev_schweiz_v1.0.pdf SIRI-SX]
|}
<nowiki>*</nowiki>Profiles of this category have been specified based on EU Minimum profile and are based on XML technology as EU profiles.

<nowiki>**</nowiki> Profiles of this category have been specified either before the definition of EU Minimum profile, but they have been used to define the EU one, and/or after EU profiles and need conversion or adaptation to be interoperable.
==Data categories==

''Data categories are identified based on [https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex%3A32024R0490 MMTIS EU Regulation 490/2024]''
{| class="mw-collapsible mw-collapsed wikitable" style="width : 60%"
|+ style="white-space:nowrap; border:1px solid; padding:3px;" |Data categories table.
|-
!Level of service (LOS)!!Types of the dynamic travel and traffic data
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Dynamic data - Level of service 1 (LOS 1 )'''
|-
| colspan="2" |'''a. Passing times, trip plans and auxiliary information'''
|-
| LOS 1-1||Disruptions, such as network closures and/or diversions, and when possible, the reason
|-
|LOS 1-2||Real-time status information, such as estimated departure and arrival times of services, delays, cancellations, guaranteed connections monitoring
|-
|LOS 1-3||Status of access node features (including dynamic platform information, operational lifts/escalators, closed entrances and exit locations) – for scheduled transport
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Dynamic data - Level of service 2 (LOS 2)'''
|-
|LOS 2-1||'''a. Information service on parking tariffs – for transport on demand and personal transport'''
|-
| colspan="2" |'''b. Availability check and location – for transport on demand and personal transport where relevant'''
|-
|LOS 2-2||Car-sharing availability and location, bike-sharing availability and location, scooter-sharing availability and location, and other vehicle-sharing availability and location
|-
|LOS 2-3||Car parking spaces available (on and off-street)
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Dynamic data - Level of service 3 (LOS 3''')
|-
|LOS 3-1|| Occupancy information of the vehicle – for scheduled transport and transport on demand where relevant
|}

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

{| class="wikitable" style="width : 30%"
|-
!Data Categories
! width="80px" |AU
! width="80px" |HR
! width="80px" |FR
! width="80px" |IT
! width="80px" |NL
! width="300px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |GB
! width="80px" |CH
|-
|[[#Data categories|LOS 1-1]]
| style="text-align:center " |✅|| || style="text-align:center " |✅
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅ dynamic platform is included || style="text-align:center " |✅
| style="text-align:center;" |✅
|-
|[[#Data categories|LOS 1-2]]
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅ dynamic platform is included || style="text-align:center " |✅
| style="text-align:center;" |✅
|-
|[[#Data categories|LOS 1-3]]
| || || style="text-align:center " |✅
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅ dynamic platform is included || style="text-align:center " |
| style="text-align:center;" |✅
via SX
|-
|}

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

{| class="wikitable" style="width : 30%"
|-
!Data Categories
! width="80px" |AU
! width="80px" |HR
! width="80px" | FR
! width="80px" |IT
! width="80px" |NL
! width="300px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |GB
! width="80px" |CH
|-
|[[#Data categories|LOS 2-1]]
|
|
|
|
|
|
|
|
|-
|[[#Data categories|LOS 2-2]]
| || || style="text-align:center " |only for car sharing and bike sharing
| style="text-align:center " |✅|| || style="text-align:center " |✅||
|
|-
|[[#Data categories|LOS 2-3]]
| || || style="text-align:center " |off-street only
| style="text-align:center " |✅|| || style="text-align:center " |✅||
|
|-
|}

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

{| class="wikitable" style="width : 30%"
|-
!Data Categories
! width="80px" |AU
! width="80px" |FR
! width="80px" |IT
! width="80px" |NL
! width="300px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |GB
! width="80px" |CH
|-
|[[#Data categories|LOS 3-1]]
| style="text-align:center " |✅
| style="text-align:center " |✅
| style="text-align:center " |✅
|
|
|
|
|}

⚠️ If you believe that your use cases are resolved in an existing profile, it is highly recommended to '''adopt an existing solution''' and cooperate with the corresponding entity. You will save resources while you will ensure that your profile is interoperable.

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

=Implementations per Country=
Currently, the implementations of NeTEx and SIRI are documented for the following countries:

====== [[Australia]] ======

====== [[Belgium]] ======

====== [[Croatia]] ======

====== [[Denmark]] ======

====== [[France]] ======

====== [[Italy]] ======

====== [[Portugal]] ======

====== [[Slovenia]] ======

====== [[Sweden]] ======

====== [[Switzerland]] ======

National Implementations

2024-10-08T13:21:12Z

Anonymous:

= NeTEx national profiles inventory 🌐 =

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

== Published profiles ==

{| class="wikitable" style="width : 60%"
|-
! width="150px"| Profile Name
!Status/
Availability
! width="100px" | NeTEx EPIP Based* !! width="100px" | NeTEx EPIP Compatible**
! width="300px" | Documentation
|-
| Australia - Victoria (AU)
|Specified but not yet in operation
| style="text-align:center;" |✅
| style="text-align:center;" |✅
|
|-
|Austria (AT)
|Specified but not yet in operation|| style="text-align:center;" |✅|| ||[https://mobilitaetsverbuende.atlassian.net/wiki/spaces/NET/overview Austrian profile]
|-
|Belgium (BE)
|Specified but not yet in operation|| style="text-align:center;" |✅|| ||[https://github.com/Informatievlaanderen/OSLOthema-mobiliteitDienstregelingEnPlanning GitHUb]
[https://purl.eu/doc/applicationprofile/netex-belgium/timetables-ap/ AP-Timetables]

[https://purl.eu/doc/applicationprofile/netex-belgium/stopplaces-ap/ AP-Stops]

[https://purl.eu/doc/applicationprofile/netex-belgium/vehiclescheduling-ap/ AP-Vehicle Scheduling]

[https://purl.eu/ns/mobility/timetables-and-planning/ AP-TimetablesAndPlanning]

[https://github.com/Informatievlaanderen/OSLOthema-mobiliteitDienstregelingEnPlanning/tree/master/resources/DataExamples Data examples]
|-
|Croatia (HR)
|Specified and in use
| style="text-align:center;" | ✅
| style="text-align:center;" |✅
|[https://www.promet-info.hr/en NPT - Croatian NAP]
|-
|Denmark (DK)
|Specified but not yet in operation|| style="text-align:center;" |✅|| ||[https://www.trafikstyrelsen.dk/Media/638013312835439194/Vejledning%20om%20brug%20af%20NeTEx.pdf Denmark profile] - [https://www.trafikstyrelsen.dk/arbejdsomraader/kollektiv-trafik/statistik-og-data/krav-til-udstilling-af-data-til-rejseplanlaegning NAP in Denmark]
|-
|France (FR)
|Specified and in use|| || style="text-align:center;" |✅||[https://normes.transport.data.gouv.fr/normes/netex/ French profile] - [https://normes.transport.data.gouv.fr/normes/netex/elements_communs/ Common profile] - [https://normes.transport.data.gouv.fr/normes/netex/arrets/ Stop profile] - [https://normes.transport.data.gouv.fr/normes/netex/reseaux/ Network profile] - [https://normes.transport.data.gouv.fr/normes/netex/horaires/ Timetable profile] - [https://normes.transport.data.gouv.fr/normes/netex/tarifs/ Fare profile] - [https://normes.transport.data.gouv.fr/normes/netex/parkings/ Parking profile] - [https://normes.transport.data.gouv.fr/normes/netex/accessibilite/ Accessibility profile]
|-
|Italy (IT)
|Specified and in use|| style="text-align:center;" |✅||
|[https://github.com/5Tsrl/netex-italian-profile/tree/main/Linee%20guida Italian profile]
|-
|Netherlands (NL)
|Specified but not yet in operation|| style="text-align:center;" |✅|| ||[https://bison.dova.nu/standaarden/nederlands-netex-profiel Netherlands profile] - [https://bison.dova.nu/sites/default/files/bison_prijzen_producten_en_tarieven_v8.1.3.0_release.pdf Bison Fares]
|-
| Nordic (Norway, Sweden, Finland, Denmark)
|Specified and in use|| || style="text-align:center;" |✅||[https://enturas.atlassian.net/wiki/spaces/PUBLIC/pages/728891481/Nordic+NeTEx+Profile Nordic profile]
|-
|Portugal (PT)
|Specified and in use|| || ||[https://ptprofiles.azurewebsites.net/netex-profile Portuguese profile]
|-
| Slovenija (SI)
|Specified but not yet in operation|| || style="text-align:center " |✅||[https://www.nap.si/_resources/profiles/NeTEx_SI_Profile_v2.pdf Slovenian profile]
|-
|Switzerland (CH)
|Specified and in use
|
|
|[https://www.oev-info.ch/sites/default/files/2024-05/NeTEx_Core-Realisation_Guide_TP_Suisse-v1.00.pdf Swiss profile]
|-
|UK (GB)
|Specified and in use|| || style="text-align:center " |✅||[http://netex.uk/farexchange/ UK profile] - [http://netex.uk/farexchange/doc/uk_profile/DfT-NeTEx-1-Fares-Intro-2019.06.17-v0.09.pdf Introduction] - [http://netex.uk/farexchange/doc/uk_profile/DfT-NeTEx-2-Base_Spec-2019.06.30-v0.14.pdf Stop and Timetables] - [http://netex.uk/farexchange/doc/uk_profile/DfT-NeTEx-3-Fares_Spec-2019.06.17-v0.17.pdf Fares]
|-
|Ireland (IE)
|Specified and in use|| || ||[https://netex.ie/ Irish profile] - [http://netex.uk/netexie/doc/EIRE_NP/NTA-NeTEx-1-Spec-2020.08.12-v0.22.pdf Profile Elements] - [http://netex.uk/netexie/doc/EIRE_NP/NTA-NeTEx-2-Mappings-2020.08.06-v0.22.pdf Profile Data Mappings]
|-
|Czech Republic (CZ)
|Specified but not yet in operation
| style="text-align:center " |✅
|
|
|}
<nowiki>*</nowiki>Profiles of this category have been specified based on EU Minimum profile and are based on XML technology as EU profiles.

<nowiki>**</nowiki> Profiles of this category have been specified either before the definition of EU Minimum profile, but they have been used to define the EU one, and/or after EU profiles and need conversion or adaptation to be interoperable.
==Data categories==

''Data categories are identified based on [https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex%3A32024R0490 MMTIS EU Regulation 490/2024]''
{| class="mw-collapsible mw-collapsed wikitable" style="width:70%"
|+ style="white-space:nowrap; border:1px solid; padding:3px;" | Data categories table.
|-
!Level of service (LOS)!!Static data
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Static data - Level of service 1 (LOS 1 )'''
|-
| colspan="2" |'''a. Location search (origin/destination)'''
|-
|LOS 1-1||Address identifiers (building number, street name, postcode)
|-
| LOS 1-2||Topographic places (city, town, village, suburb, administrative unit)
|-
|LOS 1-3||Points of interest (related to transport information) to which people may wish to travel
|-
|LOS 1-4||'''b. Trip plans: operational calendar, mapping day types to calendar dates'''
|-
| colspan="2" |'''c. Location search (access nodes) – for scheduled transport and transport on demand where relevant'''
|-
|LOS 1-5
| Identified access nodes
|-
|LOS 1-6 ||Geometry/map layout structure of access nodes

|-
| colspan="2" |'''d. Trip plan computation – for scheduled transport and transport on demand where relevant'''
|-
|LOS 1-7||Connection where interchanges may be made
|-
|LOS 1-8
|Default transfer times at interchanges
|-
|LOS 1-9||Network topology and routes/lines (topology)
|-
| LOS 1-10|| Transport operators
|-
|LOS 1-11|| Timetables
|-
|LOS 1-12||Planned interchanges between guaranteed scheduled services
|-
|LOS 1-13||Hours of operation
|-
| LOS 1-14
|Facilities of access nodes (including platform information, help desk/information points, ticket booths, lifts/stairs, entrances and exit locations)
|-
|LOS 1-15||Vehicles, including their accessibility (such as low floor, wheelchair accessible, pram accessible) and accessibility of on-board services (such as toilets)
|-
|LOS 1-16||Accessibility of access nodes, and paths within an interchange (such as existence of lifts, escalators)
|-
|LOS 1-17||Existence of assistance services (such as existence of on-site assistance)
|-
| colspan="2" |'''e. Trip plan computation'''
|-
|LOS 1-18||Road network (including segregated lanes for bus/taxi)
|-
|LOS 1-19||Cycle network (cycle tracks, cycle lanes, bus-and-cycle lanes, on-road shared with vehicles, on-path shared with pedestrians)
|-
|LOS 1-20||Pedestrian network and accessibility facilities
|-
| ||Framework data
|-
|
|
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Static data - Level of service 2 (LOS 2)'''
|-
| colspan="2" |'''a. Location search – for transport on demand and personal transport'''
|-
|LOS 2-1
|Location of parking places (on and off-street), including accessible parking places for persons with disabilities and persons with reduced mobility
|-
|LOS 2-2||Park & Ride stops
|-
|LOS 2-3
| Park & Drive stops
|-
|LOS 2-4||Bike sharing stations
|-
|LOS 2-5||Car-sharing stations
|-
| LOS 2-6
|Secure bike parking (such as locked bike garages)
|-
|LOS 2-7
|Scooter parking zones
|-
| colspan="2" |'''b. Information service'''
|-
|LOS 2-8||Where and how to buy tickets for scheduled transport, including retail channels, fulfilment methods, payment methods
|-
|LOS 2-9||Where and how to pay for parking, including retail channels, fulfilment methods, payment methods
|-
| colspan="2" |'''c. Auxiliary information – for scheduled transport and transport on demand where relevant'''
|-
|LOS 2-10 ||Basic common standard fares
- fare network data (fare zones/stops and fare stages)

- standard fare structures (point to point including daily and weekly fares, zonal fares, flat fares)
|-
|LOS 2-11||Vehicle facilities such as classes of carriage, on-board Wi-Fi.
|-
| ||
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Static data - Level of service 3 (LOS 3''')
|-
| colspan="2" |'''a. Detailed common standard and special fare query – for scheduled transport and transport on demand where relevant'''
|-
|LOS 3-1||Passenger classes (classes of passenger such as adult, child, senior, student, military/veteran, passenger with disability and passenger with reduced mobility, and qualifying conditions, and classes of travel)
|-
|LOS 3-2|| Common fare products (access rights such as zone/point-to-point including daily and weekly tickets/single/return, eligibility of access, basic usage conditions such as validity period/operator/time of travel/interchanging, standard point-to-point fares prices for different point-to-point pairs including daily and weekly fares/zonal fare prices/flat fare prices)
|-
|LOS 3-3||Special fare products (offers with additional special conditions such as promotional fares, group fares, season passes, aggregated products combining different products, and add-on products such as parking and travel, minimum stay)
|-
|LOS 3-4|| Basic commercial conditions such as refunding, replacing, exchanging or transferring
|-
|LOS 3-5||Basic booking conditions such as purchase windows, validity periods, routing restrictions zonal sequence fares, minimum stay
|-
|LOS 3-6||'''b. Information service – for transport on demand: how to book demand-responsive transport services, including retail channels, fulfilment methods, payment methods'''
|-
| colspan="2" |'''c. Trip plans'''
|-
|LOS 3-7||Detailed cycle network attributes (surface quality, side-by-side cycling, shared surface, on/off road, scenic route, “walk only”, turn or access restrictions, e.g. against flow of traffic)
|-
|LOS 3-8 ||Parameters needed to calculate an environmental factor such as greenhouse gas emissions per vehicle type or passenger mile or per distance walked
|-
|LOS 3-9||Parameters needed to calculate fuel consumption of conventional and alternative fuels
|-
|LOS 3-10
|'''d. Trip plan computation: estimated travel times by day type and time-band by transport mode/combination of transport mode'''
|-
| colspan="2" |
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Static data - Level of service 4 (LOS 4 )'''
|-
| LOS 4-1
|'''a. Historic travel and traffic data on delays – for scheduled transport and transport on demand where relevant'''
|-
| colspan="2" |'''b. Observed data on delays and passing time – for scheduled transport'''
|-
|LOS 4-2
|Length of, and when possible the reason for, delays of at least 60 minutes for rail passenger services (in accordance with Article 19 of Regulation (EU) 2021/782)
|-
|LOS 4-3
|Length of, and when possible the reason for, delays in departure of more than 90 minutes for sea and inland waterways passenger services (in accordance with Article 18 of Regulation (EU) No 1177/2010)
|-
|LOS 4-4
| Length of, and when possible the reason for, delays in departure from a terminal of more than 120 minutes for regular bus and coach passenger services with a scheduled distance of 250 km or more (in accordance with Article 19 of Regulation (EU) No 181/2011)
|-
|LOS 4-5
|Length of, and when possible the reason for, flight delays at departure of at least 120 minutes; and flight delays at arrival of at least 180 minutes (in accordance with Articles 5 and 6 of Regulation (EC) No 261/2004)
|-
| colspan="2" |'''c. Observed data on cancellations – for scheduled transport'''
|-
|LOS 4-6
|Cancellations, and when possible the reason, of rail passenger services
|-
|LOS 4-7
|Cancellations, and when possible the reason, of sea and inland waterways passenger services
|-
|LOS 4-8
|Cancellations, and when possible the reason, of regular bus and coach services with a scheduled distance of 250 km or more
|-
|LOS 4-9
|Cancellations, and when possible the reason, of flights
|-
|LOS 4-10
|'''d. Information on parking tariffs'''
|}

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

{| class="wikitable" style="width:70%"
|-
! width="80px" |Data Categories

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

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

{| class="wikitable" style="width:70%"
|-
! width="80px" |Data Categories
! width="80px" style="text-align:center " |EPIP
! width="80px" | AU
! width="80px" |AT
! width="80px" |ΒΕ
! width="80px" |HR
! width="80px" |DK
! width="80px" |FR
! width="80px" |IT
! width="80px" |NL
! width="150px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |PT
! width="80px" |SI
! width="80px" |CH
! width="80px" |GB
|-
|[[#Data categories|LOS 2-1]]
|
|
|
|
| style="text-align:center;" |✅
|
| style="text-align:center;" |for off-street only
| style="text-align:center " |✅
|
|
|
| |
| style="text-align:center;" |partially covered
|
|-
|[[#Data categories|LOS 2-2]]||
| ||
|
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
| style="text-align:center;" |partially covered||
|-
|[[#Data categories|LOS 2-3]]
|
|
|
|
| style="text-align:center " |✅
|
|
| style="text-align:center " |✅
|
|
|
|
| style="text-align:center;" |partially covered
|
|-
|[[#Data categories|LOS 2-4]]||
| ||
|
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " | ✅
| style="text-align:center;" |partially covered||
|-
|[[#Data categories|LOS 2-5]]||
| ||
|
| style="text-align:center " |✅|| style="text-align:center " |✅
| style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
| style="text-align:center;" |partially covered||
|-
|[[#Data categories|LOS 2-6]]||
| ||
|
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |in off-street car parks only|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
|
|
|-
|[[#Data categories|LOS 2-7]]
|
|
|
|
| style="text-align:center " |✅
|
|
| style="text-align:center " |✅
|
|
|
|
|
|
|-
|[[#Data categories|LOS 2-8]]||
| ||
|
| style="text-align:center " |✅|| || style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
| ||
|-
|[[#Data categories|LOS 2-9]]
|
|
|
|
| style="text-align:center " |✅
|
| style="text-align:center " |✅
| style="text-align:center " |✅
|
| style="text-align:center " | ✅
|
| style="text-align:center " |✅
|
|
|-
|[[#Data categories|LOS 2-10]]||
| style="text-align:center;" |✅||
|
| || || style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " | ✅
| || style="text-align:center " |✅
|-
|[[#Data categories|LOS 2-11]]||
| style="text-align:center;" |✅||
| style="text-align:center " |✅
| || || style="text-align:center " | ✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
| || style="text-align:center " |✅
|-
|[[#Data categories|LOS 2-12]]||
| ||
|
| || || style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
| || style="text-align:center " | ✅
|-
|[[#Data categories|LOS 2-13]]||
| ||
| style="text-align:center " |✅
| || style="text-align:center " |✅|| style="text-align:center " | ✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
| || style="text-align:center " |✅
|-
|}

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

{| class="wikitable" style="width:70%"
|-
! width="80px" |Data Categories
! width="80px" style="text-align:center " |EPIP
! width="80px" |AU
! width="80px" |AT
! width="80px" |BE
! width="80px" |HR
! width="80px" |DK
! width="80px" |FR
! width="80px" |IT
! width="80px" |NL
! width="150px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |PT
! width="80px" |SI
! width="80px" |CH
! width="80px" |GB
|-
|[[#Data categories|LOS 3-1]]||
| ||
| style="text-align:center " |✅

| style="text-align:center " | ✅|| || style="text-align:center " |✅ || style="text-align:center " |✅|| || style="text-align:center " |✅|| ||
| || style="text-align:center " | ✅
|-
|[[#Data categories|LOS 3-2]]||
| ||
|
| style="text-align:center " |✅|| || style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| ||
| || style="text-align:center " |✅
|-
|[[#Data categories|LOS 3-3]]||
| ||
|
| || || style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| ||
| || style="text-align:center " |✅
|-
|[[#Data categories|LOS 3-4]]
|
|
|
|
|
|
| style="text-align:center;" |✅
| style="text-align:center " |✅
|
|
|
|
|
|
|-
|[[#Data categories|LOS 3-5]]
|
|
|
|
|
|
| style="text-align:center;" |✅
|
|
|
|
|
|
|
|-
|[[#Data categories|LOS 3-6]]
|
|
|
|
|
|
| style="text-align:center;" |✅
|
|
|
|
|
| style="text-align:center;" |✅
|
|-
|[[#Data categories|LOS 3-7]]||
| ||
|
| || || || || || style="text-align:center " |✅|| ||
| ||
|-
|[[#Data categories|LOS 3-8]]||
| ||
|
| || || style="text-align:center;" |✅|| || || style="text-align:center " |✅|| ||
| ||
|-
|[[#Data categories|LOS 3-9]]||
| ||
|
| || || style="text-align:center;" |✅|| || || style="text-align:center " |✅|| ||
| ||
|-
|[[#Data categories|LOS 3-10]]||
| ||
|
| || || || || || style="text-align:center " |✅|| ||
| style="text-align:center;" |N/A||
|-
|}

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

⚠️ If you believe that your use cases are resolved in an existing profile, it is highly recommended to '''adopt an existing solution''' and cooperate with the corresponding entity. You will save resources while you will ensure that your profile is interoperable.

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

=SIRI National profiles inventory 🌐=

National profiles are specified to cover the national needs. To help implementation, DATA4PT is also in process of delivering SIRI EU minimum profile, in collaboration with relevant CEN group. DATA4PT has prepared a table with the currently available SIRI national profiles, including an overview of data categories that are currently covered. For data categories relevant to static data check the [NeTEx Profiles Inventory https://data4pt.org/w/index.php?title=NeTEX#NeTEx_national_and_EU_minimum_profiles_inventory].

==Published profiles==

{| class="wikitable" style="width : 50%"
|-
!Profile Name!!Status/
Availability
!EU Minimum profile based*!!EU Minimum SIRI profile compatible** !!Documentation
|-
|Australia - Victoria (AU)
|Specified but not yet in operation
| style="text-align:center " |✅
| style="text-align:center " |✅
|
|-
|Croatia (HR)
|Using an existing profile
|
| style="text-align:center " |✅
|
|-
|France (FR)||Specified and in use
| style="text-align:center " |✅|| style="text-align:center;" | ||[https://normes.transport.data.gouv.fr/normes/siri/profil-france/ French SIRI profile]
|-
|Italy (IT)
| Specified and in use
| style="text-align:center " |✅
|
|[https://github.com/5Tsrl/siri-italian-profile/tree/main/Linee%20guida Italian SIRI profile]
|-
|Netherlands (NL)||Specified but not yet in operation
| || style="text-align:center;" |✅||
|-
|Nordic (Norway, Sweden, Finland, Denmark)|| Specified and in use
| || style="text-align:center;" |✅||[https://enturas.atlassian.net/wiki/spaces/PUBLIC/pages/637370420/Nordic+SIRI+Profile Nordic SIRI profile]
|-
|UK (GB) ||Specified and in use
| || style="text-align:center;" |✅||
|-
|Switzerland (CH)
|Specified and in use
| style="text-align:center;" |✅
| style="text-align:center;" |✅
|[https://www.oev-info.ch/sites/default/files/2023-04/siri_realisation-guide_pt_ch_v0.9.0.pdf SIRI-ET/PT][https://www.oev-info.ch/sites/default/files/2024-07/realization_guide_siri-sx_oev_schweiz_v1.0.pdf SIRI-SX]
|}
<nowiki>*</nowiki>Profiles of this category have been specified based on EU Minimum profile and are based on XML technology as EU profiles.

<nowiki>**</nowiki> Profiles of this category have been specified either before the definition of EU Minimum profile, but they have been used to define the EU one, and/or after EU profiles and need conversion or adaptation to be interoperable.
==Data categories==

''Data categories are identified based on [https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex%3A32024R0490 MMTIS EU Regulation 490/2024]''
{| class="mw-collapsible mw-collapsed wikitable" style="width : 60%"
|+ style="white-space:nowrap; border:1px solid; padding:3px;" |Data categories table.
|-
!Level of service (LOS)!!Types of the dynamic travel and traffic data
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Dynamic data - Level of service 1 (LOS 1 )'''
|-
| colspan="2" |'''a. Passing times, trip plans and auxiliary information'''
|-
| LOS 1-1||Disruptions, such as network closures and/or diversions, and when possible, the reason
|-
|LOS 1-2||Real-time status information, such as estimated departure and arrival times of services, delays, cancellations, guaranteed connections monitoring
|-
|LOS 1-3||Status of access node features (including dynamic platform information, operational lifts/escalators, closed entrances and exit locations) – for scheduled transport
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Dynamic data - Level of service 2 (LOS 2)'''
|-
|LOS 2-1||'''a. Information service on parking tariffs – for transport on demand and personal transport'''
|-
| colspan="2" |'''b. Availability check and location – for transport on demand and personal transport where relevant'''
|-
|LOS 2-2||Car-sharing availability and location, bike-sharing availability and location, scooter-sharing availability and location, and other vehicle-sharing availability and location
|-
|LOS 2-3||Car parking spaces available (on and off-street)
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Dynamic data - Level of service 3 (LOS 3''')
|-
|LOS 3-1|| Occupancy information of the vehicle – for scheduled transport and transport on demand where relevant
|}

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

{| class="wikitable" style="width : 30%"
|-
!Data Categories
! width="80px" |AU
! width="80px" |HR
! width="80px" |FR
! width="80px" |IT
! width="80px" |NL
! width="300px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |GB
! width="80px" |CH
|-
|[[#Data categories|LOS 1-1]]
| style="text-align:center " |✅|| || style="text-align:center " |✅
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅ dynamic platform is included || style="text-align:center " |✅
| style="text-align:center;" |✅
|-
|[[#Data categories|LOS 1-2]]
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅ dynamic platform is included || style="text-align:center " |✅
| style="text-align:center;" |✅
|-
|[[#Data categories|LOS 1-3]]
| || || style="text-align:center " |✅
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅ dynamic platform is included || style="text-align:center " |
| style="text-align:center;" |✅
via SX
|-
|}

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

{| class="wikitable" style="width : 30%"
|-
!Data Categories
! width="80px" |AU
! width="80px" |HR
! width="80px" | FR
! width="80px" |IT
! width="80px" |NL
! width="300px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |GB
! width="80px" |CH
|-
|[[#Data categories|LOS 2-1]]
|
|
|
|
|
|
|
|
|-
|[[#Data categories|LOS 2-2]]
| || || style="text-align:center " |only for car sharing and bike sharing
| style="text-align:center " |✅|| || style="text-align:center " |✅||
|
|-
|[[#Data categories|LOS 2-3]]
| || || style="text-align:center " |off-street only
| style="text-align:center " |✅|| || style="text-align:center " |✅||
|
|-
|}

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

{| class="wikitable" style="width : 30%"
|-
!Data Categories
! width="80px" |AU
! width="80px" |FR
! width="80px" |IT
! width="80px" |NL
! width="300px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |GB
! width="80px" |CH
|-
|[[#Data categories|LOS 3-1]]
| style="text-align:center " |✅
| style="text-align:center " |✅
| style="text-align:center " |✅
|
|
|
|
|}

⚠️ If you believe that your use cases are resolved in an existing profile, it is highly recommended to '''adopt an existing solution''' and cooperate with the corresponding entity. You will save resources while you will ensure that your profile is interoperable.

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

=Implementations per Country=
Currently, the implementations of NeTEx and SIRI are documented for the following countries:

====== [[Australia]] ======

====== [[Belgium]] ======

====== [[Croatia]] ======

====== [[Denmark]] ======

====== [[France]] ======

====== [[Italy]] ======

====== [[Portugal]] ======

====== [[Slovenia]] ======

====== [[Sweden]] ======

====== [[Switzerland]] ======

National Implementations

2024-10-08T13:17:38Z

Anonymous: /* Implementations per Country */

= NeTEx national profiles inventory 🌐 =

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

== Published profiles ==

{| class="wikitable" style="width : 60%"
|-
! width="150px"| Profile Name
!Status/
Availability
! width="100px" | NeTEx EPIP Based* !! width="100px" | NeTEx EPIP Compatible**
! width="300px" | Documentation
|-
| Australia - Victoria (AU)
|Specified but not yet in operation
| style="text-align:center;" |✅
| style="text-align:center;" |✅
|
|-
|Austria (AT)
|Specified but not yet in operation|| style="text-align:center;" |✅|| ||[https://mobilitaetsverbuende.atlassian.net/wiki/spaces/NET/overview Austrian profile]
|-
|Belgium (BE)
|Specified but not yet in operation|| style="text-align:center;" |✅|| ||[https://github.com/Informatievlaanderen/OSLOthema-mobiliteitDienstregelingEnPlanning GitHUb]
[https://purl.eu/doc/applicationprofile/netex-belgium/timetables-ap/ AP-Timetables]

[https://purl.eu/doc/applicationprofile/netex-belgium/stopplaces-ap/ AP-Stops]

[https://purl.eu/doc/applicationprofile/netex-belgium/vehiclescheduling-ap/ AP-Vehicle Scheduling]

[https://purl.eu/ns/mobility/timetables-and-planning/ AP-TimetablesAndPlanning]

[https://github.com/Informatievlaanderen/OSLOthema-mobiliteitDienstregelingEnPlanning/tree/master/resources/DataExamples Data examples]
|-
|Croatia (HR)
|Specified and in use
| style="text-align:center;" | ✅
| style="text-align:center;" |✅
|[https://www.promet-info.hr/en NPT - Croatian NAP]
|-
|Denmark (DK)
|Specified but not yet in operation|| style="text-align:center;" |✅|| ||[https://www.trafikstyrelsen.dk/Media/638013312835439194/Vejledning%20om%20brug%20af%20NeTEx.pdf Denmark profile] - [https://www.trafikstyrelsen.dk/arbejdsomraader/kollektiv-trafik/statistik-og-data/krav-til-udstilling-af-data-til-rejseplanlaegning NAP in Denmark]
|-
|France (FR)
|Specified and in use|| || style="text-align:center;" |✅||[https://normes.transport.data.gouv.fr/normes/netex/ French profile] - [https://normes.transport.data.gouv.fr/normes/netex/elements_communs/ Common profile] - [https://normes.transport.data.gouv.fr/normes/netex/arrets/ Stop profile] - [https://normes.transport.data.gouv.fr/normes/netex/reseaux/ Network profile] - [https://normes.transport.data.gouv.fr/normes/netex/horaires/ Timetable profile] - [https://normes.transport.data.gouv.fr/normes/netex/tarifs/ Fare profile] - [https://normes.transport.data.gouv.fr/normes/netex/parkings/ Parking profile] - [https://normes.transport.data.gouv.fr/normes/netex/accessibilite/ Accessibility profile]
|-
|Italy (IT)
|Specified and in use|| style="text-align:center;" |✅||
|[https://github.com/5Tsrl/netex-italian-profile/tree/main/Linee%20guida Italian profile]
|-
|Netherlands (NL)
|Specified but not yet in operation|| style="text-align:center;" |✅|| ||[https://bison.dova.nu/standaarden/nederlands-netex-profiel Netherlands profile] - [https://bison.dova.nu/sites/default/files/bison_prijzen_producten_en_tarieven_v8.1.3.0_release.pdf Bison Fares]
|-
| Nordic (Norway, Sweden, Finland, Denmark)
|Specified and in use|| || style="text-align:center;" |✅||[https://enturas.atlassian.net/wiki/spaces/PUBLIC/pages/728891481/Nordic+NeTEx+Profile Nordic profile]
|-
|Portugal (PT)
|Specified and in use|| || ||[https://ptprofiles.azurewebsites.net/netex-profile Portuguese profile]
|-
| Slovenija (SI)
|Specified but not yet in operation|| || style="text-align:center " |✅||[https://www.nap.si/_resources/profiles/NeTEx_SI_Profile_v2.pdf Slovenian profile]
|-
|Switzerland (CH)
|Specified and in use
|
|
|[https://www.oev-info.ch/sites/default/files/2024-05/NeTEx_Core-Realisation_Guide_TP_Suisse-v1.00.pdf Swiss profile]
|-
|UK (GB)
|Specified and in use|| || style="text-align:center " |✅||[http://netex.uk/farexchange/ UK profile] - [http://netex.uk/farexchange/doc/uk_profile/DfT-NeTEx-1-Fares-Intro-2019.06.17-v0.09.pdf Introduction] - [http://netex.uk/farexchange/doc/uk_profile/DfT-NeTEx-2-Base_Spec-2019.06.30-v0.14.pdf Stop and Timetables] - [http://netex.uk/farexchange/doc/uk_profile/DfT-NeTEx-3-Fares_Spec-2019.06.17-v0.17.pdf Fares]
|-
|Ireland (IE)
|Specified and in use|| || ||[https://netex.ie/ Irish profile] - [http://netex.uk/netexie/doc/EIRE_NP/NTA-NeTEx-1-Spec-2020.08.12-v0.22.pdf Profile Elements] - [http://netex.uk/netexie/doc/EIRE_NP/NTA-NeTEx-2-Mappings-2020.08.06-v0.22.pdf Profile Data Mappings]
|-
|Czech Republic (CZ)
|Specified but not yet in operation
| style="text-align:center " |✅
|
|
|}
<nowiki>*</nowiki>Profiles of this category have been specified based on EU Minimum profile and are based on XML technology as EU profiles.

<nowiki>**</nowiki> Profiles of this category have been specified either before the definition of EU Minimum profile, but they have been used to define the EU one, and/or after EU profiles and need conversion or adaptation to be interoperable.
==Data categories==

''Data categories are identified based on [https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex%3A32024R0490 MMTIS EU Regulation 490/2024]''
{| class="mw-collapsible mw-collapsed wikitable" style="width:70%"
|+ style="white-space:nowrap; border:1px solid; padding:3px;" | Data categories table.
|-
!Level of service (LOS)!!Static data
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Static data - Level of service 1 (LOS 1 )'''
|-
| colspan="2" |'''a. Location search (origin/destination)'''
|-
|LOS 1-1||Address identifiers (building number, street name, postcode)
|-
| LOS 1-2||Topographic places (city, town, village, suburb, administrative unit)
|-
|LOS 1-3||Points of interest (related to transport information) to which people may wish to travel
|-
|LOS 1-4||'''b. Trip plans: operational calendar, mapping day types to calendar dates'''
|-
| colspan="2" |'''c. Location search (access nodes) – for scheduled transport and transport on demand where relevant'''
|-
|LOS 1-5
| Identified access nodes
|-
|LOS 1-6 ||Geometry/map layout structure of access nodes

|-
| colspan="2" |'''d. Trip plan computation – for scheduled transport and transport on demand where relevant'''
|-
|LOS 1-7||Connection where interchanges may be made
|-
|LOS 1-8
|Default transfer times at interchanges
|-
|LOS 1-9||Network topology and routes/lines (topology)
|-
| LOS 1-10|| Transport operators
|-
|LOS 1-11|| Timetables
|-
|LOS 1-12||Planned interchanges between guaranteed scheduled services
|-
|LOS 1-13||Hours of operation
|-
| LOS 1-14
|Facilities of access nodes (including platform information, help desk/information points, ticket booths, lifts/stairs, entrances and exit locations)
|-
|LOS 1-15||Vehicles, including their accessibility (such as low floor, wheelchair accessible, pram accessible) and accessibility of on-board services (such as toilets)
|-
|LOS 1-16||Accessibility of access nodes, and paths within an interchange (such as existence of lifts, escalators)
|-
|LOS 1-17||Existence of assistance services (such as existence of on-site assistance)
|-
| colspan="2" |'''e. Trip plan computation'''
|-
|LOS 1-18||Road network (including segregated lanes for bus/taxi)
|-
|LOS 1-19||Cycle network (cycle tracks, cycle lanes, bus-and-cycle lanes, on-road shared with vehicles, on-path shared with pedestrians)
|-
|LOS 1-20||Pedestrian network and accessibility facilities
|-
| ||Framework data
|-
|
|
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Static data - Level of service 2 (LOS 2)'''
|-
| colspan="2" |'''a. Location search – for transport on demand and personal transport'''
|-
|LOS 2-1
|Location of parking places (on and off-street), including accessible parking places for persons with disabilities and persons with reduced mobility
|-
|LOS 2-2||Park & Ride stops
|-
|LOS 2-3
| Park & Drive stops
|-
|LOS 2-4||Bike sharing stations
|-
|LOS 2-5||Car-sharing stations
|-
| LOS 2-6
|Secure bike parking (such as locked bike garages)
|-
|LOS 2-7
|Scooter parking zones
|-
| colspan="2" |'''b. Information service'''
|-
|LOS 2-8||Where and how to buy tickets for scheduled transport, including retail channels, fulfilment methods, payment methods
|-
|LOS 2-9||Where and how to pay for parking, including retail channels, fulfilment methods, payment methods
|-
| colspan="2" |'''c. Auxiliary information – for scheduled transport and transport on demand where relevant'''
|-
|LOS 2-10 ||Basic common standard fares
- fare network data (fare zones/stops and fare stages)

- standard fare structures (point to point including daily and weekly fares, zonal fares, flat fares)
|-
|LOS 2-11||Vehicle facilities such as classes of carriage, on-board Wi-Fi.
|-
| ||
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Static data - Level of service 3 (LOS 3''')
|-
| colspan="2" |'''a. Detailed common standard and special fare query – for scheduled transport and transport on demand where relevant'''
|-
|LOS 3-1||Passenger classes (classes of passenger such as adult, child, senior, student, military/veteran, passenger with disability and passenger with reduced mobility, and qualifying conditions, and classes of travel)
|-
|LOS 3-2|| Common fare products (access rights such as zone/point-to-point including daily and weekly tickets/single/return, eligibility of access, basic usage conditions such as validity period/operator/time of travel/interchanging, standard point-to-point fares prices for different point-to-point pairs including daily and weekly fares/zonal fare prices/flat fare prices)
|-
|LOS 3-3||Special fare products (offers with additional special conditions such as promotional fares, group fares, season passes, aggregated products combining different products, and add-on products such as parking and travel, minimum stay)
|-
|LOS 3-4|| Basic commercial conditions such as refunding, replacing, exchanging or transferring
|-
|LOS 3-5||Basic booking conditions such as purchase windows, validity periods, routing restrictions zonal sequence fares, minimum stay
|-
|LOS 3-6||'''b. Information service – for transport on demand: how to book demand-responsive transport services, including retail channels, fulfilment methods, payment methods'''
|-
| colspan="2" |'''c. Trip plans'''
|-
|LOS 3-7||Detailed cycle network attributes (surface quality, side-by-side cycling, shared surface, on/off road, scenic route, “walk only”, turn or access restrictions, e.g. against flow of traffic)
|-
|LOS 3-8 ||Parameters needed to calculate an environmental factor such as greenhouse gas emissions per vehicle type or passenger mile or per distance walked
|-
|LOS 3-9||Parameters needed to calculate fuel consumption of conventional and alternative fuels
|-
|LOS 3-10
|'''d. Trip plan computation: estimated travel times by day type and time-band by transport mode/combination of transport mode'''
|-
| colspan="2" |
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Static data - Level of service 4 (LOS 4 )'''
|-
| LOS 4-1
|'''a. Historic travel and traffic data on delays – for scheduled transport and transport on demand where relevant'''
|-
| colspan="2" |'''b. Observed data on delays and passing time – for scheduled transport'''
|-
|LOS 4-2
|Length of, and when possible the reason for, delays of at least 60 minutes for rail passenger services (in accordance with Article 19 of Regulation (EU) 2021/782)
|-
|LOS 4-3
|Length of, and when possible the reason for, delays in departure of more than 90 minutes for sea and inland waterways passenger services (in accordance with Article 18 of Regulation (EU) No 1177/2010)
|-
|LOS 4-4
| Length of, and when possible the reason for, delays in departure from a terminal of more than 120 minutes for regular bus and coach passenger services with a scheduled distance of 250 km or more (in accordance with Article 19 of Regulation (EU) No 181/2011)
|-
|LOS 4-5
|Length of, and when possible the reason for, flight delays at departure of at least 120 minutes; and flight delays at arrival of at least 180 minutes (in accordance with Articles 5 and 6 of Regulation (EC) No 261/2004)
|-
| colspan="2" |'''c. Observed data on cancellations – for scheduled transport'''
|-
|LOS 4-6
|Cancellations, and when possible the reason, of rail passenger services
|-
|LOS 4-7
|Cancellations, and when possible the reason, of sea and inland waterways passenger services
|-
|LOS 4-8
|Cancellations, and when possible the reason, of regular bus and coach services with a scheduled distance of 250 km or more
|-
|LOS 4-9
|Cancellations, and when possible the reason, of flights
|-
|LOS 4-10
|'''d. Information on parking tariffs'''
|}

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

{| class="wikitable" style="width:70%"
|-
! width="80px" |Data Categories

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

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

{| class="wikitable" style="width:70%"
|-
! width="80px" |Data Categories
! width="80px" style="text-align:center " |EPIP
! width="80px" | AU
! width="80px" |AT
! width="80px" |ΒΕ
! width="80px" |HR
! width="80px" |DK
! width="80px" |FR
! width="80px" |IT
! width="80px" |NL
! width="150px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |PT
! width="80px" |SI
! width="80px" |CH
! width="80px" |GB
|-
|[[#Data categories|LOS 2-1]]
|
|
|
|
| style="text-align:center;" |✅
|
| style="text-align:center;" |for off-street only
| style="text-align:center " |✅
|
|
|
| |
| style="text-align:center;" |partially covered
|
|-
|[[#Data categories|LOS 2-2]]||
| ||
|
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
| style="text-align:center;" |partially covered||
|-
|[[#Data categories|LOS 2-3]]
|
|
|
|
| style="text-align:center " |✅
|
|
| style="text-align:center " |✅
|
|
|
|
| style="text-align:center;" |partially covered
|
|-
|[[#Data categories|LOS 2-4]]||
| ||
|
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " | ✅
| style="text-align:center;" |partially covered||
|-
|[[#Data categories|LOS 2-5]]||
| ||
|
| style="text-align:center " |✅|| style="text-align:center " |✅
| style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
| style="text-align:center;" |partially covered||
|-
|[[#Data categories|LOS 2-6]]||
| ||
|
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |in off-street car parks only|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
|
|
|-
|[[#Data categories|LOS 2-7]]
|
|
|
|
| style="text-align:center " |✅
|
|
| style="text-align:center " |✅
|
|
|
|
|
|
|-
|[[#Data categories|LOS 2-8]]||
| ||
|
| style="text-align:center " |✅|| || style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
| ||
|-
|[[#Data categories|LOS 2-9]]
|
|
|
|
| style="text-align:center " |✅
|
| style="text-align:center " |✅
| style="text-align:center " |✅
|
| style="text-align:center " | ✅
|
| style="text-align:center " |✅
|
|
|-
|[[#Data categories|LOS 2-10]]||
| style="text-align:center;" |✅||
|
| || || style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " | ✅
| || style="text-align:center " |✅
|-
|[[#Data categories|LOS 2-11]]||
| style="text-align:center;" |✅||
| style="text-align:center " |✅
| || || style="text-align:center " | ✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
| || style="text-align:center " |✅
|-
|[[#Data categories|LOS 2-12]]||
| ||
|
| || || style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
| || style="text-align:center " | ✅
|-
|[[#Data categories|LOS 2-13]]||
| ||
| style="text-align:center " |✅
| || style="text-align:center " |✅|| style="text-align:center " | ✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
| || style="text-align:center " |✅
|-
|}

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

{| class="wikitable" style="width:70%"
|-
! width="80px" |Data Categories
! width="80px" style="text-align:center " |EPIP
! width="80px" |AU
! width="80px" |AT
! width="80px" |BE
! width="80px" |HR
! width="80px" |DK
! width="80px" |FR
! width="80px" |IT
! width="80px" |NL
! width="150px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |PT
! width="80px" |SI
! width="80px" |CH
! width="80px" |GB
|-
|[[#Data categories|LOS 3-1]]||
| ||
| style="text-align:center " |✅

| style="text-align:center " | ✅|| || style="text-align:center " |✅ || style="text-align:center " |✅|| || style="text-align:center " |✅|| ||
| || style="text-align:center " | ✅
|-
|[[#Data categories|LOS 3-2]]||
| ||
|
| style="text-align:center " |✅|| || style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| ||
| || style="text-align:center " |✅
|-
|[[#Data categories|LOS 3-3]]||
| ||
|
| || || style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| ||
| || style="text-align:center " |✅
|-
|[[#Data categories|LOS 3-4]]
|
|
|
|
|
|
| style="text-align:center;" |✅
| style="text-align:center " |✅
|
|
|
|
|
|
|-
|[[#Data categories|LOS 3-5]]
|
|
|
|
|
|
| style="text-align:center;" |✅
|
|
|
|
|
|
|
|-
|[[#Data categories|LOS 3-6]]
|
|
|
|
|
|
| style="text-align:center;" |✅
|
|
|
|
|
| style="text-align:center;" |✅
|
|-
|[[#Data categories|LOS 3-7]]||
| ||
|
| || || || || || style="text-align:center " |✅|| ||
| ||
|-
|[[#Data categories|LOS 3-8]]||
| ||
|
| || || style="text-align:center;" |✅|| || || style="text-align:center " |✅|| ||
| ||
|-
|[[#Data categories|LOS 3-9]]||
| ||
|
| || || style="text-align:center;" |✅|| || || style="text-align:center " |✅|| ||
| ||
|-
|[[#Data categories|LOS 3-10]]||
| ||
|
| || || || || || style="text-align:center " |✅|| ||
| style="text-align:center;" |N/A||
|-
|}

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

⚠️ If you believe that your use cases are resolved in an existing profile, it is highly recommended to '''adopt an existing solution''' and cooperate with the corresponding entity. You will save resources while you will ensure that your profile is interoperable.

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

=SIRI National profiles inventory 🌐=

National profiles are specified to cover the national needs. To help implementation, DATA4PT is also in process of delivering SIRI EU minimum profile, in collaboration with relevant CEN group. DATA4PT has prepared a table with the currently available SIRI national profiles, including an overview of data categories that are currently covered. For data categories relevant to static data check the [NeTEx Profiles Inventory https://data4pt.org/w/index.php?title=NeTEX#NeTEx_national_and_EU_minimum_profiles_inventory].

==Published profiles==

{| class="wikitable" style="width : 50%"
|-
!Profile Name!!Status/
Availability
!EU Minimum profile based*!!EU Minimum SIRI profile compatible** !!Documentation
|-
|Australia - Victoria (AU)
|Specified but not yet in operation
| style="text-align:center " |✅
| style="text-align:center " |✅
|
|-
|Croatia (HR)
|Using an existing profile
|
| style="text-align:center " |✅
|
|-
|France (FR)||Specified and in use
| style="text-align:center " |✅|| style="text-align:center;" | ||[https://normes.transport.data.gouv.fr/normes/siri/profil-france/ French SIRI profile]
|-
|Italy (IT)
| Specified and in use
| style="text-align:center " |✅
|
|[https://github.com/5Tsrl/siri-italian-profile/tree/main/Linee%20guida Italian SIRI profile]
|-
|Netherlands (NL)||Specified but not yet in operation
| || style="text-align:center;" |✅||
|-
|Nordic (Norway, Sweden, Finland, Denmark)|| Specified and in use
| || style="text-align:center;" |✅||[https://enturas.atlassian.net/wiki/spaces/PUBLIC/pages/637370420/Nordic+SIRI+Profile Nordic SIRI profile]
|-
|UK (GB) ||Specified and in use
| || style="text-align:center;" |✅||
|-
|Switzerland (CH)
|Specified and in use
| style="text-align:center;" |✅
| style="text-align:center;" |✅
|[https://www.oev-info.ch/sites/default/files/2023-04/siri_realisation-guide_pt_ch_v0.9.0.pdf SIRI-ET/PT][https://www.oev-info.ch/sites/default/files/2024-07/realization_guide_siri-sx_oev_schweiz_v1.0.pdf SIRI-SX]
|}
<nowiki>*</nowiki>Profiles of this category have been specified based on EU Minimum profile and are based on XML technology as EU profiles.

<nowiki>**</nowiki> Profiles of this category have been specified either before the definition of EU Minimum profile, but they have been used to define the EU one, and/or after EU profiles and need conversion or adaptation to be interoperable.
==Data categories==

''Data categories are identified based on [https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex%3A32024R0490 MMTIS EU Regulation 490/2024]''
{| class="mw-collapsible mw-collapsed wikitable" style="width : 60%"
|+ style="white-space:nowrap; border:1px solid; padding:3px;" |Data categories table.
|-
!Level of service (LOS)!!Types of the dynamic travel and traffic data
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Dynamic data - Level of service 1 (LOS 1 )'''
|-
| colspan="2" |'''a. Passing times, trip plans and auxiliary information'''
|-
| LOS 1-1||Disruptions, such as network closures and/or diversions, and when possible, the reason
|-
|LOS 1-2||Real-time status information, such as estimated departure and arrival times of services, delays, cancellations, guaranteed connections monitoring
|-
|LOS 1-3||Status of access node features (including dynamic platform information, operational lifts/escalators, closed entrances and exit locations) – for scheduled transport
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Dynamic data - Level of service 2 (LOS 2)'''
|-
|LOS 2-1||'''a. Information service on parking tariffs – for transport on demand and personal transport'''
|-
| colspan="2" |'''b. Availability check and location – for transport on demand and personal transport where relevant'''
|-
|LOS 2-2||Car-sharing availability and location, bike-sharing availability and location, scooter-sharing availability and location, and other vehicle-sharing availability and location
|-
|LOS 2-3||Car parking spaces available (on and off-street)
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Dynamic data - Level of service 3 (LOS 3''')
|-
|LOS 3-1|| Occupancy information of the vehicle – for scheduled transport and transport on demand where relevant
|}

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

{| class="wikitable" style="width : 30%"
|-
!Data Categories
! width="80px" |AU
! width="80px" |HR
! width="80px" |FR
! width="80px" |IT
! width="80px" |NL
! width="300px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |GB
! width="80px" |CH
|-
|[[#Data categories|LOS 1-1]]
| style="text-align:center " |✅|| || style="text-align:center " |✅
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅ dynamic platform is included || style="text-align:center " |✅
| style="text-align:center;" |✅
|-
|[[#Data categories|LOS 1-2]]
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅ dynamic platform is included || style="text-align:center " |✅
| style="text-align:center;" |✅
|-
|[[#Data categories|LOS 1-3]]
| || || style="text-align:center " |✅
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅ dynamic platform is included || style="text-align:center " |
| style="text-align:center;" |✅
via SX
|-
|}

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

{| class="wikitable" style="width : 30%"
|-
!Data Categories
! width="80px" |AU
! width="80px" |HR
! width="80px" | FR
! width="80px" |IT
! width="80px" |NL
! width="300px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |GB
! width="80px" |CH
|-
|[[#Data categories|LOS 2-1]]
|
|
|
|
|
|
|
|
|-
|[[#Data categories|LOS 2-2]]
| || || style="text-align:center " |only for car sharing and bike sharing
| style="text-align:center " |✅|| || style="text-align:center " |✅||
|
|-
|[[#Data categories|LOS 2-3]]
| || || style="text-align:center " |off-street only
| style="text-align:center " |✅|| || style="text-align:center " |✅||
|
|-
|}

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

{| class="wikitable" style="width : 30%"
|-
!Data Categories
! width="80px" |AU
! width="80px" |FR
! width="80px" |IT
! width="80px" |NL
! width="300px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |GB
! width="80px" |CH
|-
|[[#Data categories|LOS 3-1]]
| style="text-align:center " |✅
| style="text-align:center " |✅
| style="text-align:center " |✅
|
|
|
|
|}

⚠️ If you believe that your use cases are resolved in an existing profile, it is highly recommended to '''adopt an existing solution''' and cooperate with the corresponding entity. You will save resources while you will ensure that your profile is interoperable.

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

=Implementations per Country=
Currently, the implementations of NeTEx and SIRI are documented for the following countries:

====== [[Australia]] ======

====== [[Belgium]] ======

====== [[Croatia]] ======

====== [[Denmark]] ======

====== [[France]] ======

====== [[Italy]] ======

====== [[Slovenia]] ======

====== [[Sweden]] ======

====== [[Switzerland]] ======

National Implementations

2024-10-08T13:16:54Z

Anonymous: Added countries

= NeTEx national profiles inventory 🌐 =

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

== Published profiles ==

{| class="wikitable" style="width : 60%"
|-
! width="150px"| Profile Name
!Status/
Availability
! width="100px" | NeTEx EPIP Based* !! width="100px" | NeTEx EPIP Compatible**
! width="300px" | Documentation
|-
| Australia - Victoria (AU)
|Specified but not yet in operation
| style="text-align:center;" |✅
| style="text-align:center;" |✅
|
|-
|Austria (AT)
|Specified but not yet in operation|| style="text-align:center;" |✅|| ||[https://mobilitaetsverbuende.atlassian.net/wiki/spaces/NET/overview Austrian profile]
|-
|Belgium (BE)
|Specified but not yet in operation|| style="text-align:center;" |✅|| ||[https://github.com/Informatievlaanderen/OSLOthema-mobiliteitDienstregelingEnPlanning GitHUb]
[https://purl.eu/doc/applicationprofile/netex-belgium/timetables-ap/ AP-Timetables]

[https://purl.eu/doc/applicationprofile/netex-belgium/stopplaces-ap/ AP-Stops]

[https://purl.eu/doc/applicationprofile/netex-belgium/vehiclescheduling-ap/ AP-Vehicle Scheduling]

[https://purl.eu/ns/mobility/timetables-and-planning/ AP-TimetablesAndPlanning]

[https://github.com/Informatievlaanderen/OSLOthema-mobiliteitDienstregelingEnPlanning/tree/master/resources/DataExamples Data examples]
|-
|Croatia (HR)
|Specified and in use
| style="text-align:center;" | ✅
| style="text-align:center;" |✅
|[https://www.promet-info.hr/en NPT - Croatian NAP]
|-
|Denmark (DK)
|Specified but not yet in operation|| style="text-align:center;" |✅|| ||[https://www.trafikstyrelsen.dk/Media/638013312835439194/Vejledning%20om%20brug%20af%20NeTEx.pdf Denmark profile] - [https://www.trafikstyrelsen.dk/arbejdsomraader/kollektiv-trafik/statistik-og-data/krav-til-udstilling-af-data-til-rejseplanlaegning NAP in Denmark]
|-
|France (FR)
|Specified and in use|| || style="text-align:center;" |✅||[https://normes.transport.data.gouv.fr/normes/netex/ French profile] - [https://normes.transport.data.gouv.fr/normes/netex/elements_communs/ Common profile] - [https://normes.transport.data.gouv.fr/normes/netex/arrets/ Stop profile] - [https://normes.transport.data.gouv.fr/normes/netex/reseaux/ Network profile] - [https://normes.transport.data.gouv.fr/normes/netex/horaires/ Timetable profile] - [https://normes.transport.data.gouv.fr/normes/netex/tarifs/ Fare profile] - [https://normes.transport.data.gouv.fr/normes/netex/parkings/ Parking profile] - [https://normes.transport.data.gouv.fr/normes/netex/accessibilite/ Accessibility profile]
|-
|Italy (IT)
|Specified and in use|| style="text-align:center;" |✅||
|[https://github.com/5Tsrl/netex-italian-profile/tree/main/Linee%20guida Italian profile]
|-
|Netherlands (NL)
|Specified but not yet in operation|| style="text-align:center;" |✅|| ||[https://bison.dova.nu/standaarden/nederlands-netex-profiel Netherlands profile] - [https://bison.dova.nu/sites/default/files/bison_prijzen_producten_en_tarieven_v8.1.3.0_release.pdf Bison Fares]
|-
| Nordic (Norway, Sweden, Finland, Denmark)
|Specified and in use|| || style="text-align:center;" |✅||[https://enturas.atlassian.net/wiki/spaces/PUBLIC/pages/728891481/Nordic+NeTEx+Profile Nordic profile]
|-
|Portugal (PT)
|Specified and in use|| || ||[https://ptprofiles.azurewebsites.net/netex-profile Portuguese profile]
|-
| Slovenija (SI)
|Specified but not yet in operation|| || style="text-align:center " |✅||[https://www.nap.si/_resources/profiles/NeTEx_SI_Profile_v2.pdf Slovenian profile]
|-
|Switzerland (CH)
|Specified and in use
|
|
|[https://www.oev-info.ch/sites/default/files/2024-05/NeTEx_Core-Realisation_Guide_TP_Suisse-v1.00.pdf Swiss profile]
|-
|UK (GB)
|Specified and in use|| || style="text-align:center " |✅||[http://netex.uk/farexchange/ UK profile] - [http://netex.uk/farexchange/doc/uk_profile/DfT-NeTEx-1-Fares-Intro-2019.06.17-v0.09.pdf Introduction] - [http://netex.uk/farexchange/doc/uk_profile/DfT-NeTEx-2-Base_Spec-2019.06.30-v0.14.pdf Stop and Timetables] - [http://netex.uk/farexchange/doc/uk_profile/DfT-NeTEx-3-Fares_Spec-2019.06.17-v0.17.pdf Fares]
|-
|Ireland (IE)
|Specified and in use|| || ||[https://netex.ie/ Irish profile] - [http://netex.uk/netexie/doc/EIRE_NP/NTA-NeTEx-1-Spec-2020.08.12-v0.22.pdf Profile Elements] - [http://netex.uk/netexie/doc/EIRE_NP/NTA-NeTEx-2-Mappings-2020.08.06-v0.22.pdf Profile Data Mappings]
|-
|Czech Republic (CZ)
|Specified but not yet in operation
| style="text-align:center " |✅
|
|
|}
<nowiki>*</nowiki>Profiles of this category have been specified based on EU Minimum profile and are based on XML technology as EU profiles.

<nowiki>**</nowiki> Profiles of this category have been specified either before the definition of EU Minimum profile, but they have been used to define the EU one, and/or after EU profiles and need conversion or adaptation to be interoperable.
==Data categories==

''Data categories are identified based on [https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex%3A32024R0490 MMTIS EU Regulation 490/2024]''
{| class="mw-collapsible mw-collapsed wikitable" style="width:70%"
|+ style="white-space:nowrap; border:1px solid; padding:3px;" | Data categories table.
|-
!Level of service (LOS)!!Static data
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Static data - Level of service 1 (LOS 1 )'''
|-
| colspan="2" |'''a. Location search (origin/destination)'''
|-
|LOS 1-1||Address identifiers (building number, street name, postcode)
|-
| LOS 1-2||Topographic places (city, town, village, suburb, administrative unit)
|-
|LOS 1-3||Points of interest (related to transport information) to which people may wish to travel
|-
|LOS 1-4||'''b. Trip plans: operational calendar, mapping day types to calendar dates'''
|-
| colspan="2" |'''c. Location search (access nodes) – for scheduled transport and transport on demand where relevant'''
|-
|LOS 1-5
| Identified access nodes
|-
|LOS 1-6 ||Geometry/map layout structure of access nodes

|-
| colspan="2" |'''d. Trip plan computation – for scheduled transport and transport on demand where relevant'''
|-
|LOS 1-7||Connection where interchanges may be made
|-
|LOS 1-8
|Default transfer times at interchanges
|-
|LOS 1-9||Network topology and routes/lines (topology)
|-
| LOS 1-10|| Transport operators
|-
|LOS 1-11|| Timetables
|-
|LOS 1-12||Planned interchanges between guaranteed scheduled services
|-
|LOS 1-13||Hours of operation
|-
| LOS 1-14
|Facilities of access nodes (including platform information, help desk/information points, ticket booths, lifts/stairs, entrances and exit locations)
|-
|LOS 1-15||Vehicles, including their accessibility (such as low floor, wheelchair accessible, pram accessible) and accessibility of on-board services (such as toilets)
|-
|LOS 1-16||Accessibility of access nodes, and paths within an interchange (such as existence of lifts, escalators)
|-
|LOS 1-17||Existence of assistance services (such as existence of on-site assistance)
|-
| colspan="2" |'''e. Trip plan computation'''
|-
|LOS 1-18||Road network (including segregated lanes for bus/taxi)
|-
|LOS 1-19||Cycle network (cycle tracks, cycle lanes, bus-and-cycle lanes, on-road shared with vehicles, on-path shared with pedestrians)
|-
|LOS 1-20||Pedestrian network and accessibility facilities
|-
| ||Framework data
|-
|
|
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Static data - Level of service 2 (LOS 2)'''
|-
| colspan="2" |'''a. Location search – for transport on demand and personal transport'''
|-
|LOS 2-1
|Location of parking places (on and off-street), including accessible parking places for persons with disabilities and persons with reduced mobility
|-
|LOS 2-2||Park & Ride stops
|-
|LOS 2-3
| Park & Drive stops
|-
|LOS 2-4||Bike sharing stations
|-
|LOS 2-5||Car-sharing stations
|-
| LOS 2-6
|Secure bike parking (such as locked bike garages)
|-
|LOS 2-7
|Scooter parking zones
|-
| colspan="2" |'''b. Information service'''
|-
|LOS 2-8||Where and how to buy tickets for scheduled transport, including retail channels, fulfilment methods, payment methods
|-
|LOS 2-9||Where and how to pay for parking, including retail channels, fulfilment methods, payment methods
|-
| colspan="2" |'''c. Auxiliary information – for scheduled transport and transport on demand where relevant'''
|-
|LOS 2-10 ||Basic common standard fares
- fare network data (fare zones/stops and fare stages)

- standard fare structures (point to point including daily and weekly fares, zonal fares, flat fares)
|-
|LOS 2-11||Vehicle facilities such as classes of carriage, on-board Wi-Fi.
|-
| ||
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Static data - Level of service 3 (LOS 3''')
|-
| colspan="2" |'''a. Detailed common standard and special fare query – for scheduled transport and transport on demand where relevant'''
|-
|LOS 3-1||Passenger classes (classes of passenger such as adult, child, senior, student, military/veteran, passenger with disability and passenger with reduced mobility, and qualifying conditions, and classes of travel)
|-
|LOS 3-2|| Common fare products (access rights such as zone/point-to-point including daily and weekly tickets/single/return, eligibility of access, basic usage conditions such as validity period/operator/time of travel/interchanging, standard point-to-point fares prices for different point-to-point pairs including daily and weekly fares/zonal fare prices/flat fare prices)
|-
|LOS 3-3||Special fare products (offers with additional special conditions such as promotional fares, group fares, season passes, aggregated products combining different products, and add-on products such as parking and travel, minimum stay)
|-
|LOS 3-4|| Basic commercial conditions such as refunding, replacing, exchanging or transferring
|-
|LOS 3-5||Basic booking conditions such as purchase windows, validity periods, routing restrictions zonal sequence fares, minimum stay
|-
|LOS 3-6||'''b. Information service – for transport on demand: how to book demand-responsive transport services, including retail channels, fulfilment methods, payment methods'''
|-
| colspan="2" |'''c. Trip plans'''
|-
|LOS 3-7||Detailed cycle network attributes (surface quality, side-by-side cycling, shared surface, on/off road, scenic route, “walk only”, turn or access restrictions, e.g. against flow of traffic)
|-
|LOS 3-8 ||Parameters needed to calculate an environmental factor such as greenhouse gas emissions per vehicle type or passenger mile or per distance walked
|-
|LOS 3-9||Parameters needed to calculate fuel consumption of conventional and alternative fuels
|-
|LOS 3-10
|'''d. Trip plan computation: estimated travel times by day type and time-band by transport mode/combination of transport mode'''
|-
| colspan="2" |
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Static data - Level of service 4 (LOS 4 )'''
|-
| LOS 4-1
|'''a. Historic travel and traffic data on delays – for scheduled transport and transport on demand where relevant'''
|-
| colspan="2" |'''b. Observed data on delays and passing time – for scheduled transport'''
|-
|LOS 4-2
|Length of, and when possible the reason for, delays of at least 60 minutes for rail passenger services (in accordance with Article 19 of Regulation (EU) 2021/782)
|-
|LOS 4-3
|Length of, and when possible the reason for, delays in departure of more than 90 minutes for sea and inland waterways passenger services (in accordance with Article 18 of Regulation (EU) No 1177/2010)
|-
|LOS 4-4
| Length of, and when possible the reason for, delays in departure from a terminal of more than 120 minutes for regular bus and coach passenger services with a scheduled distance of 250 km or more (in accordance with Article 19 of Regulation (EU) No 181/2011)
|-
|LOS 4-5
|Length of, and when possible the reason for, flight delays at departure of at least 120 minutes; and flight delays at arrival of at least 180 minutes (in accordance with Articles 5 and 6 of Regulation (EC) No 261/2004)
|-
| colspan="2" |'''c. Observed data on cancellations – for scheduled transport'''
|-
|LOS 4-6
|Cancellations, and when possible the reason, of rail passenger services
|-
|LOS 4-7
|Cancellations, and when possible the reason, of sea and inland waterways passenger services
|-
|LOS 4-8
|Cancellations, and when possible the reason, of regular bus and coach services with a scheduled distance of 250 km or more
|-
|LOS 4-9
|Cancellations, and when possible the reason, of flights
|-
|LOS 4-10
|'''d. Information on parking tariffs'''
|}

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

{| class="wikitable" style="width:70%"
|-
! width="80px" |Data Categories

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

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

{| class="wikitable" style="width:70%"
|-
! width="80px" |Data Categories
! width="80px" style="text-align:center " |EPIP
! width="80px" | AU
! width="80px" |AT
! width="80px" |ΒΕ
! width="80px" |HR
! width="80px" |DK
! width="80px" |FR
! width="80px" |IT
! width="80px" |NL
! width="150px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |PT
! width="80px" |SI
! width="80px" |CH
! width="80px" |GB
|-
|[[#Data categories|LOS 2-1]]
|
|
|
|
| style="text-align:center;" |✅
|
| style="text-align:center;" |for off-street only
| style="text-align:center " |✅
|
|
|
| |
| style="text-align:center;" |partially covered
|
|-
|[[#Data categories|LOS 2-2]]||
| ||
|
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
| style="text-align:center;" |partially covered||
|-
|[[#Data categories|LOS 2-3]]
|
|
|
|
| style="text-align:center " |✅
|
|
| style="text-align:center " |✅
|
|
|
|
| style="text-align:center;" |partially covered
|
|-
|[[#Data categories|LOS 2-4]]||
| ||
|
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " | ✅
| style="text-align:center;" |partially covered||
|-
|[[#Data categories|LOS 2-5]]||
| ||
|
| style="text-align:center " |✅|| style="text-align:center " |✅
| style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
| style="text-align:center;" |partially covered||
|-
|[[#Data categories|LOS 2-6]]||
| ||
|
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |in off-street car parks only|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
|
|
|-
|[[#Data categories|LOS 2-7]]
|
|
|
|
| style="text-align:center " |✅
|
|
| style="text-align:center " |✅
|
|
|
|
|
|
|-
|[[#Data categories|LOS 2-8]]||
| ||
|
| style="text-align:center " |✅|| || style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
| ||
|-
|[[#Data categories|LOS 2-9]]
|
|
|
|
| style="text-align:center " |✅
|
| style="text-align:center " |✅
| style="text-align:center " |✅
|
| style="text-align:center " | ✅
|
| style="text-align:center " |✅
|
|
|-
|[[#Data categories|LOS 2-10]]||
| style="text-align:center;" |✅||
|
| || || style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " | ✅
| || style="text-align:center " |✅
|-
|[[#Data categories|LOS 2-11]]||
| style="text-align:center;" |✅||
| style="text-align:center " |✅
| || || style="text-align:center " | ✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
| || style="text-align:center " |✅
|-
|[[#Data categories|LOS 2-12]]||
| ||
|
| || || style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
| || style="text-align:center " | ✅
|-
|[[#Data categories|LOS 2-13]]||
| ||
| style="text-align:center " |✅
| || style="text-align:center " |✅|| style="text-align:center " | ✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
| || style="text-align:center " |✅
|-
|}

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

{| class="wikitable" style="width:70%"
|-
! width="80px" |Data Categories
! width="80px" style="text-align:center " |EPIP
! width="80px" |AU
! width="80px" |AT
! width="80px" |BE
! width="80px" |HR
! width="80px" |DK
! width="80px" |FR
! width="80px" |IT
! width="80px" |NL
! width="150px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |PT
! width="80px" |SI
! width="80px" |CH
! width="80px" |GB
|-
|[[#Data categories|LOS 3-1]]||
| ||
| style="text-align:center " |✅

| style="text-align:center " | ✅|| || style="text-align:center " |✅ || style="text-align:center " |✅|| || style="text-align:center " |✅|| ||
| || style="text-align:center " | ✅
|-
|[[#Data categories|LOS 3-2]]||
| ||
|
| style="text-align:center " |✅|| || style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| ||
| || style="text-align:center " |✅
|-
|[[#Data categories|LOS 3-3]]||
| ||
|
| || || style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| ||
| || style="text-align:center " |✅
|-
|[[#Data categories|LOS 3-4]]
|
|
|
|
|
|
| style="text-align:center;" |✅
| style="text-align:center " |✅
|
|
|
|
|
|
|-
|[[#Data categories|LOS 3-5]]
|
|
|
|
|
|
| style="text-align:center;" |✅
|
|
|
|
|
|
|
|-
|[[#Data categories|LOS 3-6]]
|
|
|
|
|
|
| style="text-align:center;" |✅
|
|
|
|
|
| style="text-align:center;" |✅
|
|-
|[[#Data categories|LOS 3-7]]||
| ||
|
| || || || || || style="text-align:center " |✅|| ||
| ||
|-
|[[#Data categories|LOS 3-8]]||
| ||
|
| || || style="text-align:center;" |✅|| || || style="text-align:center " |✅|| ||
| ||
|-
|[[#Data categories|LOS 3-9]]||
| ||
|
| || || style="text-align:center;" |✅|| || || style="text-align:center " |✅|| ||
| ||
|-
|[[#Data categories|LOS 3-10]]||
| ||
|
| || || || || || style="text-align:center " |✅|| ||
| style="text-align:center;" |N/A||
|-
|}

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

⚠️ If you believe that your use cases are resolved in an existing profile, it is highly recommended to '''adopt an existing solution''' and cooperate with the corresponding entity. You will save resources while you will ensure that your profile is interoperable.

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

=SIRI National profiles inventory 🌐=

National profiles are specified to cover the national needs. To help implementation, DATA4PT is also in process of delivering SIRI EU minimum profile, in collaboration with relevant CEN group. DATA4PT has prepared a table with the currently available SIRI national profiles, including an overview of data categories that are currently covered. For data categories relevant to static data check the [NeTEx Profiles Inventory https://data4pt.org/w/index.php?title=NeTEX#NeTEx_national_and_EU_minimum_profiles_inventory].

==Published profiles==

{| class="wikitable" style="width : 50%"
|-
!Profile Name!!Status/
Availability
!EU Minimum profile based*!!EU Minimum SIRI profile compatible** !!Documentation
|-
|Australia - Victoria (AU)
|Specified but not yet in operation
| style="text-align:center " |✅
| style="text-align:center " |✅
|
|-
|Croatia (HR)
|Using an existing profile
|
| style="text-align:center " |✅
|
|-
|France (FR)||Specified and in use
| style="text-align:center " |✅|| style="text-align:center;" | ||[https://normes.transport.data.gouv.fr/normes/siri/profil-france/ French SIRI profile]
|-
|Italy (IT)
| Specified and in use
| style="text-align:center " |✅
|
|[https://github.com/5Tsrl/siri-italian-profile/tree/main/Linee%20guida Italian SIRI profile]
|-
|Netherlands (NL)||Specified but not yet in operation
| || style="text-align:center;" |✅||
|-
|Nordic (Norway, Sweden, Finland, Denmark)|| Specified and in use
| || style="text-align:center;" |✅||[https://enturas.atlassian.net/wiki/spaces/PUBLIC/pages/637370420/Nordic+SIRI+Profile Nordic SIRI profile]
|-
|UK (GB) ||Specified and in use
| || style="text-align:center;" |✅||
|-
|Switzerland (CH)
|Specified and in use
| style="text-align:center;" |✅
| style="text-align:center;" |✅
|[https://www.oev-info.ch/sites/default/files/2023-04/siri_realisation-guide_pt_ch_v0.9.0.pdf SIRI-ET/PT][https://www.oev-info.ch/sites/default/files/2024-07/realization_guide_siri-sx_oev_schweiz_v1.0.pdf SIRI-SX]
|}
<nowiki>*</nowiki>Profiles of this category have been specified based on EU Minimum profile and are based on XML technology as EU profiles.

<nowiki>**</nowiki> Profiles of this category have been specified either before the definition of EU Minimum profile, but they have been used to define the EU one, and/or after EU profiles and need conversion or adaptation to be interoperable.
==Data categories==

''Data categories are identified based on [https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex%3A32024R0490 MMTIS EU Regulation 490/2024]''
{| class="mw-collapsible mw-collapsed wikitable" style="width : 60%"
|+ style="white-space:nowrap; border:1px solid; padding:3px;" |Data categories table.
|-
!Level of service (LOS)!!Types of the dynamic travel and traffic data
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Dynamic data - Level of service 1 (LOS 1 )'''
|-
| colspan="2" |'''a. Passing times, trip plans and auxiliary information'''
|-
| LOS 1-1||Disruptions, such as network closures and/or diversions, and when possible, the reason
|-
|LOS 1-2||Real-time status information, such as estimated departure and arrival times of services, delays, cancellations, guaranteed connections monitoring
|-
|LOS 1-3||Status of access node features (including dynamic platform information, operational lifts/escalators, closed entrances and exit locations) – for scheduled transport
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Dynamic data - Level of service 2 (LOS 2)'''
|-
|LOS 2-1||'''a. Information service on parking tariffs – for transport on demand and personal transport'''
|-
| colspan="2" |'''b. Availability check and location – for transport on demand and personal transport where relevant'''
|-
|LOS 2-2||Car-sharing availability and location, bike-sharing availability and location, scooter-sharing availability and location, and other vehicle-sharing availability and location
|-
|LOS 2-3||Car parking spaces available (on and off-street)
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Dynamic data - Level of service 3 (LOS 3''')
|-
|LOS 3-1|| Occupancy information of the vehicle – for scheduled transport and transport on demand where relevant
|}

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

{| class="wikitable" style="width : 30%"
|-
!Data Categories
! width="80px" |AU
! width="80px" |HR
! width="80px" |FR
! width="80px" |IT
! width="80px" |NL
! width="300px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |GB
! width="80px" |CH
|-
|[[#Data categories|LOS 1-1]]
| style="text-align:center " |✅|| || style="text-align:center " |✅
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅ dynamic platform is included || style="text-align:center " |✅
| style="text-align:center;" |✅
|-
|[[#Data categories|LOS 1-2]]
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅ dynamic platform is included || style="text-align:center " |✅
| style="text-align:center;" |✅
|-
|[[#Data categories|LOS 1-3]]
| || || style="text-align:center " |✅
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅ dynamic platform is included || style="text-align:center " |
| style="text-align:center;" |✅
via SX
|-
|}

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

{| class="wikitable" style="width : 30%"
|-
!Data Categories
! width="80px" |AU
! width="80px" |HR
! width="80px" | FR
! width="80px" |IT
! width="80px" |NL
! width="300px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |GB
! width="80px" |CH
|-
|[[#Data categories|LOS 2-1]]
|
|
|
|
|
|
|
|
|-
|[[#Data categories|LOS 2-2]]
| || || style="text-align:center " |only for car sharing and bike sharing
| style="text-align:center " |✅|| || style="text-align:center " |✅||
|
|-
|[[#Data categories|LOS 2-3]]
| || || style="text-align:center " |off-street only
| style="text-align:center " |✅|| || style="text-align:center " |✅||
|
|-
|}

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

{| class="wikitable" style="width : 30%"
|-
!Data Categories
! width="80px" |AU
! width="80px" |FR
! width="80px" |IT
! width="80px" |NL
! width="300px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |GB
! width="80px" |CH
|-
|[[#Data categories|LOS 3-1]]
| style="text-align:center " |✅
| style="text-align:center " |✅
| style="text-align:center " |✅
|
|
|
|
|}

⚠️ If you believe that your use cases are resolved in an existing profile, it is highly recommended to '''adopt an existing solution''' and cooperate with the corresponding entity. You will save resources while you will ensure that your profile is interoperable.

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

=Implementations per Country=
Currently, the implementations of NeTEx and SIRI are documented for the following countries:

====== [[Australia]] ======

====== [[Belgium]] ======

====== [[Croatia]] ======

====== [[Denmark]] ======

====== [[France]] ======

====== [[Italy]] ======

====== [[Portugal]] ======

====== [[Slovenia]] ======

====== [[Sweden]] ======

====== [[Switzerland]] ======

National Implementations

2024-10-02T10:15:11Z

Anonymous:

= NeTEx national profiles inventory 🌐 =

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

== Published profiles ==

{| class="wikitable" style="width : 60%"
|-
! width="150px"| Profile Name
!Status/
Availability
! width="100px" | NeTEx EPIP Based* !! width="100px" | NeTEx EPIP Compatible**
! width="300px" | Documentation
|-
| Australia - Victoria (AU)
|Specified but not yet in operation
| style="text-align:center;" |✅
| style="text-align:center;" |✅
|
|-
|Austria (AT)
|Specified but not yet in operation|| style="text-align:center;" |✅|| ||[https://mobilitaetsverbuende.atlassian.net/wiki/spaces/NET/overview Austrian profile]
|-
|Belgium (BE)
|Specified but not yet in operation|| style="text-align:center;" |✅|| ||[https://github.com/Informatievlaanderen/OSLOthema-mobiliteitDienstregelingEnPlanning GitHUb]
[https://purl.eu/doc/applicationprofile/netex-belgium/timetables-ap/ AP-Timetables]

[https://purl.eu/doc/applicationprofile/netex-belgium/stopplaces-ap/ AP-Stops]

[https://purl.eu/doc/applicationprofile/netex-belgium/vehiclescheduling-ap/ AP-Vehicle Scheduling]

[https://purl.eu/ns/mobility/timetables-and-planning/ AP-TimetablesAndPlanning]

[https://github.com/Informatievlaanderen/OSLOthema-mobiliteitDienstregelingEnPlanning/tree/master/resources/DataExamples Data examples]
|-
|Croatia (HR)
|Specified and in use
| style="text-align:center;" | ✅
| style="text-align:center;" |✅
|[https://www.promet-info.hr/en NPT - Croatian NAP]
|-
|Denmark (DK)
|Specified but not yet in operation|| style="text-align:center;" |✅|| ||[https://www.trafikstyrelsen.dk/Media/638013312835439194/Vejledning%20om%20brug%20af%20NeTEx.pdf Denmark profile] - [https://www.trafikstyrelsen.dk/arbejdsomraader/kollektiv-trafik/statistik-og-data/krav-til-udstilling-af-data-til-rejseplanlaegning NAP in Denmark]
|-
|France (FR)
|Specified and in use|| || style="text-align:center;" |✅||[https://normes.transport.data.gouv.fr/normes/netex/ French profile] - [https://normes.transport.data.gouv.fr/normes/netex/elements_communs/ Common profile] - [https://normes.transport.data.gouv.fr/normes/netex/arrets/ Stop profile] - [https://normes.transport.data.gouv.fr/normes/netex/reseaux/ Network profile] - [https://normes.transport.data.gouv.fr/normes/netex/horaires/ Timetable profile] - [https://normes.transport.data.gouv.fr/normes/netex/tarifs/ Fare profile] - [https://normes.transport.data.gouv.fr/normes/netex/parkings/ Parking profile] - [https://normes.transport.data.gouv.fr/normes/netex/accessibilite/ Accessibility profile]
|-
|Italy (IT)
|Specified and in use|| style="text-align:center;" |✅||
|[https://github.com/5Tsrl/netex-italian-profile/tree/main/Linee%20guida Italian profile]
|-
|Netherlands (NL)
|Specified but not yet in operation|| style="text-align:center;" |✅|| ||[https://bison.dova.nu/standaarden/nederlands-netex-profiel Netherlands profile] - [https://bison.dova.nu/sites/default/files/bison_prijzen_producten_en_tarieven_v8.1.3.0_release.pdf Bison Fares]
|-
| Nordic (Norway, Sweden, Finland, Denmark)
|Specified and in use|| || style="text-align:center;" |✅||[https://enturas.atlassian.net/wiki/spaces/PUBLIC/pages/728891481/Nordic+NeTEx+Profile Nordic profile]
|-
|Portugal (PT)
|Specified and in use|| || ||[https://ptprofiles.azurewebsites.net/netex-profile Portuguese profile]
|-
| Slovenija (SI)
|Specified but not yet in operation|| || style="text-align:center " |✅||[https://www.nap.si/_resources/profiles/NeTEx_SI_Profile_v2.pdf Slovenian profile]
|-
|Switzerland (CH)
|Specified and in use
|
|
|[https://www.oev-info.ch/sites/default/files/2024-05/NeTEx_Core-Realisation_Guide_TP_Suisse-v1.00.pdf Swiss profile]
|-
|UK (GB)
|Specified and in use|| || style="text-align:center " |✅||[http://netex.uk/farexchange/ UK profile] - [http://netex.uk/farexchange/doc/uk_profile/DfT-NeTEx-1-Fares-Intro-2019.06.17-v0.09.pdf Introduction] - [http://netex.uk/farexchange/doc/uk_profile/DfT-NeTEx-2-Base_Spec-2019.06.30-v0.14.pdf Stop and Timetables] - [http://netex.uk/farexchange/doc/uk_profile/DfT-NeTEx-3-Fares_Spec-2019.06.17-v0.17.pdf Fares]
|-
|Ireland (IE)
|Specified and in use|| || ||[https://netex.ie/ Irish profile] - [http://netex.uk/netexie/doc/EIRE_NP/NTA-NeTEx-1-Spec-2020.08.12-v0.22.pdf Profile Elements] - [http://netex.uk/netexie/doc/EIRE_NP/NTA-NeTEx-2-Mappings-2020.08.06-v0.22.pdf Profile Data Mappings]
|-
|Czech Republic (CZ)
|Specified but not yet in operation
| style="text-align:center " |✅
|
|
|}
<nowiki>*</nowiki>Profiles of this category have been specified based on EU Minimum profile and are based on XML technology as EU profiles.

<nowiki>**</nowiki> Profiles of this category have been specified either before the definition of EU Minimum profile, but they have been used to define the EU one, and/or after EU profiles and need conversion or adaptation to be interoperable.
==Data categories==

''Data categories are identified based on [https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex%3A32024R0490 MMTIS EU Regulation 490/2024]''
{| class="mw-collapsible mw-collapsed wikitable" style="width:70%"
|+ style="white-space:nowrap; border:1px solid; padding:3px;" | Data categories table.
|-
!Level of service (LOS)!!Static data
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Static data - Level of service 1 (LOS 1 )'''
|-
| colspan="2" |'''a. Location search (origin/destination)'''
|-
|LOS 1-1||Address identifiers (building number, street name, postcode)
|-
| LOS 1-2||Topographic places (city, town, village, suburb, administrative unit)
|-
|LOS 1-3||Points of interest (related to transport information) to which people may wish to travel
|-
|LOS 1-4||'''b. Trip plans: operational calendar, mapping day types to calendar dates'''
|-
| colspan="2" |'''c. Location search (access nodes) – for scheduled transport and transport on demand where relevant'''
|-
|LOS 1-5
| Identified access nodes
|-
|LOS 1-6 ||Geometry/map layout structure of access nodes

|-
| colspan="2" |'''d. Trip plan computation – for scheduled transport and transport on demand where relevant'''
|-
|LOS 1-7||Connection where interchanges may be made
|-
|LOS 1-8
|Default transfer times at interchanges
|-
|LOS 1-9||Network topology and routes/lines (topology)
|-
| LOS 1-10|| Transport operators
|-
|LOS 1-11|| Timetables
|-
|LOS 1-12||Planned interchanges between guaranteed scheduled services
|-
|LOS 1-13||Hours of operation
|-
| LOS 1-14
|Facilities of access nodes (including platform information, help desk/information points, ticket booths, lifts/stairs, entrances and exit locations)
|-
|LOS 1-15||Vehicles, including their accessibility (such as low floor, wheelchair accessible, pram accessible) and accessibility of on-board services (such as toilets)
|-
|LOS 1-16||Accessibility of access nodes, and paths within an interchange (such as existence of lifts, escalators)
|-
|LOS 1-17||Existence of assistance services (such as existence of on-site assistance)
|-
| colspan="2" |'''e. Trip plan computation'''
|-
|LOS 1-18||Road network (including segregated lanes for bus/taxi)
|-
|LOS 1-19||Cycle network (cycle tracks, cycle lanes, bus-and-cycle lanes, on-road shared with vehicles, on-path shared with pedestrians)
|-
|LOS 1-20||Pedestrian network and accessibility facilities
|-
| ||Framework data
|-
|
|
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Static data - Level of service 2 (LOS 2)'''
|-
| colspan="2" |'''a. Location search – for transport on demand and personal transport'''
|-
|LOS 2-1
|Location of parking places (on and off-street), including accessible parking places for persons with disabilities and persons with reduced mobility
|-
|LOS 2-2||Park & Ride stops
|-
|LOS 2-3
| Park & Drive stops
|-
|LOS 2-4||Bike sharing stations
|-
|LOS 2-5||Car-sharing stations
|-
| LOS 2-6
|Secure bike parking (such as locked bike garages)
|-
|LOS 2-7
|Scooter parking zones
|-
| colspan="2" |'''b. Information service'''
|-
|LOS 2-8||Where and how to buy tickets for scheduled transport, including retail channels, fulfilment methods, payment methods
|-
|LOS 2-9||Where and how to pay for parking, including retail channels, fulfilment methods, payment methods
|-
| colspan="2" |'''c. Auxiliary information – for scheduled transport and transport on demand where relevant'''
|-
|LOS 2-10 ||Basic common standard fares
- fare network data (fare zones/stops and fare stages)

- standard fare structures (point to point including daily and weekly fares, zonal fares, flat fares)
|-
|LOS 2-11||Vehicle facilities such as classes of carriage, on-board Wi-Fi.
|-
| ||
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Static data - Level of service 3 (LOS 3''')
|-
| colspan="2" |'''a. Detailed common standard and special fare query – for scheduled transport and transport on demand where relevant'''
|-
|LOS 3-1||Passenger classes (classes of passenger such as adult, child, senior, student, military/veteran, passenger with disability and passenger with reduced mobility, and qualifying conditions, and classes of travel)
|-
|LOS 3-2|| Common fare products (access rights such as zone/point-to-point including daily and weekly tickets/single/return, eligibility of access, basic usage conditions such as validity period/operator/time of travel/interchanging, standard point-to-point fares prices for different point-to-point pairs including daily and weekly fares/zonal fare prices/flat fare prices)
|-
|LOS 3-3||Special fare products (offers with additional special conditions such as promotional fares, group fares, season passes, aggregated products combining different products, and add-on products such as parking and travel, minimum stay)
|-
|LOS 3-4|| Basic commercial conditions such as refunding, replacing, exchanging or transferring
|-
|LOS 3-5||Basic booking conditions such as purchase windows, validity periods, routing restrictions zonal sequence fares, minimum stay
|-
|LOS 3-6||'''b. Information service – for transport on demand: how to book demand-responsive transport services, including retail channels, fulfilment methods, payment methods'''
|-
| colspan="2" |'''c. Trip plans'''
|-
|LOS 3-7||Detailed cycle network attributes (surface quality, side-by-side cycling, shared surface, on/off road, scenic route, “walk only”, turn or access restrictions, e.g. against flow of traffic)
|-
|LOS 3-8 ||Parameters needed to calculate an environmental factor such as greenhouse gas emissions per vehicle type or passenger mile or per distance walked
|-
|LOS 3-9||Parameters needed to calculate fuel consumption of conventional and alternative fuels
|-
|LOS 3-10
|'''d. Trip plan computation: estimated travel times by day type and time-band by transport mode/combination of transport mode'''
|-
| colspan="2" |
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Static data - Level of service 4 (LOS 4 )'''
|-
| LOS 4-1
|'''a. Historic travel and traffic data on delays – for scheduled transport and transport on demand where relevant'''
|-
| colspan="2" |'''b. Observed data on delays and passing time – for scheduled transport'''
|-
|LOS 4-2
|Length of, and when possible the reason for, delays of at least 60 minutes for rail passenger services (in accordance with Article 19 of Regulation (EU) 2021/782)
|-
|LOS 4-3
|Length of, and when possible the reason for, delays in departure of more than 90 minutes for sea and inland waterways passenger services (in accordance with Article 18 of Regulation (EU) No 1177/2010)
|-
|LOS 4-4
| Length of, and when possible the reason for, delays in departure from a terminal of more than 120 minutes for regular bus and coach passenger services with a scheduled distance of 250 km or more (in accordance with Article 19 of Regulation (EU) No 181/2011)
|-
|LOS 4-5
|Length of, and when possible the reason for, flight delays at departure of at least 120 minutes; and flight delays at arrival of at least 180 minutes (in accordance with Articles 5 and 6 of Regulation (EC) No 261/2004)
|-
| colspan="2" |'''c. Observed data on cancellations – for scheduled transport'''
|-
|LOS 4-6
|Cancellations, and when possible the reason, of rail passenger services
|-
|LOS 4-7
|Cancellations, and when possible the reason, of sea and inland waterways passenger services
|-
|LOS 4-8
|Cancellations, and when possible the reason, of regular bus and coach services with a scheduled distance of 250 km or more
|-
|LOS 4-9
|Cancellations, and when possible the reason, of flights
|-
|LOS 4-10
|'''d. Information on parking tariffs'''
|}

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

{| class="wikitable" style="width:70%"
|-
! width="80px" |Data Categories

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

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

{| class="wikitable" style="width:70%"
|-
! width="80px" |Data Categories
! width="80px" style="text-align:center " |EPIP
! width="80px" | AU
! width="80px" |AT
! width="80px" |ΒΕ
! width="80px" |HR
! width="80px" |DK
! width="80px" |FR
! width="80px" |IT
! width="80px" |NL
! width="150px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |PT
! width="80px" |SI
! width="80px" |CH
! width="80px" |GB
|-
|[[#Data categories|LOS 2-1]]
|
|
|
|
| style="text-align:center;" |✅
|
| style="text-align:center;" |for off-street only
| style="text-align:center " |✅
|
|
|
| |
| style="text-align:center;" |partially covered
|
|-
|[[#Data categories|LOS 2-2]]||
| ||
|
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
| style="text-align:center;" |partially covered||
|-
|[[#Data categories|LOS 2-3]]
|
|
|
|
| style="text-align:center " |✅
|
|
| style="text-align:center " |✅
|
|
|
|
| style="text-align:center;" |partially covered
|
|-
|[[#Data categories|LOS 2-4]]||
| ||
|
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " | ✅
| style="text-align:center;" |partially covered||
|-
|[[#Data categories|LOS 2-5]]||
| ||
|
| style="text-align:center " |✅|| style="text-align:center " |✅
| style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
| style="text-align:center;" |partially covered||
|-
|[[#Data categories|LOS 2-6]]||
| ||
|
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |in off-street car parks only|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
|
|
|-
|[[#Data categories|LOS 2-7]]
|
|
|
|
| style="text-align:center " |✅
|
|
| style="text-align:center " |✅
|
|
|
|
|
|
|-
|[[#Data categories|LOS 2-8]]||
| ||
|
| style="text-align:center " |✅|| || style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
| ||
|-
|[[#Data categories|LOS 2-9]]
|
|
|
|
| style="text-align:center " |✅
|
| style="text-align:center " |✅
| style="text-align:center " |✅
|
| style="text-align:center " | ✅
|
| style="text-align:center " |✅
|
|
|-
|[[#Data categories|LOS 2-10]]||
| style="text-align:center;" |✅||
|
| || || style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " | ✅
| || style="text-align:center " |✅
|-
|[[#Data categories|LOS 2-11]]||
| style="text-align:center;" |✅||
| style="text-align:center " |✅
| || || style="text-align:center " | ✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
| || style="text-align:center " |✅
|-
|[[#Data categories|LOS 2-12]]||
| ||
|
| || || style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
| || style="text-align:center " | ✅
|-
|[[#Data categories|LOS 2-13]]||
| ||
| style="text-align:center " |✅
| || style="text-align:center " |✅|| style="text-align:center " | ✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
| || style="text-align:center " |✅
|-
|}

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

{| class="wikitable" style="width:70%"
|-
! width="80px" |Data Categories
! width="80px" style="text-align:center " |EPIP
! width="80px" |AU
! width="80px" |AT
! width="80px" |BE
! width="80px" |HR
! width="80px" |DK
! width="80px" |FR
! width="80px" |IT
! width="80px" |NL
! width="150px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |PT
! width="80px" |SI
! width="80px" |CH
! width="80px" |GB
|-
|[[#Data categories|LOS 3-1]]||
| ||
| style="text-align:center " |✅

| style="text-align:center " | ✅|| || style="text-align:center " |✅ || style="text-align:center " |✅|| || style="text-align:center " |✅|| ||
| || style="text-align:center " | ✅
|-
|[[#Data categories|LOS 3-2]]||
| ||
|
| style="text-align:center " |✅|| || style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| ||
| || style="text-align:center " |✅
|-
|[[#Data categories|LOS 3-3]]||
| ||
|
| || || style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| ||
| || style="text-align:center " |✅
|-
|[[#Data categories|LOS 3-4]]
|
|
|
|
|
|
| style="text-align:center;" |✅
| style="text-align:center " |✅
|
|
|
|
|
|
|-
|[[#Data categories|LOS 3-5]]
|
|
|
|
|
|
| style="text-align:center;" |✅
|
|
|
|
|
|
|
|-
|[[#Data categories|LOS 3-6]]
|
|
|
|
|
|
| style="text-align:center;" |✅
|
|
|
|
|
| style="text-align:center;" |✅
|
|-
|[[#Data categories|LOS 3-7]]||
| ||
|
| || || || || || style="text-align:center " |✅|| ||
| ||
|-
|[[#Data categories|LOS 3-8]]||
| ||
|
| || || style="text-align:center;" |✅|| || || style="text-align:center " |✅|| ||
| ||
|-
|[[#Data categories|LOS 3-9]]||
| ||
|
| || || style="text-align:center;" |✅|| || || style="text-align:center " |✅|| ||
| ||
|-
|[[#Data categories|LOS 3-10]]||
| ||
|
| || || || || || style="text-align:center " |✅|| ||
| style="text-align:center;" |N/A||
|-
|}

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

⚠️ If you believe that your use cases are resolved in an existing profile, it is highly recommended to '''adopt an existing solution''' and cooperate with the corresponding entity. You will save resources while you will ensure that your profile is interoperable.

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

=SIRI National profiles inventory 🌐=

National profiles are specified to cover the national needs. To help implementation, DATA4PT is also in process of delivering SIRI EU minimum profile, in collaboration with relevant CEN group. DATA4PT has prepared a table with the currently available SIRI national profiles, including an overview of data categories that are currently covered. For data categories relevant to static data check the [NeTEx Profiles Inventory https://data4pt.org/w/index.php?title=NeTEX#NeTEx_national_and_EU_minimum_profiles_inventory].

==Published profiles==

{| class="wikitable" style="width : 50%"
|-
!Profile Name!!Status/
Availability
!EU Minimum profile based*!!EU Minimum SIRI profile compatible** !!Documentation
|-
|Australia - Victoria (AU)
|Specified but not yet in operation
| style="text-align:center " |✅
| style="text-align:center " |✅
|
|-
|Croatia (HR)
|Using an existing profile
|
| style="text-align:center " |✅
|
|-
|France (FR)||Specified and in use
| style="text-align:center " |✅|| style="text-align:center;" | ||[https://normes.transport.data.gouv.fr/normes/siri/profil-france/ French SIRI profile]
|-
|Italy (IT)
| Specified and in use
| style="text-align:center " |✅
|
|[https://github.com/5Tsrl/siri-italian-profile/tree/main/Linee%20guida Italian SIRI profile]
|-
|Netherlands (NL)||Specified but not yet in operation
| || style="text-align:center;" |✅||
|-
|Nordic (Norway, Sweden, Finland, Denmark)|| Specified and in use
| || style="text-align:center;" |✅||[https://enturas.atlassian.net/wiki/spaces/PUBLIC/pages/637370420/Nordic+SIRI+Profile Nordic SIRI profile]
|-
|UK (GB) ||Specified and in use
| || style="text-align:center;" |✅||
|-
|Switzerland (CH)
|Specified and in use
| style="text-align:center;" |✅
| style="text-align:center;" |✅
|[https://www.oev-info.ch/sites/default/files/2023-04/siri_realisation-guide_pt_ch_v0.9.0.pdf SIRI-ET/PT][https://www.oev-info.ch/sites/default/files/2024-07/realization_guide_siri-sx_oev_schweiz_v1.0.pdf SIRI-SX]
|}
<nowiki>*</nowiki>Profiles of this category have been specified based on EU Minimum profile and are based on XML technology as EU profiles.

<nowiki>**</nowiki> Profiles of this category have been specified either before the definition of EU Minimum profile, but they have been used to define the EU one, and/or after EU profiles and need conversion or adaptation to be interoperable.
==Data categories==

''Data categories are identified based on [https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex%3A32024R0490 MMTIS EU Regulation 490/2024]''
{| class="mw-collapsible mw-collapsed wikitable" style="width : 60%"
|+ style="white-space:nowrap; border:1px solid; padding:3px;" |Data categories table.
|-
!Level of service (LOS)!!Types of the dynamic travel and traffic data
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Dynamic data - Level of service 1 (LOS 1 )'''
|-
| colspan="2" |'''a. Passing times, trip plans and auxiliary information'''
|-
| LOS 1-1||Disruptions, such as network closures and/or diversions, and when possible, the reason
|-
|LOS 1-2||Real-time status information, such as estimated departure and arrival times of services, delays, cancellations, guaranteed connections monitoring
|-
|LOS 1-3||Status of access node features (including dynamic platform information, operational lifts/escalators, closed entrances and exit locations) – for scheduled transport
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Dynamic data - Level of service 2 (LOS 2)'''
|-
|LOS 2-1||'''a. Information service on parking tariffs – for transport on demand and personal transport'''
|-
| colspan="2" |'''b. Availability check and location – for transport on demand and personal transport where relevant'''
|-
|LOS 2-2||Car-sharing availability and location, bike-sharing availability and location, scooter-sharing availability and location, and other vehicle-sharing availability and location
|-
|LOS 2-3||Car parking spaces available (on and off-street)
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Dynamic data - Level of service 3 (LOS 3''')
|-
|LOS 3-1|| Occupancy information of the vehicle – for scheduled transport and transport on demand where relevant
|}

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

{| class="wikitable" style="width : 30%"
|-
!Data Categories
! width="80px" |AU
! width="80px" |HR
! width="80px" |FR
! width="80px" |IT
! width="80px" |NL
! width="300px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |GB
! width="80px" |CH
|-
|[[#Data categories|LOS 1-1]]
| style="text-align:center " |✅|| || style="text-align:center " |✅
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅ dynamic platform is included || style="text-align:center " |✅
| style="text-align:center;" |✅
|-
|[[#Data categories|LOS 1-2]]
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅ dynamic platform is included || style="text-align:center " |✅
| style="text-align:center;" |✅
|-
|[[#Data categories|LOS 1-3]]
| || || style="text-align:center " |✅
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅ dynamic platform is included || style="text-align:center " |
| style="text-align:center;" |✅
via SX
|-
|}

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

{| class="wikitable" style="width : 30%"
|-
!Data Categories
! width="80px" |AU
! width="80px" |HR
! width="80px" | FR
! width="80px" |IT
! width="80px" |NL
! width="300px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |GB
! width="80px" |CH
|-
|[[#Data categories|LOS 2-1]]
|
|
|
|
|
|
|
|
|-
|[[#Data categories|LOS 2-2]]
| || || style="text-align:center " |only for car sharing and bike sharing
| style="text-align:center " |✅|| || style="text-align:center " |✅||
|
|-
|[[#Data categories|LOS 2-3]]
| || || style="text-align:center " |off-street only
| style="text-align:center " |✅|| || style="text-align:center " |✅||
|
|-
|}

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

{| class="wikitable" style="width : 30%"
|-
!Data Categories
! width="80px" |AU
! width="80px" |FR
! width="80px" |IT
! width="80px" |NL
! width="300px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |GB
! width="80px" |CH
|-
|[[#Data categories|LOS 3-1]]
| style="text-align:center " |✅
| style="text-align:center " |✅
| style="text-align:center " |✅
|
|
|
|
|}

⚠️ If you believe that your use cases are resolved in an existing profile, it is highly recommended to '''adopt an existing solution''' and cooperate with the corresponding entity. You will save resources while you will ensure that your profile is interoperable.

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

=Implementations per Country=
Currently, the implementations of NeTEx and SIRI are documented for the following countries:

* [[Australia]]
* [[Croatia]]
* [[Italy]]

National Implementations

2024-10-02T09:14:38Z

Anonymous:

= NeTEx national profiles inventory 🌐 =

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

== Published profiles ==

{| class="wikitable" style="width : 60%"
|-
! width="150px"| Profile Name
!Status/
Availability
! width="100px" | NeTEx EPIP Based* !! width="100px" | NeTEx EPIP Compatible**
! width="300px" | Documentation
|-
| Australia - Victoria (AU)
|Specified but not yet in operation
| style="text-align:center;" |✅
| style="text-align:center;" |✅
|
|-
|Austria (AT)
|Specified but not yet in operation|| style="text-align:center;" |✅|| ||[https://mobilitaetsverbuende.atlassian.net/wiki/spaces/NET/overview Austrian profile]
|-
|Belgium (BE)
|Specified but not yet in operation|| style="text-align:center;" |✅|| ||[https://github.com/Informatievlaanderen/OSLOthema-mobiliteitDienstregelingEnPlanning GitHUb]
[https://purl.eu/doc/applicationprofile/netex-belgium/timetables-ap/ AP-Timetables]

[https://purl.eu/doc/applicationprofile/netex-belgium/stopplaces-ap/ AP-Stops]

[https://purl.eu/doc/applicationprofile/netex-belgium/vehiclescheduling-ap/ AP-Vehicle Scheduling]

[https://purl.eu/ns/mobility/timetables-and-planning/ AP-TimetablesAndPlanning]

[https://github.com/Informatievlaanderen/OSLOthema-mobiliteitDienstregelingEnPlanning/tree/master/resources/DataExamples Data examples]
|-
|Croatia (HR)
|Specified and in use
| style="text-align:center;" | ✅
| style="text-align:center;" |✅
|[https://www.promet-info.hr/en NPT - Croatian NAP]
|-
|Denmark (DK)
|Specified but not yet in operation|| style="text-align:center;" |✅|| ||[https://www.trafikstyrelsen.dk/Media/638013312835439194/Vejledning%20om%20brug%20af%20NeTEx.pdf Denmark profile] - [https://www.trafikstyrelsen.dk/arbejdsomraader/kollektiv-trafik/statistik-og-data/krav-til-udstilling-af-data-til-rejseplanlaegning NAP in Denmark]
|-
|France (FR)
|Specified and in use|| || style="text-align:center;" |✅||[https://normes.transport.data.gouv.fr/normes/netex/ French profile] - [https://normes.transport.data.gouv.fr/normes/netex/elements_communs/ Common profile] - [https://normes.transport.data.gouv.fr/normes/netex/arrets/ Stop profile] - [https://normes.transport.data.gouv.fr/normes/netex/reseaux/ Network profile] - [https://normes.transport.data.gouv.fr/normes/netex/horaires/ Timetable profile] - [https://normes.transport.data.gouv.fr/normes/netex/tarifs/ Fare profile] - [https://normes.transport.data.gouv.fr/normes/netex/parkings/ Parking profile] - [https://normes.transport.data.gouv.fr/normes/netex/accessibilite/ Accessibility profile]
|-
|Italy (IT)
|Specified and in use|| style="text-align:center;" |✅||
|[https://github.com/5Tsrl/netex-italian-profile/tree/main/Linee%20guida Italian profile]
|-
|Netherlands (NL)
|Specified but not yet in operation|| style="text-align:center;" |✅|| ||[https://bison.dova.nu/standaarden/nederlands-netex-profiel Netherlands profile] - [https://bison.dova.nu/sites/default/files/bison_prijzen_producten_en_tarieven_v8.1.3.0_release.pdf Bison Fares]
|-
| Nordic (Norway, Sweden, Finland, Denmark)
|Specified and in use|| || style="text-align:center;" |✅||[https://enturas.atlassian.net/wiki/spaces/PUBLIC/pages/728891481/Nordic+NeTEx+Profile Nordic profile]
|-
|Portugal (PT)
|Specified and in use|| || ||[https://ptprofiles.azurewebsites.net/netex-profile Portuguese profile]
|-
| Slovenija (SI)
|Specified but not yet in operation|| || style="text-align:center " |✅||[https://www.nap.si/_resources/profiles/NeTEx_SI_Profile_v2.pdf Slovenian profile]
|-
|Switzerland (CH)
|Specified and in use
|
|
|[https://www.oev-info.ch/sites/default/files/2024-05/NeTEx_Core-Realisation_Guide_TP_Suisse-v1.00.pdf Swiss profile]
|-
|UK (GB)
|Specified and in use|| || style="text-align:center " |✅||[http://netex.uk/farexchange/ UK profile] - [http://netex.uk/farexchange/doc/uk_profile/DfT-NeTEx-1-Fares-Intro-2019.06.17-v0.09.pdf Introduction] - [http://netex.uk/farexchange/doc/uk_profile/DfT-NeTEx-2-Base_Spec-2019.06.30-v0.14.pdf Stop and Timetables] - [http://netex.uk/farexchange/doc/uk_profile/DfT-NeTEx-3-Fares_Spec-2019.06.17-v0.17.pdf Fares]
|-
|Ireland (IE)
|Specified and in use|| || ||[https://netex.ie/ Irish profile] - [http://netex.uk/netexie/doc/EIRE_NP/NTA-NeTEx-1-Spec-2020.08.12-v0.22.pdf Profile Elements] - [http://netex.uk/netexie/doc/EIRE_NP/NTA-NeTEx-2-Mappings-2020.08.06-v0.22.pdf Profile Data Mappings]
|-
|Czech Republic (CZ)
|Specified but not yet in operation
| style="text-align:center " |✅
|
|
|}
<nowiki>*</nowiki>Profiles of this category have been specified based on EU Minimum profile and are based on XML technology as EU profiles.

<nowiki>**</nowiki> Profiles of this category have been specified either before the definition of EU Minimum profile, but they have been used to define the EU one, and/or after EU profiles and need conversion or adaptation to be interoperable.
==Data categories==

''Data categories are identified based on [https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex%3A32024R0490 MMTIS EU Regulation 490/2024]''
{| class="mw-collapsible mw-collapsed wikitable" style="width:70%"
|+ style="white-space:nowrap; border:1px solid; padding:3px;" | Data categories table.
|-
!Level of service (LOS)!!Static data
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Static data - Level of service 1 (LOS 1 )'''
|-
| colspan="2" |'''a. Location search (origin/destination)'''
|-
|LOS 1-1||Address identifiers (building number, street name, postcode)
|-
| LOS 1-2||Topographic places (city, town, village, suburb, administrative unit)
|-
|LOS 1-3||Points of interest (related to transport information) to which people may wish to travel
|-
|LOS 1-4||'''b. Trip plans: operational calendar, mapping day types to calendar dates'''
|-
| colspan="2" |'''c. Location search (access nodes) – for scheduled transport and transport on demand where relevant'''
|-
|LOS 1-5
| Identified access nodes
|-
|LOS 1-6 ||Geometry/map layout structure of access nodes

|-
| colspan="2" |'''d. Trip plan computation – for scheduled transport and transport on demand where relevant'''
|-
|LOS 1-7||Connection where interchanges may be made
|-
|LOS 1-8
|Default transfer times at interchanges
|-
|LOS 1-9||Network topology and routes/lines (topology)
|-
| LOS 1-10|| Transport operators
|-
|LOS 1-11|| Timetables
|-
|LOS 1-12||Planned interchanges between guaranteed scheduled services
|-
|LOS 1-13||Hours of operation
|-
| LOS 1-14
|Facilities of access nodes (including platform information, help desk/information points, ticket booths, lifts/stairs, entrances and exit locations)
|-
|LOS 1-15||Vehicles, including their accessibility (such as low floor, wheelchair accessible, pram accessible) and accessibility of on-board services (such as toilets)
|-
|LOS 1-16||Accessibility of access nodes, and paths within an interchange (such as existence of lifts, escalators)
|-
|LOS 1-17||Existence of assistance services (such as existence of on-site assistance)
|-
| colspan="2" |'''e. Trip plan computation'''
|-
|LOS 1-18||Road network (including segregated lanes for bus/taxi)
|-
|LOS 1-19||Cycle network (cycle tracks, cycle lanes, bus-and-cycle lanes, on-road shared with vehicles, on-path shared with pedestrians)
|-
|LOS 1-20||Pedestrian network and accessibility facilities
|-
| ||Framework data
|-
|
|
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Static data - Level of service 2 (LOS 2)'''
|-
| colspan="2" |'''a. Location search – for transport on demand and personal transport'''
|-
|LOS 2-1
|Location of parking places (on and off-street), including accessible parking places for persons with disabilities and persons with reduced mobility
|-
|LOS 2-2||Park & Ride stops
|-
|LOS 2-3
| Park & Drive stops
|-
|LOS 2-4||Bike sharing stations
|-
|LOS 2-5||Car-sharing stations
|-
| LOS 2-6
|Secure bike parking (such as locked bike garages)
|-
|LOS 2-7
|Scooter parking zones
|-
| colspan="2" |'''b. Information service'''
|-
|LOS 2-8||Where and how to buy tickets for scheduled transport, including retail channels, fulfilment methods, payment methods
|-
|LOS 2-9||Where and how to pay for parking, including retail channels, fulfilment methods, payment methods
|-
| colspan="2" |'''c. Auxiliary information – for scheduled transport and transport on demand where relevant'''
|-
|LOS 2-10 ||Basic common standard fares
- fare network data (fare zones/stops and fare stages)

- standard fare structures (point to point including daily and weekly fares, zonal fares, flat fares)
|-
|LOS 2-11||Vehicle facilities such as classes of carriage, on-board Wi-Fi.
|-
| ||
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Static data - Level of service 3 (LOS 3''')
|-
| colspan="2" |'''a. Detailed common standard and special fare query – for scheduled transport and transport on demand where relevant'''
|-
|LOS 3-1||Passenger classes (classes of passenger such as adult, child, senior, student, military/veteran, passenger with disability and passenger with reduced mobility, and qualifying conditions, and classes of travel)
|-
|LOS 3-2|| Common fare products (access rights such as zone/point-to-point including daily and weekly tickets/single/return, eligibility of access, basic usage conditions such as validity period/operator/time of travel/interchanging, standard point-to-point fares prices for different point-to-point pairs including daily and weekly fares/zonal fare prices/flat fare prices)
|-
|LOS 3-3||Special fare products (offers with additional special conditions such as promotional fares, group fares, season passes, aggregated products combining different products, and add-on products such as parking and travel, minimum stay)
|-
|LOS 3-4|| Basic commercial conditions such as refunding, replacing, exchanging or transferring
|-
|LOS 3-5||Basic booking conditions such as purchase windows, validity periods, routing restrictions zonal sequence fares, minimum stay
|-
|LOS 3-6||'''b. Information service – for transport on demand: how to book demand-responsive transport services, including retail channels, fulfilment methods, payment methods'''
|-
| colspan="2" |'''c. Trip plans'''
|-
|LOS 3-7||Detailed cycle network attributes (surface quality, side-by-side cycling, shared surface, on/off road, scenic route, “walk only”, turn or access restrictions, e.g. against flow of traffic)
|-
|LOS 3-8 ||Parameters needed to calculate an environmental factor such as greenhouse gas emissions per vehicle type or passenger mile or per distance walked
|-
|LOS 3-9||Parameters needed to calculate fuel consumption of conventional and alternative fuels
|-
|LOS 3-10
|'''d. Trip plan computation: estimated travel times by day type and time-band by transport mode/combination of transport mode'''
|-
| colspan="2" |
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Static data - Level of service 4 (LOS 4 )'''
|-
| LOS 4-1
|'''a. Historic travel and traffic data on delays – for scheduled transport and transport on demand where relevant'''
|-
| colspan="2" |'''b. Observed data on delays and passing time – for scheduled transport'''
|-
|LOS 4-2
|Length of, and when possible the reason for, delays of at least 60 minutes for rail passenger services (in accordance with Article 19 of Regulation (EU) 2021/782)
|-
|LOS 4-3
|Length of, and when possible the reason for, delays in departure of more than 90 minutes for sea and inland waterways passenger services (in accordance with Article 18 of Regulation (EU) No 1177/2010)
|-
|LOS 4-4
| Length of, and when possible the reason for, delays in departure from a terminal of more than 120 minutes for regular bus and coach passenger services with a scheduled distance of 250 km or more (in accordance with Article 19 of Regulation (EU) No 181/2011)
|-
|LOS 4-5
|Length of, and when possible the reason for, flight delays at departure of at least 120 minutes; and flight delays at arrival of at least 180 minutes (in accordance with Articles 5 and 6 of Regulation (EC) No 261/2004)
|-
| colspan="2" |'''c. Observed data on cancellations – for scheduled transport'''
|-
|LOS 4-6
|Cancellations, and when possible the reason, of rail passenger services
|-
|LOS 4-7
|Cancellations, and when possible the reason, of sea and inland waterways passenger services
|-
|LOS 4-8
|Cancellations, and when possible the reason, of regular bus and coach services with a scheduled distance of 250 km or more
|-
|LOS 4-9
|Cancellations, and when possible the reason, of flights
|-
|LOS 4-10
|'''d. Information on parking tariffs'''
|}

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

{| class="wikitable" style="width:70%"
|-
! width="80px" |Data Categories

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

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

{| class="wikitable" style="width:70%"
|-
! width="80px" |Data Categories
! width="80px" style="text-align:center " |EPIP
! width="80px" | AU
! width="80px" |AT
! width="80px" |ΒΕ
! width="80px" |HR
! width="80px" |DK
! width="80px" |FR
! width="80px" |IT
! width="80px" |NL
! width="150px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |PT
! width="80px" |SI
! width="80px" |CH
! width="80px" |GB
|-
|[[#Data categories|LOS 2-1]]
|
|
|
|
| style="text-align:center;" |✅
|
| style="text-align:center;" |for off-street only
| style="text-align:center " |✅
|
|
|
| |
| style="text-align:center;" |✅
|
|-
|[[#Data categories|LOS 2-2]]||
| ||
|
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
| style="text-align:center;" |✅||
|-
|[[#Data categories|LOS 2-3]]
|
|
|
|
| style="text-align:center " |✅
|
|
| style="text-align:center " |✅
|
|
|
|
| style="text-align:center;" |✅
|
|-
|[[#Data categories|LOS 2-4]]||
| ||
|
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " | ✅
| style="text-align:center;" |✅||
|-
|[[#Data categories|LOS 2-5]]||
| ||
|
| style="text-align:center " |✅|| style="text-align:center " |✅
| style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
| style="text-align:center;" |✅||
|-
|[[#Data categories|LOS 2-6]]||
| ||
|
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |in off-street car parks only|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
|
|
|-
|[[#Data categories|LOS 2-7]]
|
|
|
|
| style="text-align:center " |✅
|
|
| style="text-align:center " |✅
|
|
|
|
|
|
|-
|[[#Data categories|LOS 2-8]]||
| ||
|
| style="text-align:center " |✅|| || style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
| ||
|-
|[[#Data categories|LOS 2-9]]
|
|
|
|
| style="text-align:center " |✅
|
| style="text-align:center " |✅
| style="text-align:center " |✅
|
| style="text-align:center " | ✅
|
| style="text-align:center " |✅
|
|
|-
|[[#Data categories|LOS 2-10]]||
| style="text-align:center;" |✅||
|
| || || style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " | ✅
| || style="text-align:center " |✅
|-
|[[#Data categories|LOS 2-11]]||
| style="text-align:center;" |✅||
| style="text-align:center " |✅
| || || style="text-align:center " | ✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
| || style="text-align:center " |✅
|-
|[[#Data categories|LOS 2-12]]||
| ||
|
| || || style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
| || style="text-align:center " | ✅
|-
|[[#Data categories|LOS 2-13]]||
| ||
| style="text-align:center " |✅
| || style="text-align:center " |✅|| style="text-align:center " | ✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
| || style="text-align:center " |✅
|-
|}

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

{| class="wikitable" style="width:70%"
|-
! width="80px" |Data Categories
! width="80px" style="text-align:center " |EPIP
! width="80px" |AU
! width="80px" |AT
! width="80px" |BE
! width="80px" |HR
! width="80px" |DK
! width="80px" |FR
! width="80px" |IT
! width="80px" |NL
! width="150px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |PT
! width="80px" |SI
! width="80px" |CH
! width="80px" |GB
|-
|[[#Data categories|LOS 3-1]]||
| ||
| style="text-align:center " |✅

| style="text-align:center " | ✅|| || style="text-align:center " |✅ || style="text-align:center " |✅|| || style="text-align:center " |✅|| ||
| || style="text-align:center " | ✅
|-
|[[#Data categories|LOS 3-2]]||
| ||
|
| style="text-align:center " |✅|| || style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| ||
| || style="text-align:center " |✅
|-
|[[#Data categories|LOS 3-3]]||
| ||
|
| || || style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| ||
| || style="text-align:center " |✅
|-
|[[#Data categories|LOS 3-4]]
|
|
|
|
|
|
| style="text-align:center;" |✅
| style="text-align:center " |✅
|
|
|
|
|
|
|-
|[[#Data categories|LOS 3-5]]
|
|
|
|
|
|
| style="text-align:center;" |✅
|
|
|
|
|
|
|
|-
|[[#Data categories|LOS 3-6]]
|
|
|
|
|
|
| style="text-align:center;" |✅
|
|
|
|
|
| style="text-align:center;" |✅
|
|-
|[[#Data categories|LOS 3-7]]||
| ||
|
| || || || || || style="text-align:center " |✅|| ||
| ||
|-
|[[#Data categories|LOS 3-8]]||
| ||
|
| || || style="text-align:center;" |✅|| || || style="text-align:center " |✅|| ||
| ||
|-
|[[#Data categories|LOS 3-9]]||
| ||
|
| || || style="text-align:center;" |✅|| || || style="text-align:center " |✅|| ||
| ||
|-
|[[#Data categories|LOS 3-10]]||
| ||
|
| || || || || || style="text-align:center " |✅|| ||
| style="text-align:center;" |N/A||
|-
|}

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

⚠️ If you believe that your use cases are resolved in an existing profile, it is highly recommended to '''adopt an existing solution''' and cooperate with the corresponding entity. You will save resources while you will ensure that your profile is interoperable.

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

=SIRI National profiles inventory 🌐=

National profiles are specified to cover the national needs. To help implementation, DATA4PT is also in process of delivering SIRI EU minimum profile, in collaboration with relevant CEN group. DATA4PT has prepared a table with the currently available SIRI national profiles, including an overview of data categories that are currently covered. For data categories relevant to static data check the [NeTEx Profiles Inventory https://data4pt.org/w/index.php?title=NeTEX#NeTEx_national_and_EU_minimum_profiles_inventory].

==Published profiles==

{| class="wikitable" style="width : 50%"
|-
!Profile Name!!Status/
Availability
!EU Minimum profile based*!!EU Minimum SIRI profile compatible** !!Documentation
|-
|Australia - Victoria (AU)
|Specified but not yet in operation
| style="text-align:center " |✅
| style="text-align:center " |✅
|
|-
|Croatia (HR)
|Using an existing profile
|
| style="text-align:center " |✅
|
|-
|France (FR)||Specified and in use
| style="text-align:center " |✅|| style="text-align:center;" | ||[https://normes.transport.data.gouv.fr/normes/siri/profil-france/ French SIRI profile]
|-
|Italy (IT)
| Specified and in use
| style="text-align:center " |✅
|
|[https://github.com/5Tsrl/siri-italian-profile/tree/main/Linee%20guida Italian SIRI profile]
|-
|Netherlands (NL)||Specified but not yet in operation
| || style="text-align:center;" |✅||
|-
|Nordic (Norway, Sweden, Finland, Denmark)|| Specified and in use
| || style="text-align:center;" |✅||[https://enturas.atlassian.net/wiki/spaces/PUBLIC/pages/637370420/Nordic+SIRI+Profile Nordic SIRI profile]
|-
|UK (GB) ||Specified and in use
| || style="text-align:center;" |✅||
|-
|Switzerland (CH)
|Specified and in use
| style="text-align:center;" |✅
| style="text-align:center;" |✅
|[https://www.oev-info.ch/sites/default/files/2023-04/siri_realisation-guide_pt_ch_v0.9.0.pdf SIRI-ET/PT][https://www.oev-info.ch/sites/default/files/2024-07/realization_guide_siri-sx_oev_schweiz_v1.0.pdf SIRI-SX]
|}
<nowiki>*</nowiki>Profiles of this category have been specified based on EU Minimum profile and are based on XML technology as EU profiles.

<nowiki>**</nowiki> Profiles of this category have been specified either before the definition of EU Minimum profile, but they have been used to define the EU one, and/or after EU profiles and need conversion or adaptation to be interoperable.
==Data categories==

''Data categories are identified based on [https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex%3A32024R0490 MMTIS EU Regulation 490/2024]''
{| class="mw-collapsible mw-collapsed wikitable" style="width : 60%"
|+ style="white-space:nowrap; border:1px solid; padding:3px;" |Data categories table.
|-
!Level of service (LOS)!!Types of the dynamic travel and traffic data
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Dynamic data - Level of service 1 (LOS 1 )'''
|-
| colspan="2" |'''a. Passing times, trip plans and auxiliary information'''
|-
| LOS 1-1||Disruptions, such as network closures and/or diversions, and when possible, the reason
|-
|LOS 1-2||Real-time status information, such as estimated departure and arrival times of services, delays, cancellations, guaranteed connections monitoring
|-
|LOS 1-3||Status of access node features (including dynamic platform information, operational lifts/escalators, closed entrances and exit locations) – for scheduled transport
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Dynamic data - Level of service 2 (LOS 2)'''
|-
|LOS 2-1||'''a. Information service on parking tariffs – for transport on demand and personal transport'''
|-
| colspan="2" |'''b. Availability check and location – for transport on demand and personal transport where relevant'''
|-
|LOS 2-2||Car-sharing availability and location, bike-sharing availability and location, scooter-sharing availability and location, and other vehicle-sharing availability and location
|-
|LOS 2-3||Car parking spaces available (on and off-street)
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Dynamic data - Level of service 3 (LOS 3''')
|-
|LOS 3-1|| Occupancy information of the vehicle – for scheduled transport and transport on demand where relevant
|}

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

{| class="wikitable" style="width : 30%"
|-
!Data Categories
! width="80px" |AU
! width="80px" |HR
! width="80px" |FR
! width="80px" |IT
! width="80px" |NL
! width="300px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |GB
! width="80px" |CH
|-
|[[#Data categories|LOS 1-1]]
| style="text-align:center " |✅|| || style="text-align:center " |✅
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅ dynamic platform is included || style="text-align:center " |✅
| style="text-align:center;" |✅
|-
|[[#Data categories|LOS 1-2]]
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅ dynamic platform is included || style="text-align:center " |✅
| style="text-align:center;" |✅
|-
|[[#Data categories|LOS 1-3]]
| || || style="text-align:center " |✅
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅ dynamic platform is included || style="text-align:center " |
| style="text-align:center;" |✅
via SX
|-
|}

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

{| class="wikitable" style="width : 30%"
|-
!Data Categories
! width="80px" |AU
! width="80px" |HR
! width="80px" | FR
! width="80px" |IT
! width="80px" |NL
! width="300px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |GB
! width="80px" |CH
|-
|[[#Data categories|LOS 2-1]]
|
|
|
|
|
|
|
|
|-
|[[#Data categories|LOS 2-2]]
| || || style="text-align:center " |only for car sharing and bike sharing
| style="text-align:center " |✅|| || style="text-align:center " |✅||
|
|-
|[[#Data categories|LOS 2-3]]
| || || style="text-align:center " |off-street only
| style="text-align:center " |✅|| || style="text-align:center " |✅||
|
|-
|}

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

{| class="wikitable" style="width : 30%"
|-
!Data Categories
! width="80px" |AU
! width="80px" |FR
! width="80px" |IT
! width="80px" |NL
! width="300px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |GB
! width="80px" |CH
|-
|[[#Data categories|LOS 3-1]]
| style="text-align:center " |✅
| style="text-align:center " |✅
| style="text-align:center " |✅
|
|
|
|
|}

⚠️ If you believe that your use cases are resolved in an existing profile, it is highly recommended to '''adopt an existing solution''' and cooperate with the corresponding entity. You will save resources while you will ensure that your profile is interoperable.

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

=Implementations per Country=
Currently, the implementations of NeTEx and SIRI are documented for the following countries:

* [[Australia]]
* [[Croatia]]
* [[Italy]]

Switzerland

2024-10-02T08:57:47Z

Anonymous:

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

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

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

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

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

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

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

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

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

== Use cases ==

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

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

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

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

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

Short translation:

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

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

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

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

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

Switzerland

2024-10-02T08:48:21Z

Anonymous: Creation of switzerland page

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

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

Via these two channels, Switzerland provides the following data standards for Switzerland:

* '''Timetables'''
** [https://www.oev-info.ch/sites/default/files/2024-05/NeTEx_Core-Realisation_Guide_TP_Suisse-v1.00.pdf NeTEx – Swiss Profile]
** [https://www.oev-info.ch/sites/default/files/2024-04/gtfs_profil_switzerland_version_0_16_en.pdf GTFS – Swiss Profile]
** [https://www.oev-info.ch/sites/default/files/2023-07/hrdf_2_0_5_e.pdf HRDF – Swiss Profile]

* '''On-demand'''
** [https://www.oev-info.ch/sites/default/files/2024-07/Fachkonzept%20On-Demand_v2.1_en.pdf NeTEx]
** [https://www.oev-info.ch/sites/default/files/2024-04/gtfs_profil_switzerland_version_0_16_en.pdf GTFS Flex] (as above)
* '''Realtime data'''
** [https://www.oev-info.ch/sites/default/files/2023-04/siri_realisation-guide_pt_ch_v0.9.0.pdf SIRI-ET/PT – Swiss Profile]
** [https://www.oev-info.ch/sites/default/files/2024-04/gtfs_profil_switzerland_version_0_16_en.pdf GTFS Realtime – Swiss Profile] (see above)
* '''Events'''
** [https://www.oev-info.ch/sites/default/files/2024-07/realization_guide_siri-sx_oev_schweiz_v1.0.pdf SIRI-SX – Swiss Profile]
** [https://www.oev-info.ch/sites/default/files/2024-04/gtfs_profil_switzerland_version_0_16_en.pdf GTFS Service Alerts] (see above)
* '''Routing'''
** OJP 1.0 – Swiss Profile
*** [https://www.oev-info.ch/sites/default/files/2023-05/open_journey_planner_ojp_de_v1_eng.pdf Documentation]
*** [https://opentransportdata.swiss/de/dataset/ojp2020 API]
** OJP 2.0 – Swiss Profile
*** Documentation: Work In Progress
*** [https://opentransportdata.swiss/de/dataset/ojp2-0 API]
* '''Fares'''
** OJP-Fare – Swiss Profile
*** [https://opentransportdata.swiss/en/cookbook/beta-price-information-with-ojp-fares-2/ Documentation]:
*** [https://opentransportdata.swiss/de/dataset/ojpfare API]

== Uses cases ==

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

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

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

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

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

Short translation:

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

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

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

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

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

File:Swiss architecture.png

2024-10-02T08:46:21Z

Anonymous:

Swiss architecture

National Implementations

2024-09-27T09:59:28Z

Anonymous: added links to 3 countries

= NeTEx national profiles inventory 🌐 =

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

== Published profiles ==

{| class="wikitable" style="width : 60%"
|-
! width="150px"| Profile Name
!Status/
Availability
! width="100px" | NeTEx EPIP Based* !! width="100px" | NeTEx EPIP Compatible**
! width="300px" | Documentation
|-
| Australia - Victoria (AU)
|Specified but not yet in operation
| style="text-align:center;" |✅
| style="text-align:center;" |✅
|
|-
|Austria (AT)
|Specified but not yet in operation|| style="text-align:center;" |✅|| ||[https://mobilitaetsverbuende.atlassian.net/wiki/spaces/NET/overview Austrian profile]
|-
|Belgium (BE)
|Specified but not yet in operation|| style="text-align:center;" |✅|| ||[https://github.com/Informatievlaanderen/OSLOthema-mobiliteitDienstregelingEnPlanning GitHUb]
[https://purl.eu/doc/applicationprofile/netex-belgium/timetables-ap/ AP-Timetables]

[https://purl.eu/doc/applicationprofile/netex-belgium/stopplaces-ap/ AP-Stops]

[https://purl.eu/doc/applicationprofile/netex-belgium/vehiclescheduling-ap/ AP-Vehicle Scheduling]

[https://purl.eu/ns/mobility/timetables-and-planning/ AP-TimetablesAndPlanning]

[https://github.com/Informatievlaanderen/OSLOthema-mobiliteitDienstregelingEnPlanning/tree/master/resources/DataExamples Data examples]
|-
|Croatia (HR)
|Specified and in use
| style="text-align:center;" | ✅
| style="text-align:center;" |✅
|[https://www.promet-info.hr/en NPT - Croatian NAP]
|-
|Denmark (DK)
|Specified but not yet in operation|| style="text-align:center;" |✅|| ||[https://www.trafikstyrelsen.dk/Media/638013312835439194/Vejledning%20om%20brug%20af%20NeTEx.pdf Denmark profile] - [https://www.trafikstyrelsen.dk/arbejdsomraader/kollektiv-trafik/statistik-og-data/krav-til-udstilling-af-data-til-rejseplanlaegning NAP in Denmark]
|-
|France (FR)
|Specified and in use|| || style="text-align:center;" |✅||[https://normes.transport.data.gouv.fr/normes/netex/ French profile] - [https://normes.transport.data.gouv.fr/normes/netex/elements_communs/ Common profile] - [https://normes.transport.data.gouv.fr/normes/netex/arrets/ Stop profile] - [https://normes.transport.data.gouv.fr/normes/netex/reseaux/ Network profile] - [https://normes.transport.data.gouv.fr/normes/netex/horaires/ Timetable profile] - [https://normes.transport.data.gouv.fr/normes/netex/tarifs/ Fare profile] - [https://normes.transport.data.gouv.fr/normes/netex/parkings/ Parking profile] - [https://normes.transport.data.gouv.fr/normes/netex/accessibilite/ Accessibility profile]
|-
|Italy (IT)
|Specified and in use|| style="text-align:center;" |✅||
|[https://github.com/5Tsrl/netex-italian-profile/tree/main/Linee%20guida Italian profile]
|-
|Netherlands (NL)
|Specified but not yet in operation|| style="text-align:center;" |✅|| ||[https://bison.dova.nu/standaarden/nederlands-netex-profiel Netherlands profile] - [https://bison.dova.nu/sites/default/files/bison_prijzen_producten_en_tarieven_v8.1.3.0_release.pdf Bison Fares]
|-
| Nordic (Norway, Sweden, Finland, Denmark)
|Specified and in use|| || style="text-align:center;" |✅||[https://enturas.atlassian.net/wiki/spaces/PUBLIC/pages/728891481/Nordic+NeTEx+Profile Nordic profile]
|-
|Portugal (PT)
|Specified and in use|| || ||[https://ptprofiles.azurewebsites.net/netex-profile Portuguese profile]
|-
| Slovenija (SI)
|Specified but not yet in operation|| || style="text-align:center " |✅||[https://www.nap.si/_resources/profiles/NeTEx_SI_Profile_v2.pdf Slovenian profile]
|-
|UK (GB)
|Specified and in use|| || style="text-align:center " |✅||[http://netex.uk/farexchange/ UK profile] - [http://netex.uk/farexchange/doc/uk_profile/DfT-NeTEx-1-Fares-Intro-2019.06.17-v0.09.pdf Introduction] - [http://netex.uk/farexchange/doc/uk_profile/DfT-NeTEx-2-Base_Spec-2019.06.30-v0.14.pdf Stop and Timetables] - [http://netex.uk/farexchange/doc/uk_profile/DfT-NeTEx-3-Fares_Spec-2019.06.17-v0.17.pdf Fares]
|-
|Ireland (IE)
|Specified and in use|| || ||[https://netex.ie/ Irish profile] - [http://netex.uk/netexie/doc/EIRE_NP/NTA-NeTEx-1-Spec-2020.08.12-v0.22.pdf Profile Elements] - [http://netex.uk/netexie/doc/EIRE_NP/NTA-NeTEx-2-Mappings-2020.08.06-v0.22.pdf Profile Data Mappings]
|-
|Czech Republic (CZ)
|Specified but not yet in operation
| style="text-align:center " |✅
|
|
|}
<nowiki>*</nowiki>Profiles of this category have been specified based on EU Minimum profile and are based on XML technology as EU profiles.

<nowiki>**</nowiki> Profiles of this category have been specified either before the definition of EU Minimum profile, but they have been used to define the EU one, and/or after EU profiles and need conversion or adaptation to be interoperable.
==Data categories==

''Data categories are identified based on [https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex%3A32024R0490 MMTIS EU Regulation 490/2024]''
{| class="mw-collapsible mw-collapsed wikitable" style="width:70%"
|+ style="white-space:nowrap; border:1px solid; padding:3px;" | Data categories table.
|-
!Level of service (LOS)!!Static data
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Static data - Level of service 1 (LOS 1 )'''
|-
| colspan="2" |'''a. Location search (origin/destination)'''
|-
|LOS 1-1||Address identifiers (building number, street name, postcode)
|-
| LOS 1-2||Topographic places (city, town, village, suburb, administrative unit)
|-
|LOS 1-3||Points of interest (related to transport information) to which people may wish to travel
|-
|LOS 1-4||'''b. Trip plans: operational calendar, mapping day types to calendar dates'''
|-
| colspan="2" |'''c. Location search (access nodes) – for scheduled transport and transport on demand where relevant'''
|-
|LOS 1-5
| Identified access nodes
|-
|LOS 1-6 ||Geometry/map layout structure of access nodes

|-
| colspan="2" |'''d. Trip plan computation – for scheduled transport and transport on demand where relevant'''
|-
|LOS 1-7||Connection where interchanges may be made
|-
|LOS 1-8
|Default transfer times at interchanges
|-
|LOS 1-9||Network topology and routes/lines (topology)
|-
| LOS 1-10|| Transport operators
|-
|LOS 1-11|| Timetables
|-
|LOS 1-12||Planned interchanges between guaranteed scheduled services
|-
|LOS 1-13||Hours of operation
|-
| LOS 1-14
|Facilities of access nodes (including platform information, help desk/information points, ticket booths, lifts/stairs, entrances and exit locations)
|-
|LOS 1-15||Vehicles, including their accessibility (such as low floor, wheelchair accessible, pram accessible) and accessibility of on-board services (such as toilets)
|-
|LOS 1-16||Accessibility of access nodes, and paths within an interchange (such as existence of lifts, escalators)
|-
|LOS 1-17||Existence of assistance services (such as existence of on-site assistance)
|-
| colspan="2" |'''e. Trip plan computation'''
|-
|LOS 1-18||Road network (including segregated lanes for bus/taxi)
|-
|LOS 1-19||Cycle network (cycle tracks, cycle lanes, bus-and-cycle lanes, on-road shared with vehicles, on-path shared with pedestrians)
|-
|LOS 1-20||Pedestrian network and accessibility facilities
|-
| ||Framework data
|-
|
|
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Static data - Level of service 2 (LOS 2)'''
|-
| colspan="2" |'''a. Location search – for transport on demand and personal transport'''
|-
|LOS 2-1
|Location of parking places (on and off-street), including accessible parking places for persons with disabilities and persons with reduced mobility
|-
|LOS 2-2||Park & Ride stops
|-
|LOS 2-3
| Park & Drive stops
|-
|LOS 2-4||Bike sharing stations
|-
|LOS 2-5||Car-sharing stations
|-
| LOS 2-6
|Secure bike parking (such as locked bike garages)
|-
|LOS 2-7
|Scooter parking zones
|-
| colspan="2" |'''b. Information service'''
|-
|LOS 2-8||Where and how to buy tickets for scheduled transport, including retail channels, fulfilment methods, payment methods
|-
|LOS 2-9||Where and how to pay for parking, including retail channels, fulfilment methods, payment methods
|-
| colspan="2" |'''c. Auxiliary information – for scheduled transport and transport on demand where relevant'''
|-
|LOS 2-10 ||Basic common standard fares
- fare network data (fare zones/stops and fare stages)

- standard fare structures (point to point including daily and weekly fares, zonal fares, flat fares)
|-
|LOS 2-11||Vehicle facilities such as classes of carriage, on-board Wi-Fi.
|-
| ||
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Static data - Level of service 3 (LOS 3''')
|-
| colspan="2" |'''a. Detailed common standard and special fare query – for scheduled transport and transport on demand where relevant'''
|-
|LOS 3-1||Passenger classes (classes of passenger such as adult, child, senior, student, military/veteran, passenger with disability and passenger with reduced mobility, and qualifying conditions, and classes of travel)
|-
|LOS 3-2|| Common fare products (access rights such as zone/point-to-point including daily and weekly tickets/single/return, eligibility of access, basic usage conditions such as validity period/operator/time of travel/interchanging, standard point-to-point fares prices for different point-to-point pairs including daily and weekly fares/zonal fare prices/flat fare prices)
|-
|LOS 3-3||Special fare products (offers with additional special conditions such as promotional fares, group fares, season passes, aggregated products combining different products, and add-on products such as parking and travel, minimum stay)
|-
|LOS 3-4|| Basic commercial conditions such as refunding, replacing, exchanging or transferring
|-
|LOS 3-5||Basic booking conditions such as purchase windows, validity periods, routing restrictions zonal sequence fares, minimum stay
|-
|LOS 3-6||'''b. Information service – for transport on demand: how to book demand-responsive transport services, including retail channels, fulfilment methods, payment methods'''
|-
| colspan="2" |'''c. Trip plans'''
|-
|LOS 3-7||Detailed cycle network attributes (surface quality, side-by-side cycling, shared surface, on/off road, scenic route, “walk only”, turn or access restrictions, e.g. against flow of traffic)
|-
|LOS 3-8 ||Parameters needed to calculate an environmental factor such as greenhouse gas emissions per vehicle type or passenger mile or per distance walked
|-
|LOS 3-9||Parameters needed to calculate fuel consumption of conventional and alternative fuels
|-
|LOS 3-10
|'''d. Trip plan computation: estimated travel times by day type and time-band by transport mode/combination of transport mode'''
|-
| colspan="2" |
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Static data - Level of service 4 (LOS 4 )'''
|-
| LOS 4-1
|'''a. Historic travel and traffic data on delays – for scheduled transport and transport on demand where relevant'''
|-
| colspan="2" |'''b. Observed data on delays and passing time – for scheduled transport'''
|-
|LOS 4-2
|Length of, and when possible the reason for, delays of at least 60 minutes for rail passenger services (in accordance with Article 19 of Regulation (EU) 2021/782)
|-
|LOS 4-3
|Length of, and when possible the reason for, delays in departure of more than 90 minutes for sea and inland waterways passenger services (in accordance with Article 18 of Regulation (EU) No 1177/2010)
|-
|LOS 4-4
| Length of, and when possible the reason for, delays in departure from a terminal of more than 120 minutes for regular bus and coach passenger services with a scheduled distance of 250 km or more (in accordance with Article 19 of Regulation (EU) No 181/2011)
|-
|LOS 4-5
|Length of, and when possible the reason for, flight delays at departure of at least 120 minutes; and flight delays at arrival of at least 180 minutes (in accordance with Articles 5 and 6 of Regulation (EC) No 261/2004)
|-
| colspan="2" |'''c. Observed data on cancellations – for scheduled transport'''
|-
|LOS 4-6
|Cancellations, and when possible the reason, of rail passenger services
|-
|LOS 4-7
|Cancellations, and when possible the reason, of sea and inland waterways passenger services
|-
|LOS 4-8
|Cancellations, and when possible the reason, of regular bus and coach services with a scheduled distance of 250 km or more
|-
|LOS 4-9
|Cancellations, and when possible the reason, of flights
|-
|LOS 4-10
|'''d. Information on parking tariffs'''
|}

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

{| class="wikitable" style="width:70%"
|-
! width="80px" |Data Categories

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

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

{| class="wikitable" style="width:70%"
|-
! width="80px" |Data Categories
! width="80px" style="text-align:center " |EPIP
! width="80px" | AU
! width="80px" |AT
! width="80px" |ΒΕ
! width="80px" |HR
! width="80px" |DK
! width="80px" |FR
! width="80px" |IT
! width="80px" |NL
! width="150px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |PT
! width="80px" |SI
! width="80px" |GB
|-
|[[#Data categories|LOS 2-1]]
|
|
|
|
| style="text-align:center;" |✅
|
| style="text-align:center;" |for off-street only
| style="text-align:center " |✅
|
|
|
| |
|
|-
|[[#Data categories|LOS 2-2]]||
| ||
|
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅||
|-
|[[#Data categories|LOS 2-3]]
|
|
|
|
| style="text-align:center " |✅
|
|
| style="text-align:center " |✅
|
|
|
|
|
|-
|[[#Data categories|LOS 2-4]]||
| ||
|
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " | ✅||
|-
|[[#Data categories|LOS 2-5]]||
| ||
|
| style="text-align:center " |✅|| style="text-align:center " |✅
| style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅||
|-
|[[#Data categories|LOS 2-6]]||
| ||
|
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |in off-street car parks only|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
|
|-
|[[#Data categories|LOS 2-7]]
|
|
|
|
| style="text-align:center " |✅
|
|
| style="text-align:center " |✅
|
|
|
|
|
|-
|[[#Data categories|LOS 2-8]]||
| ||
|
| style="text-align:center " |✅|| || style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅||
|-
|[[#Data categories|LOS 2-9]]
|
|
|
|
| style="text-align:center " |✅
|
| style="text-align:center " |✅
| style="text-align:center " |✅
|
| style="text-align:center " | ✅
|
| style="text-align:center " |✅
|
|-
|[[#Data categories|LOS 2-10]]||
| style="text-align:center;" |✅||
|
| || || style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " | ✅|| style="text-align:center " |✅
|-
|[[#Data categories|LOS 2-11]]||
| style="text-align:center;" |✅||
| style="text-align:center " |✅
| || || style="text-align:center " | ✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅|| style="text-align:center " |✅
|-
|[[#Data categories|LOS 2-12]]||
| ||
|
| || || style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅|| style="text-align:center " | ✅
|-
|[[#Data categories|LOS 2-13]]||
| ||
| style="text-align:center " |✅
| || style="text-align:center " |✅|| style="text-align:center " | ✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅|| style="text-align:center " |✅
|-
|}

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

{| class="wikitable" style="width:70%"
|-
! width="80px" |Data Categories
! width="80px" style="text-align:center " |EPIP
! width="80px" |AU
! width="80px" |AT
! width="80px" |BE
! width="80px" |HR
! width="80px" |DK
! width="80px" |FR
! width="80px" |IT
! width="80px" |NL
! width="150px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |PT
! width="80px" |SI
! width="80px" |GB
|-
|[[#Data categories|LOS 3-1]]||
| ||
| style="text-align:center " |✅

| style="text-align:center " | ✅|| || style="text-align:center " |✅ || style="text-align:center " |✅|| || style="text-align:center " |✅|| || || style="text-align:center " | ✅
|-
|[[#Data categories|LOS 3-2]]||
| ||
|
| style="text-align:center " |✅|| || style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || || style="text-align:center " |✅
|-
|[[#Data categories|LOS 3-3]]||
| ||
|
| || || style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || || style="text-align:center " |✅
|-
|[[#Data categories|LOS 3-4]]
|
|
|
|
|
|
| style="text-align:center;" |✅
| style="text-align:center " |✅
|
|
|
|
|
|-
|[[#Data categories|LOS 3-5]]
|
|
|
|
|
|
| style="text-align:center;" |✅
|
|
|
|
|
|
|-
|[[#Data categories|LOS 3-6]]
|
|
|
|
|
|
| style="text-align:center;" |✅
|
|
|
|
|
|
|-
|[[#Data categories|LOS 3-7]]||
| ||
|
| || || || || || style="text-align:center " |✅|| || ||
|-
|[[#Data categories|LOS 3-8]]||
| ||
|
| || || style="text-align:center;" |✅|| || || style="text-align:center " |✅|| || ||
|-
|[[#Data categories|LOS 3-9]]||
| ||
|
| || || style="text-align:center;" |✅|| || || style="text-align:center " |✅|| || ||
|-
|[[#Data categories|LOS 3-10]]||
| ||
|
| || || || || || style="text-align:center " |✅|| || ||
|-
|}

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

⚠️ If you believe that your use cases are resolved in an existing profile, it is highly recommended to '''adopt an existing solution''' and cooperate with the corresponding entity. You will save resources while you will ensure that your profile is interoperable.

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

=SIRI National profiles inventory 🌐=

National profiles are specified to cover the national needs. To help implementation, DATA4PT is also in process of delivering SIRI EU minimum profile, in collaboration with relevant CEN group. DATA4PT has prepared a table with the currently available SIRI national profiles, including an overview of data categories that are currently covered. For data categories relevant to static data check the [NeTEx Profiles Inventory https://data4pt.org/w/index.php?title=NeTEX#NeTEx_national_and_EU_minimum_profiles_inventory].

==Published profiles==

{| class="wikitable" style="width : 50%"
|-
!Profile Name!!Status/
Availability
!EU Minimum profile based*!!EU Minimum SIRI profile compatible** !!Documentation
|-
|Australia - Victoria (AU)
|Specified but not yet in operation
| style="text-align:center " |✅
| style="text-align:center " |✅
|
|-
|Croatia (HR)
|Using an existing profile
|
| style="text-align:center " |✅
|
|-
|France (FR)||Specified and in use
| style="text-align:center " |✅|| style="text-align:center;" | ||[https://normes.transport.data.gouv.fr/normes/siri/profil-france/ French SIRI profile]
|-
|Italy (IT)
| Specified and in use
| style="text-align:center " |✅
|
|[https://github.com/5Tsrl/siri-italian-profile/tree/main/Linee%20guida Italian SIRI profile]
|-
|Netherlands (NL)||Specified but not yet in operation
| || style="text-align:center;" |✅||
|-
|Nordic (Norway, Sweden, Finland, Denmark)|| Specified and in use
| || style="text-align:center;" |✅||[https://enturas.atlassian.net/wiki/spaces/PUBLIC/pages/637370420/Nordic+SIRI+Profile Nordic SIRI profile]
|-
|UK (GB) ||Specified and in use
| || style="text-align:center;" |✅||
|-
|}
<nowiki>*</nowiki>Profiles of this category have been specified based on EU Minimum profile and are based on XML technology as EU profiles.

<nowiki>**</nowiki> Profiles of this category have been specified either before the definition of EU Minimum profile, but they have been used to define the EU one, and/or after EU profiles and need conversion or adaptation to be interoperable.
==Data categories==

''Data categories are identified based on [https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex%3A32024R0490 MMTIS EU Regulation 490/2024]''
{| class="mw-collapsible mw-collapsed wikitable" style="width : 60%"
|+ style="white-space:nowrap; border:1px solid; padding:3px;" |Data categories table.
|-
!Level of service (LOS)!!Types of the dynamic travel and traffic data
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Dynamic data - Level of service 1 (LOS 1 )'''
|-
| colspan="2" |'''a. Passing times, trip plans and auxiliary information'''
|-
| LOS 1-1||Disruptions, such as network closures and/or diversions, and when possible, the reason
|-
|LOS 1-2||Real-time status information, such as estimated departure and arrival times of services, delays, cancellations, guaranteed connections monitoring
|-
|LOS 1-3||Status of access node features (including dynamic platform information, operational lifts/escalators, closed entrances and exit locations) – for scheduled transport
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Dynamic data - Level of service 2 (LOS 2)'''
|-
|LOS 2-1||'''a. Information service on parking tariffs – for transport on demand and personal transport'''
|-
| colspan="2" |'''b. Availability check and location – for transport on demand and personal transport where relevant'''
|-
|LOS 2-2||Car-sharing availability and location, bike-sharing availability and location, scooter-sharing availability and location, and other vehicle-sharing availability and location
|-
|LOS 2-3||Car parking spaces available (on and off-street)
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Dynamic data - Level of service 3 (LOS 3''')
|-
|LOS 3-1|| Occupancy information of the vehicle – for scheduled transport and transport on demand where relevant
|}

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

{| class="wikitable" style="width : 30%"
|-
!Data Categories
! width="80px" |AU
! width="80px" |HR
! width="80px" |FR
! width="80px" |IT
! width="80px" |NL
! width="300px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |GB
|-
|[[#Data categories|LOS 1-1]]
| style="text-align:center " |✅|| || style="text-align:center " |✅
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅ dynamic platform is included || style="text-align:center " |✅
|-
|[[#Data categories|LOS 1-2]]
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅ dynamic platform is included || style="text-align:center " |✅
|-
|[[#Data categories|LOS 1-3]]
| || || style="text-align:center " |✅
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅ dynamic platform is included || style="text-align:center " |
|-
|}

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

{| class="wikitable" style="width : 30%"
|-
!Data Categories
! width="80px" |AU
! width="80px" |HR
! width="80px" | FR
! width="80px" |IT
! width="80px" |NL
! width="300px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |GB
|-
|[[#Data categories|LOS 2-1]]
|
|
|
|
|
|
|
|-
|[[#Data categories|LOS 2-2]]
| || || style="text-align:center " |only for car sharing and bike sharing
| style="text-align:center " |✅|| || style="text-align:center " |✅||
|-
|[[#Data categories|LOS 2-3]]
| || || style="text-align:center " |off-street only
| style="text-align:center " |✅|| || style="text-align:center " |✅||
|-
|}

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

{| class="wikitable" style="width : 30%"
|-
!Data Categories
! width="80px" |AU
! width="80px" |FR
! width="80px" |IT
! width="80px" |NL
! width="300px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |GB
|-
|[[#Data categories|LOS 3-1]]
| style="text-align:center " |✅
| style="text-align:center " |✅
| style="text-align:center " |✅
|
|
|
|}

⚠️ If you believe that your use cases are resolved in an existing profile, it is highly recommended to '''adopt an existing solution''' and cooperate with the corresponding entity. You will save resources while you will ensure that your profile is interoperable.

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

=Implementations per Country=
Currently, the implementations of NeTEx and SIRI are documented for the following countries:

* [[Australia]]
* [[Croatia]]
* [[Italy]]

National Implementations

2024-09-27T09:43:25Z

Anonymous: /* NeTEx national profiles inventory 🌐 */

= NeTEx national profiles inventory 🌐 =

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

== Published profiles ==

{| class="wikitable" style="width : 60%"
|-
! width="150px"| Profile Name
!Status/
Availability
! width="100px" | NeTEx EPIP Based* !! width="100px" | NeTEx EPIP Compatible**
! width="300px" | Documentation
|-
| Australia - Victoria (AU)
|Specified but not yet in operation
| style="text-align:center;" |✅
| style="text-align:center;" |✅
|
|-
|Austria (AT)
|Specified but not yet in operation|| style="text-align:center;" |✅|| ||[https://mobilitaetsverbuende.atlassian.net/wiki/spaces/NET/overview Austrian profile]
|-
|Belgium (BE)
|Specified but not yet in operation|| style="text-align:center;" |✅|| ||[https://github.com/Informatievlaanderen/OSLOthema-mobiliteitDienstregelingEnPlanning GitHUb]
[https://purl.eu/doc/applicationprofile/netex-belgium/timetables-ap/ AP-Timetables]

[https://purl.eu/doc/applicationprofile/netex-belgium/stopplaces-ap/ AP-Stops]

[https://purl.eu/doc/applicationprofile/netex-belgium/vehiclescheduling-ap/ AP-Vehicle Scheduling]

[https://purl.eu/ns/mobility/timetables-and-planning/ AP-TimetablesAndPlanning]

[https://github.com/Informatievlaanderen/OSLOthema-mobiliteitDienstregelingEnPlanning/tree/master/resources/DataExamples Data examples]
|-
|Croatia (HR)
|Specified and in use
| style="text-align:center;" | ✅
| style="text-align:center;" |✅
|[https://www.promet-info.hr/en NPT - Croatian NAP]
|-
|Denmark (DK)
|Specified but not yet in operation|| style="text-align:center;" |✅|| ||[https://www.trafikstyrelsen.dk/Media/638013312835439194/Vejledning%20om%20brug%20af%20NeTEx.pdf Denmark profile] - [https://www.trafikstyrelsen.dk/arbejdsomraader/kollektiv-trafik/statistik-og-data/krav-til-udstilling-af-data-til-rejseplanlaegning NAP in Denmark]
|-
|France (FR)
|Specified and in use|| || style="text-align:center;" |✅||[https://normes.transport.data.gouv.fr/normes/netex/ French profile] - [https://normes.transport.data.gouv.fr/normes/netex/elements_communs/ Common profile] - [https://normes.transport.data.gouv.fr/normes/netex/arrets/ Stop profile] - [https://normes.transport.data.gouv.fr/normes/netex/reseaux/ Network profile] - [https://normes.transport.data.gouv.fr/normes/netex/horaires/ Timetable profile] - [https://normes.transport.data.gouv.fr/normes/netex/tarifs/ Fare profile] - [https://normes.transport.data.gouv.fr/normes/netex/parkings/ Parking profile] - [https://normes.transport.data.gouv.fr/normes/netex/accessibilite/ Accessibility profile]
|-
|Italy (IT)
|Specified and in use|| style="text-align:center;" |✅||
|[https://github.com/5Tsrl/netex-italian-profile/tree/main/Linee%20guida Italian profile]
|-
|Netherlands (NL)
|Specified but not yet in operation|| style="text-align:center;" |✅|| ||[https://bison.dova.nu/standaarden/nederlands-netex-profiel Netherlands profile] - [https://bison.dova.nu/sites/default/files/bison_prijzen_producten_en_tarieven_v8.1.3.0_release.pdf Bison Fares]
|-
| Nordic (Norway, Sweden, Finland, Denmark)
|Specified and in use|| || style="text-align:center;" |✅||[https://enturas.atlassian.net/wiki/spaces/PUBLIC/pages/728891481/Nordic+NeTEx+Profile Nordic profile]
|-
|Portugal (PT)
|Specified and in use|| || ||[https://ptprofiles.azurewebsites.net/netex-profile Portuguese profile]
|-
| Slovenija (SI)
|Specified but not yet in operation|| || style="text-align:center " |✅||[https://www.nap.si/_resources/profiles/NeTEx_SI_Profile_v2.pdf Slovenian profile]
|-
|UK (GB)
|Specified and in use|| || style="text-align:center " |✅||[http://netex.uk/farexchange/ UK profile] - [http://netex.uk/farexchange/doc/uk_profile/DfT-NeTEx-1-Fares-Intro-2019.06.17-v0.09.pdf Introduction] - [http://netex.uk/farexchange/doc/uk_profile/DfT-NeTEx-2-Base_Spec-2019.06.30-v0.14.pdf Stop and Timetables] - [http://netex.uk/farexchange/doc/uk_profile/DfT-NeTEx-3-Fares_Spec-2019.06.17-v0.17.pdf Fares]
|-
|Ireland (IE)
|Specified and in use|| || ||[https://netex.ie/ Irish profile] - [http://netex.uk/netexie/doc/EIRE_NP/NTA-NeTEx-1-Spec-2020.08.12-v0.22.pdf Profile Elements] - [http://netex.uk/netexie/doc/EIRE_NP/NTA-NeTEx-2-Mappings-2020.08.06-v0.22.pdf Profile Data Mappings]
|-
|Czech Republic (CZ)
|Specified but not yet in operation
| style="text-align:center " |✅
|
|
|}
<nowiki>*</nowiki>Profiles of this category have been specified based on EU Minimum profile and are based on XML technology as EU profiles.

<nowiki>**</nowiki> Profiles of this category have been specified either before the definition of EU Minimum profile, but they have been used to define the EU one, and/or after EU profiles and need conversion or adaptation to be interoperable.
==Data categories==

''Data categories are identified based on [https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex%3A32024R0490 MMTIS EU Regulation 490/2024]''
{| class="mw-collapsible mw-collapsed wikitable" style="width:70%"
|+ style="white-space:nowrap; border:1px solid; padding:3px;" | Data categories table.
|-
!Level of service (LOS)!!Static data
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Static data - Level of service 1 (LOS 1 )'''
|-
| colspan="2" |'''a. Location search (origin/destination)'''
|-
|LOS 1-1||Address identifiers (building number, street name, postcode)
|-
| LOS 1-2||Topographic places (city, town, village, suburb, administrative unit)
|-
|LOS 1-3||Points of interest (related to transport information) to which people may wish to travel
|-
|LOS 1-4||'''b. Trip plans: operational calendar, mapping day types to calendar dates'''
|-
| colspan="2" |'''c. Location search (access nodes) – for scheduled transport and transport on demand where relevant'''
|-
|LOS 1-5
| Identified access nodes
|-
|LOS 1-6 ||Geometry/map layout structure of access nodes

|-
| colspan="2" |'''d. Trip plan computation – for scheduled transport and transport on demand where relevant'''
|-
|LOS 1-7||Connection where interchanges may be made
|-
|LOS 1-8
|Default transfer times at interchanges
|-
|LOS 1-9||Network topology and routes/lines (topology)
|-
| LOS 1-10|| Transport operators
|-
|LOS 1-11|| Timetables
|-
|LOS 1-12||Planned interchanges between guaranteed scheduled services
|-
|LOS 1-13||Hours of operation
|-
| LOS 1-14
|Facilities of access nodes (including platform information, help desk/information points, ticket booths, lifts/stairs, entrances and exit locations)
|-
|LOS 1-15||Vehicles, including their accessibility (such as low floor, wheelchair accessible, pram accessible) and accessibility of on-board services (such as toilets)
|-
|LOS 1-16||Accessibility of access nodes, and paths within an interchange (such as existence of lifts, escalators)
|-
|LOS 1-17||Existence of assistance services (such as existence of on-site assistance)
|-
| colspan="2" |'''e. Trip plan computation'''
|-
|LOS 1-18||Road network (including segregated lanes for bus/taxi)
|-
|LOS 1-19||Cycle network (cycle tracks, cycle lanes, bus-and-cycle lanes, on-road shared with vehicles, on-path shared with pedestrians)
|-
|LOS 1-20||Pedestrian network and accessibility facilities
|-
| ||Framework data
|-
|
|
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Static data - Level of service 2 (LOS 2)'''
|-
| colspan="2" |'''a. Location search – for transport on demand and personal transport'''
|-
|LOS 2-1
|Location of parking places (on and off-street), including accessible parking places for persons with disabilities and persons with reduced mobility
|-
|LOS 2-2||Park & Ride stops
|-
|LOS 2-3
| Park & Drive stops
|-
|LOS 2-4||Bike sharing stations
|-
|LOS 2-5||Car-sharing stations
|-
| LOS 2-6
|Secure bike parking (such as locked bike garages)
|-
|LOS 2-7
|Scooter parking zones
|-
| colspan="2" |'''b. Information service'''
|-
|LOS 2-8||Where and how to buy tickets for scheduled transport, including retail channels, fulfilment methods, payment methods
|-
|LOS 2-9||Where and how to pay for parking, including retail channels, fulfilment methods, payment methods
|-
| colspan="2" |'''c. Auxiliary information – for scheduled transport and transport on demand where relevant'''
|-
|LOS 2-10 ||Basic common standard fares
- fare network data (fare zones/stops and fare stages)

- standard fare structures (point to point including daily and weekly fares, zonal fares, flat fares)
|-
|LOS 2-11||Vehicle facilities such as classes of carriage, on-board Wi-Fi.
|-
| ||
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Static data - Level of service 3 (LOS 3''')
|-
| colspan="2" |'''a. Detailed common standard and special fare query – for scheduled transport and transport on demand where relevant'''
|-
|LOS 3-1||Passenger classes (classes of passenger such as adult, child, senior, student, military/veteran, passenger with disability and passenger with reduced mobility, and qualifying conditions, and classes of travel)
|-
|LOS 3-2|| Common fare products (access rights such as zone/point-to-point including daily and weekly tickets/single/return, eligibility of access, basic usage conditions such as validity period/operator/time of travel/interchanging, standard point-to-point fares prices for different point-to-point pairs including daily and weekly fares/zonal fare prices/flat fare prices)
|-
|LOS 3-3||Special fare products (offers with additional special conditions such as promotional fares, group fares, season passes, aggregated products combining different products, and add-on products such as parking and travel, minimum stay)
|-
|LOS 3-4|| Basic commercial conditions such as refunding, replacing, exchanging or transferring
|-
|LOS 3-5||Basic booking conditions such as purchase windows, validity periods, routing restrictions zonal sequence fares, minimum stay
|-
|LOS 3-6||'''b. Information service – for transport on demand: how to book demand-responsive transport services, including retail channels, fulfilment methods, payment methods'''
|-
| colspan="2" |'''c. Trip plans'''
|-
|LOS 3-7||Detailed cycle network attributes (surface quality, side-by-side cycling, shared surface, on/off road, scenic route, “walk only”, turn or access restrictions, e.g. against flow of traffic)
|-
|LOS 3-8 ||Parameters needed to calculate an environmental factor such as greenhouse gas emissions per vehicle type or passenger mile or per distance walked
|-
|LOS 3-9||Parameters needed to calculate fuel consumption of conventional and alternative fuels
|-
|LOS 3-10
|'''d. Trip plan computation: estimated travel times by day type and time-band by transport mode/combination of transport mode'''
|-
| colspan="2" |
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Static data - Level of service 4 (LOS 4 )'''
|-
| LOS 4-1
|'''a. Historic travel and traffic data on delays – for scheduled transport and transport on demand where relevant'''
|-
| colspan="2" |'''b. Observed data on delays and passing time – for scheduled transport'''
|-
|LOS 4-2
|Length of, and when possible the reason for, delays of at least 60 minutes for rail passenger services (in accordance with Article 19 of Regulation (EU) 2021/782)
|-
|LOS 4-3
|Length of, and when possible the reason for, delays in departure of more than 90 minutes for sea and inland waterways passenger services (in accordance with Article 18 of Regulation (EU) No 1177/2010)
|-
|LOS 4-4
| Length of, and when possible the reason for, delays in departure from a terminal of more than 120 minutes for regular bus and coach passenger services with a scheduled distance of 250 km or more (in accordance with Article 19 of Regulation (EU) No 181/2011)
|-
|LOS 4-5
|Length of, and when possible the reason for, flight delays at departure of at least 120 minutes; and flight delays at arrival of at least 180 minutes (in accordance with Articles 5 and 6 of Regulation (EC) No 261/2004)
|-
| colspan="2" |'''c. Observed data on cancellations – for scheduled transport'''
|-
|LOS 4-6
|Cancellations, and when possible the reason, of rail passenger services
|-
|LOS 4-7
|Cancellations, and when possible the reason, of sea and inland waterways passenger services
|-
|LOS 4-8
|Cancellations, and when possible the reason, of regular bus and coach services with a scheduled distance of 250 km or more
|-
|LOS 4-9
|Cancellations, and when possible the reason, of flights
|-
|LOS 4-10
|'''d. Information on parking tariffs'''
|}

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

{| class="wikitable" style="width:70%"
|-
! width="80px" |Data Categories

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

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

{| class="wikitable" style="width:70%"
|-
! width="80px" |Data Categories
! width="80px" style="text-align:center " |EPIP
! width="80px" | AU
! width="80px" |AT
! width="80px" |ΒΕ
! width="80px" |HR
! width="80px" |DK
! width="80px" |FR
! width="80px" |IT
! width="80px" |NL
! width="150px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |PT
! width="80px" |SI
! width="80px" |GB
|-
|[[#Data categories|LOS 2-1]]
|
|
|
|
| style="text-align:center;" |✅
|
| style="text-align:center;" |for off-street only
| style="text-align:center " |✅
|
|
|
| |
|
|-
|[[#Data categories|LOS 2-2]]||
| ||
|
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅||
|-
|[[#Data categories|LOS 2-3]]
|
|
|
|
| style="text-align:center " |✅
|
|
| style="text-align:center " |✅
|
|
|
|
|
|-
|[[#Data categories|LOS 2-4]]||
| ||
|
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " | ✅||
|-
|[[#Data categories|LOS 2-5]]||
| ||
|
| style="text-align:center " |✅|| style="text-align:center " |✅
| style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅||
|-
|[[#Data categories|LOS 2-6]]||
| ||
|
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |in off-street car parks only|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅
|
|-
|[[#Data categories|LOS 2-7]]
|
|
|
|
| style="text-align:center " |✅
|
|
| style="text-align:center " |✅
|
|
|
|
|
|-
|[[#Data categories|LOS 2-8]]||
| ||
|
| style="text-align:center " |✅|| || style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅||
|-
|[[#Data categories|LOS 2-9]]
|
|
|
|
| style="text-align:center " |✅
|
| style="text-align:center " |✅
| style="text-align:center " |✅
|
| style="text-align:center " | ✅
|
| style="text-align:center " |✅
|
|-
|[[#Data categories|LOS 2-10]]||
| style="text-align:center;" |✅||
|
| || || style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " | ✅|| style="text-align:center " |✅
|-
|[[#Data categories|LOS 2-11]]||
| style="text-align:center;" |✅||
| style="text-align:center " |✅
| || || style="text-align:center " | ✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅|| style="text-align:center " |✅
|-
|[[#Data categories|LOS 2-12]]||
| ||
|
| || || style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅|| style="text-align:center " | ✅
|-
|[[#Data categories|LOS 2-13]]||
| ||
| style="text-align:center " |✅
| || style="text-align:center " |✅|| style="text-align:center " | ✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || style="text-align:center " |✅|| style="text-align:center " |✅
|-
|}

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

{| class="wikitable" style="width:70%"
|-
! width="80px" |Data Categories
! width="80px" style="text-align:center " |EPIP
! width="80px" |AU
! width="80px" |AT
! width="80px" |BE
! width="80px" |HR
! width="80px" |DK
! width="80px" |FR
! width="80px" |IT
! width="80px" |NL
! width="150px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |PT
! width="80px" |SI
! width="80px" |GB
|-
|[[#Data categories|LOS 3-1]]||
| ||
| style="text-align:center " |✅

| style="text-align:center " | ✅|| || style="text-align:center " |✅ || style="text-align:center " |✅|| || style="text-align:center " |✅|| || || style="text-align:center " | ✅
|-
|[[#Data categories|LOS 3-2]]||
| ||
|
| style="text-align:center " |✅|| || style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || || style="text-align:center " |✅
|-
|[[#Data categories|LOS 3-3]]||
| ||
|
| || || style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || || style="text-align:center " |✅
|-
|[[#Data categories|LOS 3-4]]
|
|
|
|
|
|
| style="text-align:center;" |✅
| style="text-align:center " |✅
|
|
|
|
|
|-
|[[#Data categories|LOS 3-5]]
|
|
|
|
|
|
| style="text-align:center;" |✅
|
|
|
|
|
|
|-
|[[#Data categories|LOS 3-6]]
|
|
|
|
|
|
| style="text-align:center;" |✅
|
|
|
|
|
|
|-
|[[#Data categories|LOS 3-7]]||
| ||
|
| || || || || || style="text-align:center " |✅|| || ||
|-
|[[#Data categories|LOS 3-8]]||
| ||
|
| || || style="text-align:center;" |✅|| || || style="text-align:center " |✅|| || ||
|-
|[[#Data categories|LOS 3-9]]||
| ||
|
| || || style="text-align:center;" |✅|| || || style="text-align:center " |✅|| || ||
|-
|[[#Data categories|LOS 3-10]]||
| ||
|
| || || || || || style="text-align:center " |✅|| || ||
|-
|}

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

⚠️ If you believe that your use cases are resolved in an existing profile, it is highly recommended to '''adopt an existing solution''' and cooperate with the corresponding entity. You will save resources while you will ensure that your profile is interoperable.

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

=SIRI National profiles inventory 🌐=

National profiles are specified to cover the national needs. To help implementation, DATA4PT is also in process of delivering SIRI EU minimum profile, in collaboration with relevant CEN group. DATA4PT has prepared a table with the currently available SIRI national profiles, including an overview of data categories that are currently covered. For data categories relevant to static data check the [NeTEx Profiles Inventory https://data4pt.org/w/index.php?title=NeTEX#NeTEx_national_and_EU_minimum_profiles_inventory].

==Published profiles==

{| class="wikitable" style="width : 50%"
|-
!Profile Name!!Status/
Availability
!EU Minimum profile based*!!EU Minimum SIRI profile compatible** !!Documentation
|-
|Australia - Victoria (AU)
|Specified but not yet in operation
| style="text-align:center " |✅
| style="text-align:center " |✅
|
|-
|Croatia (HR)
|Using an existing profile
|
| style="text-align:center " |✅
|
|-
|France (FR)||Specified and in use
| style="text-align:center " |✅|| style="text-align:center;" | ||[https://normes.transport.data.gouv.fr/normes/siri/profil-france/ French SIRI profile]
|-
|Italy (IT)
| Specified and in use
| style="text-align:center " |✅
|
|[https://github.com/5Tsrl/siri-italian-profile/tree/main/Linee%20guida Italian SIRI profile]
|-
|Netherlands (NL)||Specified but not yet in operation
| || style="text-align:center;" |✅||
|-
|Nordic (Norway, Sweden, Finland, Denmark)|| Specified and in use
| || style="text-align:center;" |✅||[https://enturas.atlassian.net/wiki/spaces/PUBLIC/pages/637370420/Nordic+SIRI+Profile Nordic SIRI profile]
|-
|UK (GB) ||Specified and in use
| || style="text-align:center;" |✅||
|-
|}
<nowiki>*</nowiki>Profiles of this category have been specified based on EU Minimum profile and are based on XML technology as EU profiles.

<nowiki>**</nowiki> Profiles of this category have been specified either before the definition of EU Minimum profile, but they have been used to define the EU one, and/or after EU profiles and need conversion or adaptation to be interoperable.
==Data categories==

''Data categories are identified based on [https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex%3A32024R0490 MMTIS EU Regulation 490/2024]''
{| class="mw-collapsible mw-collapsed wikitable" style="width : 60%"
|+ style="white-space:nowrap; border:1px solid; padding:3px;" |Data categories table.
|-
!Level of service (LOS)!!Types of the dynamic travel and traffic data
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Dynamic data - Level of service 1 (LOS 1 )'''
|-
| colspan="2" |'''a. Passing times, trip plans and auxiliary information'''
|-
| LOS 1-1||Disruptions, such as network closures and/or diversions, and when possible, the reason
|-
|LOS 1-2||Real-time status information, such as estimated departure and arrival times of services, delays, cancellations, guaranteed connections monitoring
|-
|LOS 1-3||Status of access node features (including dynamic platform information, operational lifts/escalators, closed entrances and exit locations) – for scheduled transport
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Dynamic data - Level of service 2 (LOS 2)'''
|-
|LOS 2-1||'''a. Information service on parking tariffs – for transport on demand and personal transport'''
|-
| colspan="2" |'''b. Availability check and location – for transport on demand and personal transport where relevant'''
|-
|LOS 2-2||Car-sharing availability and location, bike-sharing availability and location, scooter-sharing availability and location, and other vehicle-sharing availability and location
|-
|LOS 2-3||Car parking spaces available (on and off-street)
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Dynamic data - Level of service 3 (LOS 3''')
|-
|LOS 3-1|| Occupancy information of the vehicle – for scheduled transport and transport on demand where relevant
|}

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

{| class="wikitable" style="width : 30%"
|-
!Data Categories
! width="80px" |AU
! width="80px" |HR
! width="80px" |FR
! width="80px" |IT
! width="80px" |NL
! width="300px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |GB
|-
|[[#Data categories|LOS 1-1]]
| style="text-align:center " |✅|| || style="text-align:center " |✅
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅ dynamic platform is included || style="text-align:center " |✅
|-
|[[#Data categories|LOS 1-2]]
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅ dynamic platform is included || style="text-align:center " |✅
|-
|[[#Data categories|LOS 1-3]]
| || || style="text-align:center " |✅
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅ dynamic platform is included || style="text-align:center " |
|-
|}

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

{| class="wikitable" style="width : 30%"
|-
!Data Categories
! width="80px" |AU
! width="80px" |HR
! width="80px" | FR
! width="80px" |IT
! width="80px" |NL
! width="300px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |GB
|-
|[[#Data categories|LOS 2-1]]
|
|
|
|
|
|
|
|-
|[[#Data categories|LOS 2-2]]
| || || style="text-align:center " |only for car sharing and bike sharing
| style="text-align:center " |✅|| || style="text-align:center " |✅||
|-
|[[#Data categories|LOS 2-3]]
| || || style="text-align:center " |off-street only
| style="text-align:center " |✅|| || style="text-align:center " |✅||
|-
|}

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

{| class="wikitable" style="width : 30%"
|-
!Data Categories
! width="80px" |AU
! width="80px" |FR
! width="80px" |IT
! width="80px" |NL
! width="300px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |GB
|-
|[[#Data categories|LOS 3-1]]
| style="text-align:center " |✅
| style="text-align:center " |✅
| style="text-align:center " |✅
|
|
|
|}

⚠️ If you believe that your use cases are resolved in an existing profile, it is highly recommended to '''adopt an existing solution''' and cooperate with the corresponding entity. You will save resources while you will ensure that your profile is interoperable.

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

=Implementations per Country=
In progress

France

2024-09-27T09:24:35Z

Anonymous: creation of france page

== Overview in the National Level ==

=== Current Situation ===

* '''Mass transit''': 114 datasets in NeTEx – French Profile format are available (excluding tariff and accessibility data) out of 421 total mass transit datasets.
* '''Mass transit (Real-time)''': 25 SIRI datasets are available compared to 159 GTFS-RT datasets.
* '''Pedestrian accessibility''': 2 datasets in NeTEx – French Profile format have been provided.

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

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

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

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

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

== Use cases ==

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

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

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

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

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

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

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

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

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

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

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

Italy

2024-09-25T12:24:01Z

Anonymous: changed namespace

{{DISPLAYTITLE:Country:Italy}}

= Overview in the National Level =

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

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

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

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

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

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

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

Main data categories exchanged are:

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

* Timetables
* Validity calendars
* Lines
* Transport Operators

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

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

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

Main data categories exchanged are:

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

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

Main data categories exchanged are:

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

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

Main data categories exchanged are:

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

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

Main data categories exchanged are:

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

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

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

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

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

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

= Use cases =

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

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

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

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

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

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

=== Outcome ===
To be completed.

{{DEFAULTSORT:Country:Italy}}

Slovenia

2024-09-25T09:22:01Z

Anonymous: creation of slovenia page

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

File:Digital mobility data ecosystem at NCUP Slovenia.png

2024-09-25T09:19:44Z

Anonymous:

Digital mobility data ecosystem at NCUP

File:Digital mobility data ecosystem at NCUP.png

2024-09-25T09:17:19Z

Anonymous:

Digital mobility data ecosystem at NCUP

Belgium

2024-09-20T08:41:55Z

Anonymous: added belgium input

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

Australia

2024-09-19T08:52:43Z

Anonymous: added australian input

== Overview in the National Level ==
The Department of Transport and Planning, located in the state of Victoria, Australia, is working on implementing NeTEx/GTFS for static data and SIRI/GTFS-R for real-time data. Currently, efforts are focused on obtaining endorsement for the technical specification documents related to NeTEx, GTFS, SIRI, and GTFS-R.

In addition, the process of formalizing data change notifications to operators for each of these standards is underway, and the data information requirements document is being finalized. This document will define the high-level roles and responsibilities between operators and the State.

== Use cases ==

=== Description ===
The state of Victoria has several modes of public transport which include train, tram and bus. They run in metropolitan areas of the city of Melbourne. Also, in regional towns in the state of Victoria.

To date, a vast majority of contracts that have been entered into between the Victoria State Government either are missing data exchange clauses or are limited in their application and are only suitable for single use cases. This has resulted in limited and inconsistent quality of data.

To ensure the Victoria State Government has an endorsed position relating to Public Transport (PT) data exchange standards governing how data is exchanged across the public transport eco-system.

=== Architecture ===

==== Future state ====
The diagram below is the planned target architecture for static and real-time public transport data.
[[File:Australia architecture.jpg|center|thumb|503x503px|Planned target architecture in Australia]]

=== Use cases ===
The State Government are working with Operators to embed these data standards into the contractual agreements for modes such as train, tram and bus.

The Department has managed to export NeTEx files from their development environments using the current timetable management system.

GTFS data is currently being published out to third party apps like Google maps, and to the open data market. The Department are currently adding new data configurations based on MobilityData’s framework.

With SIRI and GTFS-R data they are currently being developed in a Proof of Concept (PoC).

The State Government is collaborating with Operators to incorporate these data standards into contractual agreements for various transport modes, including trains, trams, and buses.

In parallel, the Department has successfully exported NeTEx files from their development environments using the current timetable management system. GTFS data is being published to third-party apps like Google Maps and the open data market, with new configurations being added based on MobilityData’s framework.

Additionally, SIRI and GTFS-R data are currently being developed as part of a Proof of Concept (PoC).

=== Outcome ===
The expected results are a richer, consistent, and more accurate quality of public transport data.

File:Australia architecture.jpg

2024-09-19T08:48:38Z

Anonymous:

Australia architecture

National Implementations

2024-09-19T06:57:43Z

Anonymous:

= NeTEx national profiles inventory 🌐 =

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

== Published profiles ==

{| class="wikitable" style="width : 60%"
|-
! width="150px"| Profile Name
!Status/
Availability
! width="100px" | NeTEx EPIP Based* !! width="100px" | NeTEx EPIP Compatible**
! width="300px" | Documentation
|-
| Australia - Victoria (AU)
|Specified but not yet in operation
| style="text-align:center;" |✅
| style="text-align:center;" |✅
|
|-
|Austria (AT)
|Specified but not yet in operation|| style="text-align:center;" |✅|| ||[https://mobilitaetsverbuende.atlassian.net/wiki/spaces/NET/overview Austrian profile]
|-
|Belgium (BE)
|Specified but not yet in operation|| style="text-align:center;" |✅|| ||[https://github.com/Informatievlaanderen/OSLOthema-mobiliteitDienstregelingEnPlanning GitHUb]
[https://purl.eu/doc/applicationprofile/netex-belgium/timetables-ap/ AP-Timetables]

[https://purl.eu/doc/applicationprofile/netex-belgium/stopplaces-ap/ AP-Stops]

[https://purl.eu/doc/applicationprofile/netex-belgium/vehiclescheduling-ap/ AP-Vehicle Scheduling]

[https://purl.eu/ns/mobility/timetables-and-planning/ AP-TimetablesAndPlanning]

[https://github.com/Informatievlaanderen/OSLOthema-mobiliteitDienstregelingEnPlanning/tree/master/resources/DataExamples Data examples]
|-
|Croatia (HR)
|Specified and in use
| style="text-align:center;" | ✅
| style="text-align:center;" |✅
|[https://www.promet-info.hr/en NPT - Croatian NAP]
|-
|Denmark (DK)
|Specified but not yet in operation|| style="text-align:center;" |✅|| ||[https://www.trafikstyrelsen.dk/Media/638013312835439194/Vejledning%20om%20brug%20af%20NeTEx.pdf Denmark profile] - [https://www.trafikstyrelsen.dk/arbejdsomraader/kollektiv-trafik/statistik-og-data/krav-til-udstilling-af-data-til-rejseplanlaegning NAP in Denmark]
|-
|France (FR)
|Specified and in use|| || style="text-align:center;" |✅||[http://www.normes-donnees-tc.org/format-dechange/donnees-theoriques/netex/ French profile] - [http://www.normes-donnees-tc.org/wp-content/uploads/2021/01/Profil-NeTEx-elements-communsF-v2.2.pdf Common profil] - [http://www.normes-donnees-tc.org/wp-content/uploads/2014/05/NF_Profil_NeTEx_pour_les_arrets-_F-_-_v2.pdf Stop Profile] - [http://www.normes-donnees-tc.org/wp-content/uploads/2019/11/NF_Profil-NeTEx-pour-les-R%C3%A9seauxF-v2.1.pdf Network Profil] - [http://www.normes-donnees-tc.org/wp-content/uploads/2019/11/NF+Profil-NeTEx-pour-les-HorairesF-v2.1.pdf Timetable profile] - [http://www.normes-donnees-tc.org/wp-content/uploads/2021/11/NF_Profil-NeTEx-pour-les-TarifsF-v1.2.pdf Fare Profile] - [http://www.normes-donnees-tc.org/wp-content/uploads/2021/10/NF_Profil-NeTEx-pour-les-ParkingsF-v1.2a.pdf Parking profile] - [http://www.normes-donnees-tc.org/wp-content/uploads/2021/01/Profil-NeTEx-pour-laccessibiliteF-v2.2.pdf Accessibility Profile]
|-
|Italy (IT)
|Specified and in use|| style="text-align:center;" |✅ ||
|[https://github.com/5Tsrl/netex-italian-profile/tree/main/Linee%20guida Italian profile]
|-
|Netherlands (NL)
|Specified but not yet in operation|| style="text-align:center;" |✅|| ||[https://bison.dova.nu/standaarden/nederlands-netex-profiel Netherlands profile] - [https://bison.dova.nu/sites/default/files/bison_prijzen_producten_en_tarieven_v8.1.3.0_release.pdf Bison Fares]
|-
|Nordic (Norway, Sweden, Finland, Denmark)
|Specified and in use|| || style="text-align:center;" |✅||[https://enturas.atlassian.net/wiki/spaces/PUBLIC/pages/728891481/Nordic+NeTEx+Profile Nordic profile]
|-
|Portugal (PT)
|Specified and in use|| || ||[https://ptprofiles.azurewebsites.net/netex-profile Portuguese profile]
|-
|Slovenija (SI)
|Specified but not yet in operation|| || style="text-align:center " |✅||[https://www.nap.si/_resources/profiles/NeTEx_SI_Profile_v2.pdf Slovenian profile]
|-
|UK (GB)
|Specified and in use|| || style="text-align:center " |✅||[http://netex.uk/farexchange/ UK profile] - [http://netex.uk/farexchange/doc/uk_profile/DfT-NeTEx-1-Fares-Intro-2019.06.17-v0.09.pdf Introduction] - [http://netex.uk/farexchange/doc/uk_profile/DfT-NeTEx-2-Base_Spec-2019.06.30-v0.14.pdf Stop and Timetables] - [http://netex.uk/farexchange/doc/uk_profile/DfT-NeTEx-3-Fares_Spec-2019.06.17-v0.17.pdf Fares]
|-
|Ireland (IE)
|Specified and in use|| || ||[https://netex.ie/ Irish profile] - [http://netex.uk/netexie/doc/EIRE_NP/NTA-NeTEx-1-Spec-2020.08.12-v0.22.pdf Profile Elements] - [http://netex.uk/netexie/doc/EIRE_NP/NTA-NeTEx-2-Mappings-2020.08.06-v0.22.pdf Profile Data Mappings]
|-
|Czech Republic (CZ)
| Specified but not yet in operation
| style="text-align:center " |✅
|
|
|}
<nowiki>*</nowiki>Profiles of this category have been specified based on EU Minimum profile and are based on XML technology as EU profiles.

<nowiki>**</nowiki> Profiles of this category have been specified either before the definition of EU Minimum profile, but they have been used to define the EU one, and/or after EU profiles and need conversion or adaptation to be interoperable.
==Data categories==

''Data categories are identified based on [https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex%3A32024R0490 MMTIS EU Regulation 490/2024]''
{| class="mw-collapsible mw-collapsed wikitable" style="width:70%"
|+ style="white-space:nowrap; border:1px solid; padding:3px;" | Data categories table.
|-
!Level of service (LOS)!!Static data
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Static data - Level of service 1 (LOS 1 )'''
|-
| colspan="2" |'''a. Location search (origin/destination)'''
|-
|LOS 1-1 ||Address identifiers (building number, street name, postcode)
|-
|LOS 1-2||Topographic places (city, town, village, suburb, administrative unit)
|-
|LOS 1-3||Points of interest (related to transport information) to which people may wish to travel
|-
|LOS 1-4||'''b. Trip plans: operational calendar, mapping day types to calendar dates'''
|-
| colspan="2" |'''c. Location search (access nodes) – for scheduled transport and transport on demand where relevant'''
|-
|LOS 1-5
|Identified access nodes
|-
|LOS 1-6||Geometry/map layout structure of access nodes
|-
| colspan="2" |'''d. Trip plan computation – for scheduled transport and transport on demand where relevant'''
|-
|LOS 1-7||Connection where interchanges may be made
|-
|LOS 1-8
|Default transfer times at interchanges
|-
|LOS 1-9||Network topology and routes/lines (topology)
|-
|LOS 1-10||Transport operators
|-
|LOS 1-11|| Timetables
|-
|LOS 1-12||Planned interchanges between guaranteed scheduled services
|-
| LOS 1-13||Hours of operation
|-
|LOS 1-14
|Facilities of access nodes (including platform information, help desk/information points, ticket booths, lifts/stairs, entrances and exit locations)
|-
|LOS 1-15||Vehicles, including their accessibility (such as low floor, wheelchair accessible, pram accessible) and accessibility of on-board services (such as toilets)
|-
|LOS 1-16||Accessibility of access nodes, and paths within an interchange (such as existence of lifts, escalators)
|-
|LOS 1-17||Existence of assistance services (such as existence of on-site assistance)
|-
| colspan="2" |'''e. Trip plan computation'''
|-
|LOS 1-18||Road network (including segregated lanes for bus/taxi)
|-
|LOS 1-19||Cycle network (cycle tracks, cycle lanes, bus-and-cycle lanes, on-road shared with vehicles, on-path shared with pedestrians)
|-
|LOS 1-20||Pedestrian network and accessibility facilities
|-
| || Framework data
|-
|
|
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Static data - Level of service 2 (LOS 2)'''
|-
| colspan="2" |'''a. Location search – for transport on demand and personal transport'''
|-
|LOS 2-1
| Location of parking places (on and off-street), including accessible parking places for persons with disabilities and persons with reduced mobility
|-
|LOS 2-2||Park & Ride stops
|-
|LOS 2-3
|Park & Drive stops
|-
|LOS 2-4||Bike sharing stations
|-
|LOS 2-5||Car-sharing stations
|-
|LOS 2-6
|Secure bike parking (such as locked bike garages)
|-
|LOS 2-7
| Scooter parking zones
|-
| colspan="2" |'''b. Information service'''
|-
|LOS 2-8|| Where and how to buy tickets for scheduled transport, including retail channels, fulfilment methods, payment methods
|-
|LOS 2-9||Where and how to pay for parking, including retail channels, fulfilment methods, payment methods
|-
| colspan="2" |'''c. Auxiliary information – for scheduled transport and transport on demand where relevant'''
|-
|LOS 2-10||Basic common standard fares
- fare network data (fare zones/stops and fare stages)

- standard fare structures (point to point including daily and weekly fares, zonal fares, flat fares)
|-
| LOS 2-11||Vehicle facilities such as classes of carriage, on-board Wi-Fi.
|-
| ||
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Static data - Level of service 3 (LOS 3''')
|-
| colspan="2" |'''a. Detailed common standard and special fare query – for scheduled transport and transport on demand where relevant'''
|-
|LOS 3-1||Passenger classes (classes of passenger such as adult, child, senior, student, military/veteran, passenger with disability and passenger with reduced mobility, and qualifying conditions, and classes of travel)
|-
|LOS 3-2||Common fare products (access rights such as zone/point-to-point including daily and weekly tickets/single/return, eligibility of access, basic usage conditions such as validity period/operator/time of travel/interchanging, standard point-to-point fares prices for different point-to-point pairs including daily and weekly fares/zonal fare prices/flat fare prices)
|-
|LOS 3-3||Special fare products (offers with additional special conditions such as promotional fares, group fares, season passes, aggregated products combining different products, and add-on products such as parking and travel, minimum stay)
|-
|LOS 3-4 ||Basic commercial conditions such as refunding, replacing, exchanging or transferring
|-
|LOS 3-5||Basic booking conditions such as purchase windows, validity periods, routing restrictions zonal sequence fares, minimum stay
|-
|LOS 3-6||'''b. Information service – for transport on demand: how to book demand-responsive transport services, including retail channels, fulfilment methods, payment methods'''
|-
| colspan="2" |'''c. Trip plans'''
|-
| LOS 3-7||Detailed cycle network attributes (surface quality, side-by-side cycling, shared surface, on/off road, scenic route, “walk only”, turn or access restrictions, e.g. against flow of traffic)
|-
|LOS 3-8 || Parameters needed to calculate an environmental factor such as greenhouse gas emissions per vehicle type or passenger mile or per distance walked
|-
|LOS 3-9||Parameters needed to calculate fuel consumption of conventional and alternative fuels
|-
|LOS 3-10
|'''d. Trip plan computation: estimated travel times by day type and time-band by transport mode/combination of transport mode'''
|-
| colspan="2" |
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Static data - Level of service 4 (LOS 4 )'''
|-
|LOS 4-1
|'''a. Historic travel and traffic data on delays – for scheduled transport and transport on demand where relevant'''
|-
| colspan="2" |'''b. Observed data on delays and passing time – for scheduled transport'''
|-
|LOS 4-2
|Length of, and when possible the reason for, delays of at least 60 minutes for rail passenger services (in accordance with Article 19 of Regulation (EU) 2021/782)
|-
|LOS 4-3
|Length of, and when possible the reason for, delays in departure of more than 90 minutes for sea and inland waterways passenger services (in accordance with Article 18 of Regulation (EU) No 1177/2010)
|-
|LOS 4-4
| Length of, and when possible the reason for, delays in departure from a terminal of more than 120 minutes for regular bus and coach passenger services with a scheduled distance of 250 km or more (in accordance with Article 19 of Regulation (EU) No 181/2011)
|-
|LOS 4-5
| Length of, and when possible the reason for, flight delays at departure of at least 120 minutes; and flight delays at arrival of at least 180 minutes (in accordance with Articles 5 and 6 of Regulation (EC) No 261/2004)
|-
| colspan="2" |'''c. Observed data on cancellations – for scheduled transport'''
|-
|LOS 4-6
|Cancellations, and when possible the reason, of rail passenger services
|-
|LOS 4-7
| Cancellations, and when possible the reason, of sea and inland waterways passenger services
|-
| LOS 4-8
|Cancellations, and when possible the reason, of regular bus and coach services with a scheduled distance of 250 km or more
|-
|LOS 4-9
|Cancellations, and when possible the reason, of flights
|-
|LOS 4-10
|'''d. Information on parking tariffs'''
|}

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

{| class="wikitable" style="width:70%"
|-
! width="80px" |Data Categories

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

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

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

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

{| class="wikitable" style="width:70%"
|-
! width="80px" |Data Categories
! width="80px" style="text-align:center " |EPIP
! width="80px" |AU
! width="80px" |AT
! width="80px" |BE
! width="80px" |HR
! width="80px" |DK
! width="80px" |FR
! width="80px" |IT
! width="80px" |NL
! width="150px" | Nordic (SE, NOR, DK, FIN)
! width="80px" |PT
! width="80px" |SI
! width="80px" |GB
|-
|[[#Data categories|LOS 3-1]]||
| ||
| style="text-align:center " |✅

| style="text-align:center " |✅|| || style="text-align:center " |✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || || style="text-align:center " |✅
|-
|[[#Data categories|LOS 3-2]]||
| ||
|
| style="text-align:center " |✅|| || style="text-align:center " | ✅|| style="text-align:center " |✅|| || style="text-align:center " |✅|| || || style="text-align:center " |✅
|-
|[[#Data categories|LOS 3-3]]||
| ||
|
| || || style="text-align:center " |✅ || style="text-align:center " |✅|| || style="text-align:center " |✅|| || || style="text-align:center " |✅
|-
|[[#Data categories|LOS 3-4]]
|
|
|
|
|
|
|
| style="text-align:center " |✅
|
|
|
|
|
|-
|[[#Data categories|LOS 3-5]]
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
|[[#Data categories|LOS 3-6]]
|
|
|
|
|
|
|
|
|
|
|
|
|
|-
|[[#Data categories|LOS 3-7]]||
| ||
|
| || || || || || style="text-align:center " |✅|| || ||
|-
|[[#Data categories|LOS 3-8]]||
| ||
|
| || || || || || style="text-align:center " |✅|| || ||
|-
|[[#Data categories|LOS 3-9]]||
| ||
|
| || || || || || style="text-align:center " |✅|| || ||
|-
|[[#Data categories|LOS 3-10]]||
| ||
|
| || || || || || style="text-align:center " |✅|| || ||
|-
|}

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

⚠️ If you believe that your use cases are resolved in an existing profile, it is highly recommended to '''adopt an existing solution''' and cooperate with the corresponding entity. You will save resources while you will ensure that your profile is interoperable.

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

=SIRI National profiles inventory 🌐=

National profiles are specified to cover the national needs. To help implementation, DATA4PT is also in process of delivering SIRI EU minimum profile, in collaboration with relevant CEN group. DATA4PT has prepared a table with the currently available SIRI national profiles, including an overview of data categories that are currently covered. For data categories relevant to static data check the [NeTEx Profiles Inventory https://data4pt.org/w/index.php?title=NeTEX#NeTEx_national_and_EU_minimum_profiles_inventory].

==Published profiles==

{| class="wikitable" style="width : 50%"
|-
! Profile Name!!Status/
Availability
!EU Minimum profile based*!!EU Minimum SIRI profile compatible**!!Documentation
|-
|Australia - Victoria (AU)
|Specified but not yet in operation
| style="text-align:center " |✅
| style="text-align:center " |✅
|
|-
|Croatia (HR)
| Using an existing profile
|
| style="text-align:center " | ✅
|
|-
|France (FR)||In use in numerous cities and regions
| || style="text-align:center;" |✅ ||
|-
|Italy (IT)
|Specified and in use
| style="text-align:center " | ✅
|
|[https://github.com/5Tsrl/siri-italian-profile/tree/main/Linee%20guida Italian SIRI profile]
|-
|Netherlands (NL)||Specified but not yet in operation
| || style="text-align:center;" |✅||
|-
|Nordic (Norway, Sweden, Finland, Denmark)||Specified and in use
| || style="text-align:center;" |✅||[https://enturas.atlassian.net/wiki/spaces/PUBLIC/pages/637370420/Nordic+SIRI+Profile Nordic SIRI profile]
|-
|UK (GB)||Specified and in use
| || style="text-align:center;" |✅||
|-
|}
<nowiki>*</nowiki>Profiles of this category have been specified based on EU Minimum profile and are based on XML technology as EU profiles.

<nowiki>**</nowiki> Profiles of this category have been specified either before the definition of EU Minimum profile, but they have been used to define the EU one, and/or after EU profiles and need conversion or adaptation to be interoperable.
==Data categories==

''Data categories are identified based on [https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex%3A32024R0490 MMTIS EU Regulation 490/2024]''
{| class="mw-collapsible mw-collapsed wikitable" style="width : 60%"
|+ style="white-space:nowrap; border:1px solid; padding:3px;" |Data categories table.
|-
!Level of service (LOS)!!Types of the dynamic travel and traffic data
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Dynamic data - Level of service 1 (LOS 1 )'''
|-
| colspan="2" |'''a. Passing times, trip plans and auxiliary information'''
|-
|LOS 1-1||Disruptions, such as network closures and/or diversions, and when possible, the reason
|-
| LOS 1-2||Real-time status information, such as estimated departure and arrival times of services, delays, cancellations, guaranteed connections monitoring
|-
|LOS 1-3||Status of access node features (including dynamic platform information, operational lifts/escalators, closed entrances and exit locations) – for scheduled transport
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Dynamic data - Level of service 2 (LOS 2)'''
|-
|LOS 2-1||'''a. Information service on parking tariffs – for transport on demand and personal transport'''
|-
| colspan="2" |'''b. Availability check and location – for transport on demand and personal transport where relevant'''
|-
|LOS 2-2||Car-sharing availability and location, bike-sharing availability and location, scooter-sharing availability and location, and other vehicle-sharing availability and location
|-
| LOS 2-3||Car parking spaces available (on and off-street)
|-
| colspan="2" style="text-align:center " bgcolor="#A6C9EC" |'''Dynamic data - Level of service 3 (LOS 3''')
|-
|LOS 3-1||Occupancy information of the vehicle – for scheduled transport and transport on demand where relevant
|}

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

{| class="wikitable" style="width : 30%"
|-
!Data Categories
! width="80px" |AU
! width="80px" |HR
! width="80px" |FR
! width="80px" |IT
! width="80px" | NL
! width="300px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |GB
|-
|[[#Data categories|LOS 1-1]]
| style="text-align:center " |✅|| || style="text-align:center " |✅
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅ dynamic platform is included|| style="text-align:center " |✅
|-
|[[#Data categories|LOS 1-2]]
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅
| style="text-align:center " |✅|| style="text-align:center " |✅|| style="text-align:center " |✅ dynamic platform is included|| style="text-align:center " |✅
|-
|[[#Data categories|LOS 1-3]]
| || || style="text-align:center " |✅
| style="text-align:center " |✅ || style="text-align:center " |✅|| style="text-align:center " |✅ dynamic platform is included|| style="text-align:center " |
|-
|}

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

{| class="wikitable" style="width : 30%"
|-
!Data Categories
! width="80px" |AU
! width="80px" | HR
! width="80px" |FR
! width="80px" |IT
! width="80px" | NL
! width="300px" |Nordic (SE, NOR, DK, FIN)
! width="80px" | GB
|-
|[[#Data categories|LOS 2-1]]
|
|
|
|
|
|
|
|-
|[[#Data categories|LOS 2-2]]
| || || style="text-align:center " |✅
| style="text-align:center " |✅|| || style="text-align:center " |✅||
|-
|[[#Data categories|LOS 2-3]]
| || || style="text-align:center " |✅
| style="text-align:center " |✅|| || style="text-align:center " |✅||
|-
|}

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

{| class="wikitable" style="width : 30%"
|-
!Data Categories
! width="80px" |AU
! width="80px" |FR
! width="80px" |IT
! width="80px" |NL
! width="300px" |Nordic (SE, NOR, DK, FIN)
! width="80px" |GB
|-
|[[#Data categories|LOS 3-1]]
| style="text-align:center " |✅
|
| style="text-align:center " |✅
|
|
|
|}

⚠️ If you believe that your use cases are resolved in an existing profile, it is highly recommended to '''adopt an existing solution''' and cooperate with the corresponding entity. You will save resources while you will ensure that your profile is interoperable.

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

=Implementations per Country=
In progress

Austria

2024-09-17T14:15:29Z

Anonymous:

== Overview in the National Level ==
For many implementations, the VDV standards (incl. VDV736) are preferred over other options, for them being tailored to the regional specifics.

[https://data.mobilitaetsverbuende.at/en MVO] publishes NeTEx data and preferably uses VDV736 (SIRI-SX) for situation information.

== Use cases ==

=== Description ===
For the purposes of operating and maintaining customer information channels (such as the WienMobil app, digital signage and departure boards, the website, on-board information, etc.), Wiener Linien has introduced an API gateway as a middleware component. This ensures that all customer-facing channels source their information from a single system (the API gateway), providing consistent information across all available platforms.

=== Architecture ===
Since the data sources connected to the API Gateway may provide different formats, or the data required for "customer information" may be scattered across various independent sources, Wiener Linien has implemented SIRI and/or NeTEx as the canonical data formats within the API Gateway. This approach facilitates the consolidation of information within the API Gateway, ensuring it serves as the single point of truth for all customer information channels.

The API Gateway can provide customer information channels with data in the canonical format (SIRI or NeTEx) or transform the data into any format required by the consuming system.

For specific use cases, the data can be enriched before being provided to the customer information channels:

* Automatic translation of SIRI-SX Situation Descriptions
* Generation of sign language videos
* Creation of workload or delay estimates using machine learning

=== Use cases ===
The following use cases illustrate how Wiener Linien utilizes the API Gateway and data standards to operate and maintain customer information channels:

FIS+ involves on-board information screens in the latest subway rolling stock (X-Wagen). The necessary data, including station departures and current situations, is retrieved from internal data sources, transformed into the SIRI-SM and SIRI-SX canonical formats, and then converted into a proprietary format that contains only the most relevant information. This format is extremely lightweight due to limited bandwidth, and the information is subsequently forwarded to the rolling stock.

For the WienMobil App and WienMobil Monitor, the relevant information (station departures and current situations) is pulled from multiple data sources, including external sources from other transport operators like ÖBB. This data is transformed into the canonical SIRI-SM and SIRI-SX formats, cached within the API Gateway, and then delivered on demand to the app backend. The format is optimized by omitting redundant overhead to improve efficiency.

The e-Paper timetable follows a similar process. Station departure and current situation data are pulled from internal data sources, transformed into SIRI-SM and SIRI-SX, cached within the API Gateway, and sent to the e-Paper backend as needed.

For the generation of sign language videos, current situation data is regularly retrieved from internal sources, transformed into SIRI-SX, and sent to the SignTime API. SignTime processes the situation descriptions, generating a sign language video for each relevant entry. A link to the video is returned and can be added as a custom field in any subsequent SIRI-SX messages.

In the case of the WienMobil Alexa Skill, the required information (station departures) is sourced from internal and external data sources (such as ÖBB), transformed into SIRI-SM, cached in the API Gateway, and provided on demand to the backend system of the Alexa Skill.

=== Outcome ===
The chosen data standard framework is highly robust, accommodating virtually any use case. However, this flexibility introduces significant complexity, which can be challenging for some colleagues and implementors. Despite this, it is well-suited as a canonical data format for these reasons. With this framework in place, Wiener Linien is well-prepared to meet the requirements of EU Regulation 2017/1926.

Sweden

2024-09-17T14:00:34Z

Anonymous:

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

==Use cases ==

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

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

===Architecture===

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

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

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

Sweden

2024-09-17T14:00:23Z

Anonymous:

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

==Use cases ==

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

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

===Architecture===

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

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

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

Draft:Denmark

2024-09-17T13:58:48Z

Anonymous:

== Overview in the National Level ==
[[File:Map DK.png|thumb|397x397px|Map of Denmark, with a focus on Greater Copenhagen]]

=== NeTEx and SIRI profiles ===
In Denmark, EU profiles for NeTEx and SIRI has been adopted. The implementation follows the European standards to ensure compatibility and data quality for journey planning and real-time information services.

Guidance on the national requirements and best practices is available in Danish through Trafikstyrelsen, the [https://www.trafikstyrelsen.dk/arbejdsomraader/kollektiv-trafik/statistik-og-data/krav-til-udstilling-af-data-til-rejseplanlaegning Danish Civil Aviation and Railway Authority], who is responsible for the implementation of NeTEx, SIRI and NAP on national level. For guidance in English, you can reach out to eudata@trafikstyrelsen.dk.

== Use cases ==
In Denmark two main stakeholders implement NeTEx and SIRI currently:

# '''Movia'''. It is the PTA for buses and (certain) local trains in Greater Copenhagen. Other PTAs in this area are DSB (regional trains and S-trains) and Metro (Copenhagen metro and a tram line under construction).
# '''Rejsekort & Rejseplan A/S'''. It is the company behind the national travel planner and electronic ticketing system in Denmark, which unites all regions and different transport operators into a common system.

=== Description ===

==== Rejsekort & Rejseplan ====
Rejsekort & Rejseplan A/S have used the NeTEx and SIRI standards nationwide, providing comprehensive coverage of the entire public transport network.

The architecture implemented by Rejsekort & Rejseplan A/S relies on centralized data exports from subcontractors IVU Traffic Technologies and HaCon, which supply the necessary data to Rejsekort and Rejseplan. These systems use the NeTEx and SIRI profiles to ensure high compatibility and data consistency. This architecture allows for the effective aggregation of transport data across various operators and regions, supporting both journey planning and real-time passenger information services.

==== Movia ====
Movia is using NeTEx and SIRI as the main interfaces around a new ‘Traffic Management System’ TMS. The delivery of the TMS was tendered and the contract was awarded FARA in 2023 and is expected to be in operation in 2025.

The system will handle all PT bus and local train traffic within Greater Copenhagen and Sealand:

* Number of ServiceJourneys on a workday: ~20 000
* Number of Calls on a workday: ~700 000
* Number of concurrent journeys in rush hour: ~1 000
* Number of active stops (Quays): ~17 000

=== Architecture ===

==== Movia ====
The TMS will consume stops and schedules in NeTEx-format. We use a profile based on the [https://enturas.atlassian.net/wiki/spaces/PUBLIC/pages/728891481/Nordic+NeTEx+Profile Nordic Profile] with minor adaptions.

The system will expose NeTEx as well as SIRI data. NeTEx will be exposed using the Nordic-based profile as well as EPIP.
[[File:Data providers.png|center|thumb|589x589px|TMS solution]]

=== Use cases ===
Currently, there are no active users of NeTEx and SIRI. The national travel planner already provides comprehensive and well-functioning services across the country, and the introduction of these standards has not been able to contribute to any improvement.

=== Outcome ===
Movia is currently using a system based on NOPTIS interfaces. The choice of NeTEx/SIRI for the new system was driven by the fact that NOPTIS is only supported by few suppliers – NeTEx/SIRI are supported by EU, has status as CEN/TS, and are widely supported. We believe that the choice of NeTEx/SIRI has opened the competition with lower price as a result. Moreover, Movia expects that with NeTEx/SIRI, it will be easier to integrate new consumers in the future.

As of now, no significant benefits from the implementation of NeTEx and SIRI have been observed in Denmark.

The largest Danish public transport authority is in the process of implementing NeTEx and SIRI, which may create new opportunities for enhanced data exchange and service improvements in the future. The full potential of these standards, however, has yet to be realized in Denmark.

Draft:Denmark

2024-09-17T13:57:39Z

Anonymous:

== Overview in the National Level ==
[[File:Map DK.png|thumb|397x397px|Map of Denmark, with a focus on Greater Copenhagen]]

=== NeTEx and SIRI profiles ===
In Denmark, EU profiles for NeTEx and SIRI has been adopted. The implementation follows the European standards to ensure compatibility and data quality for journey planning and real-time information services.

Guidance on the national requirements and best practices is available in Danish through Trafikstyrelsen, the [https://www.trafikstyrelsen.dk/arbejdsomraader/kollektiv-trafik/statistik-og-data/krav-til-udstilling-af-data-til-rejseplanlaegning Danish Civil Aviation and Railway Authority], who is responsible for the implementation of NeTEx, SIRI and NAP on national level. For guidance in English, you can reach out to eudata@trafikstyrelsen.dk.

== Use cases ==
In Denmark two main stakeholders implement NeTEx and SIRI currently:

'''Movia''' is the PTA for buses and (certain) local trains in Greater Copenhagen. Other PTAs in this area are DSB (regional trains and S-trains) and Metro (Copenhagen metro and a tram line under construction).

'''Rejsekort & Rejseplan A/S''' is the company behind the national travel planner and electronic ticketing system in Denmark, which unites all regions and different transport operators into a common system.

=== Description ===

==== Rejsekort & Rejseplan ====
Rejsekort & Rejseplan A/S have used the NeTEx and SIRI standards nationwide, providing comprehensive coverage of the entire public transport network.

The architecture implemented by Rejsekort & Rejseplan A/S relies on centralized data exports from subcontractors IVU Traffic Technologies and HaCon, which supply the necessary data to Rejsekort and Rejseplan. These systems use the NeTEx and SIRI profiles to ensure high compatibility and data consistency. This architecture allows for the effective aggregation of transport data across various operators and regions, supporting both journey planning and real-time passenger information services.

==== Movia ====
Movia is using NeTEx and SIRI as the main interfaces around a new ‘Traffic Management System’ TMS. The delivery of the TMS was tendered and the contract was awarded FARA in 2023 and is expected to be in operation in 2025.

The system will handle all PT bus and local train traffic within Greater Copenhagen and Sealand:

* Number of ServiceJourneys on a workday: ~20 000
* Number of Calls on a workday: ~700 000
* Number of concurrent journeys in rush hour: ~1 000
* Number of active stops (Quays): ~17 000

=== Architecture ===

==== Movia ====
The TMS will consume stops and schedules in NeTEx-format. We use a profile based on the [https://enturas.atlassian.net/wiki/spaces/PUBLIC/pages/728891481/Nordic+NeTEx+Profile Nordic Profile] with minor adaptions.

The system will expose NeTEx as well as SIRI data. NeTEx will be exposed using the Nordic-based profile as well as EPIP.
[[File:Data providers.png|center|thumb|589x589px|TMS solution]]

=== Use cases ===
Currently, there are no active users of NeTEx and SIRI. The national travel planner already provides comprehensive and well-functioning services across the country, and the introduction of these standards has not been able to contribute to any improvement.

=== Outcome ===
Movia is currently using a system based on NOPTIS interfaces. The choice of NeTEx/SIRI for the new system was driven by the fact that NOPTIS is only supported by few suppliers – NeTEx/SIRI are supported by EU, has status as CEN/TS, and are widely supported. We believe that the choice of NeTEx/SIRI has opened the competition with lower price as a result. Moreover, Movia expects that with NeTEx/SIRI, it will be easier to integrate new consumers in the future.

As of now, no significant benefits from the implementation of NeTEx and SIRI have been observed in Denmark.

The largest Danish public transport authority is in the process of implementing NeTEx and SIRI, which may create new opportunities for enhanced data exchange and service improvements in the future. The full potential of these standards, however, has yet to be realized in Denmark.

Draft:Denmark

2024-09-17T13:57:15Z

Anonymous:

== Overview in the National Level ==
[[File:Map DK.png|thumb|397x397px|Map of Denmark, with a focus on Greater Copenhagen]]

=== NeTEx and SIRI profiles ===
In Denmark, EU profiles for NeTEx and SIRI has been adopted. The implementation follows the European standards to ensure compatibility and data quality for journey planning and real-time information services.

Guidance on the national requirements and best practices is available in Danish through Trafikstyrelsen, the [https://www.trafikstyrelsen.dk/arbejdsomraader/kollektiv-trafik/statistik-og-data/krav-til-udstilling-af-data-til-rejseplanlaegning Danish Civil Aviation and Railway Authority], who is responsible for the implementation of NeTEx, SIRI and NAP on national level. For guidance in English, you can reach out to eudata@trafikstyrelsen.dk.

== Use cases ==
In Denmark two main stakeholders implement NeTEx and SIRI currently:

'''Movia''' is the PTA for buses and (certain) local trains in Greater Copenhagen. Other PTAs in this area are DSB (regional trains and S-trains) and Metro (Copenhagen metro and a tram line under construction).

'''Rejsekort & Rejseplan A/S''' is the company behind the national travel planner and electronic ticketing system in Denmark, which unites all regions and different transport operators into a common system.

=== '''Description''' ===

==== '''Rejsekort & Rejseplan''' ====
Rejsekort & Rejseplan A/S have used the NeTEx and SIRI standards nationwide, providing comprehensive coverage of the entire public transport network.

The architecture implemented by Rejsekort & Rejseplan A/S relies on centralized data exports from subcontractors IVU Traffic Technologies and HaCon, which supply the necessary data to Rejsekort and Rejseplan. These systems use the NeTEx and SIRI profiles to ensure high compatibility and data consistency. This architecture allows for the effective aggregation of transport data across various operators and regions, supporting both journey planning and real-time passenger information services.

===== Movia =====
Movia is using NeTEx and SIRI as the main interfaces around a new ‘Traffic Management System’ TMS. The delivery of the TMS was tendered and the contract was awarded FARA in 2023 and is expected to be in operation in 2025.

The system will handle all PT bus and local train traffic within Greater Copenhagen and Sealand:

* Number of ServiceJourneys on a workday: ~20 000
* Number of Calls on a workday: ~700 000
* Number of concurrent journeys in rush hour: ~1 000
* Number of active stops (Quays): ~17 000

=== Architecture ===

==== Movia ====
The TMS will consume stops and schedules in NeTEx-format. We use a profile based on the [https://enturas.atlassian.net/wiki/spaces/PUBLIC/pages/728891481/Nordic+NeTEx+Profile Nordic Profile] with minor adaptions.

The system will expose NeTEx as well as SIRI data. NeTEx will be exposed using the Nordic-based profile as well as EPIP.
[[File:Data providers.png|center|thumb|589x589px|TMS solution]]

=== Use cases ===
Currently, there are no active users of NeTEx and SIRI. The national travel planner already provides comprehensive and well-functioning services across the country, and the introduction of these standards has not been able to contribute to any improvement.

=== Outcome ===
Movia is currently using a system based on NOPTIS interfaces. The choice of NeTEx/SIRI for the new system was driven by the fact that NOPTIS is only supported by few suppliers – NeTEx/SIRI are supported by EU, has status as CEN/TS, and are widely supported. We believe that the choice of NeTEx/SIRI has opened the competition with lower price as a result. Moreover, Movia expects that with NeTEx/SIRI, it will be easier to integrate new consumers in the future.

As of now, no significant benefits from the implementation of NeTEx and SIRI have been observed in Denmark.

The largest Danish public transport authority is in the process of implementing NeTEx and SIRI, which may create new opportunities for enhanced data exchange and service improvements in the future. The full potential of these standards, however, has yet to be realized in Denmark.

Croatia

2024-09-17T13:47:17Z

Anonymous:

== Overview in the National Level ==
The national NeTEx profile of Croatia was created within the project of Implementation of NAP for multimodal traffic information and development of a local journey planner which took place in 2022 from March to November.

The following documents were used to implement the Croatian national profile for NeTEx (also available via Croatian Institute for Standards).

* CEN/TS 16614-1:2020 Public transport - Network and Timetable Exchange (NeTEx) - Part 1: Public transport network topology exchange format.
** “white paper” NeTEx-Network-WhitePaper_1.08 which describes NeTEx network concept in a non-expert way.
* CEN/TS 16614-2:2020 Public transport - Network and Timetable Exchange (NeTEx) - Part 2: Public transport scheduled timetables exchange.
** “white paper” 09.NeTEx-Timetable-WhitePaper_1.05 which describes NeTEx timetable in a non-expert way.
* CEN/TS 16614-4:2020 Public transport - Network and Timetable Exchange (NeTEx) - Part 4: Passenger Information European Profile.

Within the project of Implementation of NAP for multimodal traffic information and development of a local journey planner, an internal tool was created to convert GTFS files to NeTEx due to the lack of PTA/PTO providers that have a machine-readable format.

Some of the PTA/PTO providers are on the national and some on regional level, and due to various completeness of data provided we had issues with compliance.

Besides city centres, Croatia can be divided in three areas, central, maritime, and mountainous regions. From the perspective of data quality and available applications, central and maritime areas are more covered with quality data than mountainous region since they are driven by greater touristic demand.

Level of digitalization of PTA/PTO data is rather low. Where exist, different standards are used, with GTFS prevailing as the most used data format. Further activities must be made in order to raise the level of data digitalisation within stakeholders, to hold the stakeholders to recognize benefits of data sharing and to ensure provision in EU support and recommended formats. Croatia has already started several projects in order to fulfil goals, with results already being visible with inclusion of more data sources in standardized format in Croatian NAP.

The basic concepts for EPIP are described in the data dictionary in CEN/TS 16614-4: 2020 Public transport - Network and Timetable Data Exchange (NeTEx) - Part 4: Passenger Information European Profile.

The main terminology used to describe the topology of the public transport network are:

* ROUTE: an ordered list of discrete locations as a route point that geographically defines a single route passing through a road (or rail) network. ROUTE can pass through the same point of the route multiple times. ROUTE LINK can be used to connect ROUTE POINT points along the way.
* JOURNEY PATTERN: defined as an organized SCHEDULED STOP POINT (e.g. '''teyes''' where passengers enter and exit) and TIMING POINTS (i.e. information on the time required for the preparation of timetables) on each ROUTE describing the pattern of operation of public transport vehicles. Journey Pattern can go through the same point multiple times.
* TIMING PATTERN: redo sequence TIMING POINTS for each JOURNEY PATTERN determined by TIMING PATTERN. The sequence scheduled stop points (from journey pattern) is determined by the SERVICE PATTERN. Service Pattern (= variant ROUTE) is a subset of a JOURNEY PATTERN consisting of a stop point sequence.

A line (LINE) is usually defined as the sum of multiple ROUTEs with a public label (name, number). From a topological point of view ROUTS are usually very similar because the versions are basic ROUTE with some deviations. Two routes that share the same infrastructure path (or parallel path), but with the opposite orientation usually belong to the same LINE.

An XML document is a physical record of public passenger transport data used for the exchange between sender and recipient of EPIP-compliant data.

It is recommended that the XML document name be written as follows:

* The name of the document (prefix) is NETEX_PI
* The main version of EPIP; currently 01
* ISO 3166-2 Country Code
* Sender name (use NAP if data comes from National access point)
* Document type (LINE, NETWORK , or STOP)
** LINE: The document contains a description of one line: line number or name if no number is available (short name, fewer than 15 characters, made only of letters (uppercase and lowercase), numbers and "-")
** NETWORK: Document contains a description of two or more lines
** STOP: Document contains a description of all stops

* Date Created (YYMMDD)

* All fields are separated by a "_" character.

== Use cases ==
During the implementation of the NAP for multimodal traffic information and the development of a local journey planner, GTFS files were primarily transposed into NeTEx files. Currently, at NAP, data from several PTA/PTO providers (GPP Osijek, ZET, Pulapromet – bus, HŽ – train, and Jadrolinija – ferry) are available in the NeTEx standard. Additionally, the LJP was developed with all available PTA/PTO data. More information are accessible [https://www.promet-info.hr/ljp/?lang=en here].

In Croatia, the following projects utilize NeTEx and Datex standards:

* '''Smart City Rijeka, City of Rijeka - CEKOM Project''': Application of NeTEx and Datex standards for traffic management and passenger information.
* '''OLGA Green and Holistic Airport, City of Zagreb''': Application of NeTEx and Datex standards for traffic management and public transport optimization.
* '''Traffic Management System, City of Split''': Application of NeTEx and Datex standards for traffic management and passenger information.

=== Outcome ===
Most NAP users have expressed a strong interest in accessing PTA/PTO data, making it essential to ensure that all data available on NAP is updated in a timely manner, which is not always the case currently.

The implementation results have facilitated easier data exchange among various stakeholders. The harmonization of standards has led to the development of uniform applications, reducing the need for integrating non-standard data from third-party providers. This has decreased application development costs and increased the reusability of applications.

Portugal

2024-09-17T13:45:47Z

Anonymous:

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

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

== Use cases ==

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

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

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

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

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

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

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

Portugal

2024-09-17T11:24:24Z

Anonymous:

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

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

== Use cases ==

=== Description ===
'''Metropolitan Area of Porto'''

* Area: 2,041 km²
* Population: 1.76 million
* 76,000 university students (representing 20% of Portugal's university population)

As a Transport Authority, we are responsible for overseeing bus services operated by private companies. Our responsibilities include:

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

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

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

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

=== Outcome ===
As long as NeTEx covers the aspects required for information sharing, there is no need for extensions.

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

Portugal

2024-09-17T11:22:54Z

Anonymous:

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

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

== Use cases ==

=== Description ===
'''Metropolitan Area of Porto'''

* Area: 2,041 km²
* Population: 1.76 million
* 76,000 university students (representing 20% of Portugal's university population)

As a Transport Authority, we are responsible for overseeing bus services operated by private companies. Our responsibilities include:

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

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

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

=== Architecture ===
The platform is designed as a collection of microservices, with information exchange between specialized applications managed through NeTEx. This architecture allows for the replacement of any application with a commercial, internal, or open-source solution, provided that it supports exporting or importing data in the NeTEx format.
[[File:Portugal schema.png|thumb|656x656px]]
[[File:Flux diagram of NeTEx exchange.png|center|thumb|724x724px|Flux diagram of NeTEx exchange]]

=== Use cases ===
PLIM is the name of the platform where all internal information is communicated using NeTEx. It produces NeTEx, GTFS, SIRI, and GTFS-feed formats for dissemination to National Access Points (NAP).

=== Outcome ===
As long as NeTEx covers the aspects required for information sharing, there is no need for extensions.

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

File:Portugal schema.png

2024-09-17T11:22:09Z

Anonymous:

portugal

Portugal

2024-09-17T11:18:52Z

Anonymous:

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

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

== Use cases ==

=== Description ===
'''Metropolitan Area of Porto'''

* Area: 2,041 km²
* Population: 1.76 million
* 76,000 university students (representing 20% of Portugal's university population)

As a Transport Authority, we are responsible for overseeing bus services operated by private companies. Our responsibilities include:

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

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

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

=== Architecture ===
The platform is designed as a collection of microservices, with information exchange between specialized applications managed through NeTEx. This architecture allows for the replacement of any application with a commercial, internal, or open-source solution, provided that it supports exporting or importing data in the NeTEx format.
[[File:Flux diagram of NeTEx exchange.png|center|thumb|724x724px|Flux diagram of NeTEx exchange]]

=== Use cases ===
PLIM is the name of the platform where all internal information is communicated using NeTEx. It produces NeTEx, GTFS, SIRI, and GTFS-feed formats for dissemination to National Access Points (NAP).

=== Outcome ===
As long as NeTEx covers the aspects required for information sharing, there is no need for extensions.

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

Italy

2024-09-17T11:15:07Z

Anonymous:

= Overview in the National Level =

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

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

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

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

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

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

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

Main data categories exchanged are:

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

* Timetables
* Validity calendars
* Lines
* Transport Operators

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

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

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

Main data categories exchanged are:

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

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

Main data categories exchanged are:

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

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

Main data categories exchanged are:

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

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

Main data categories exchanged are:

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

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

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

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

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

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

= Use cases =

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

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

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

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

STA opted to implement NeTEx and SIRI ‘natively’, meaning there is no conversion between the production of the data and NeTEx data files from another exchange data format. Considering the complex modelling that is needed to represent the physical environment of public transport, the complete standards NeTEx and SIRI were decided as more suitable.
[[File:STA 3.png|center|thumb|500x500px|Challenges]]Based on the new architecture, NeTEx - SIRI, and other relevant standards, are implemented for the exchange of planned and real time data between back end systems (like operational planning tool ticketing system, travel planner and others. This architecture and the introduction of those standards is seen as the sustainable solution that can accommodate future developments on for example MaaS and integrated ticketing systems. In particular this arcitecture was chosen to support also "LinkingAlps", one of the EU projects in which it is developed a decentralised network of travel information services. This network will be created by interlinking existing regional or national journey planner services from all neighbour countries, with focus on multimodal transport (public transport, railways, new modes) through a standardised exchange service. In this context, the exchange of complete and interoperable datasets is key.
[[File:SA 1.png|center|thumb|731x731px]]
[[File:SA 2.png|center|thumb|500x500px]]

=== Outcome ===
To be completed.

Slovenia

2024-09-17T11:14:34Z

Anonymous: Created page with "== Overview in the National Level == == Use cases == === Description === === Architecture === === Use cases === === Outcome ==="

== Overview in the National Level ==

== Use cases ==

=== Description ===

=== Architecture ===

=== Use cases ===

=== Outcome ===

Sweden

2024-09-17T11:13:47Z

Anonymous: numerotation

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

==Use cases ==

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

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

===Architecture===

# The new '''National ticket Distribution System, Sweden''' infrastructure creates favorable conditions for the continued development of the ticket collaboration Resplus. The service will also enable more secure and widely validatable tickets when implemented. This, in turn, will contribute to increased safety and secured revenue. The system is being developed in collaboration with Turnit, an Estonian company with experience in standards within the railway industry in Europe. The new infrastructure is built on four essential components, with communication between these components based on the international and open OSDM-Online standard (Open Sales and Distribution Model).
## A "data warehouse" where the majority of Samtrafiken's partners will store their ticket products. This is where the offerings of transportation companies are entered, and it is from here that the service retrieves the inventory.
## The sales tool Samtrafiken TRAID and a sales API. In TRAID, retailers can directly book journeys, suitable for those retailers with a need for manual sales management (such as kiosks, stores, or call centers) or as a complement to web sales. Retailers and producers wishing to sell through their own sales tools (such as websites or apps) can choose to access the inventory via API.
## Travel search for all saleable ground-based collective transport.
## A central service, a so-called distribution hub, which retrieves, combines, and distributes ticket products from both Samtrafiken's data warehouse and external data warehouses for partners with their booking systems.
# '''The Skåne OpenTripPlanner''' (OTP2) is a server-side Java application that is primarily designed to interpret and combine map, transit service, and other mobility data sets, providing API endpoints that receive user origins and destinations and return trip plans to other applications along with vector map tiles, stop departures, and other rider information. In other words, OTP is a backend application that can work with other frontend user interfaces. OTP is an open standard and works with your website, mobile app, physical signage or other applications in order to provide relevant customer information and meaningful trip plans to riders.

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

France

2024-09-17T11:11:12Z

Anonymous: Created page with "== Overview in the National Level == == Use cases == === Description === === Architecture === === Use cases === === Outcome ==="

== Overview in the National Level ==

== Use cases ==

=== Description ===

=== Architecture ===

=== Use cases ===

=== Outcome ===

Australia

2024-09-17T11:10:47Z

Anonymous: Created page with "== Overview in the National Level == == Use cases == === Description === === Architecture === === Use cases === === Outcome ==="

== Overview in the National Level ==

== Use cases ==

=== Description ===

=== Architecture ===

=== Use cases ===

=== Outcome ===

Draft:Czech Republic

2024-09-17T11:10:19Z

Anonymous: Created page with "== Overview in the National Level == == Use cases == === Description === === Architecture === === Use cases === === Outcome ==="

== Overview in the National Level ==

== Use cases ==

=== Description ===

=== Architecture ===

=== Use cases ===

=== Outcome ===

Belgium

2024-09-17T11:09:30Z

Anonymous:

== Overview in the National Level ==

== Use cases ==

=== Description ===

=== Architecture ===

=== Use cases ===

=== Outcome ===

Croatia

2024-09-17T10:00:29Z

Anonymous:

== Overview in the National Level ==
The national NeTEx profile of Croatia was created within the project of Implementation of NAP for multimodal traffic information and development of a local journey planner which took place in 2022 from March to November.

The following documents were used to implement the Croatian national profile for NeTEx (also available via Croatian Institute for Standards).

* CEN/TS 16614-1:2020 Public transport - Network and Timetable Exchange (NeTEx) - Part 1: Public transport network topology exchange format.
** “white paper” NeTEx-Network-WhitePaper_1.08 which describes NeTEx network concept in a non-expert way.
* CEN/TS 16614-2:2020 Public transport - Network and Timetable Exchange (NeTEx) - Part 2: Public transport scheduled timetables exchange.
** “white paper” 09.NeTEx-Timetable-WhitePaper_1.05 which describes NeTEx timetable in a non-expert way.
* CEN/TS 16614-4:2020 Public transport - Network and Timetable Exchange (NeTEx) - Part 4: Passenger Information European Profile.

== Use cases ==

=== Description ===
Within the project of Implementation of NAP for multimodal traffic information and development of a local journey planner, an internal tool was created to convert GTFS files to NeTEx due to the lack of PTA/PTO providers that have a machine-readable format.

Some of the PTA/PTO providers are on the national and some on regional level, and due to various completeness of data provided we had issues with compliance.

Besides city centres, Croatia can be divided in three areas, central, maritime, and mountainous regions. From the perspective of data quality and available applications, central and maritime areas are more covered with quality data than mountainous region since they are driven by greater touristic demand.

Level of digitalization of PTA/PTO data is rather low. Where exist, different standards are used, with GTFS prevailing as the most used data format. Further activities must be made in order to raise the level of data digitalisation within stakeholders, to hold the stakeholders to recognize benefits of data sharing and to ensure provision in EU support and recommended formats. Croatia has already started several projects in order to fulfil goals, with results already being visible with inclusion of more data sources in standardized format in Croatian NAP.

=== Architecture ===
The basic concepts for EPIP are described in the data dictionary in CEN/TS 16614-4: 2020 Public transport - Network and Timetable Data Exchange (NeTEx) - Part 4: Passenger Information European Profile.

The main terminology used to describe the topology of the public transport network are:

* ROUTE: an ordered list of discrete locations as a route point that geographically defines a single route passing through a road (or rail) network. ROUTE can pass through the same point of the route multiple times. ROUTE LINK can be used to connect ROUTE POINT points along the way.
* JOURNEY PATTERN: defined as an organized SCHEDULED STOP POINT (e.g. '''teyes''' where passengers enter and exit) and TIMING POINTS (i.e. information on the time required for the preparation of timetables) on each ROUTE describing the pattern of operation of public transport vehicles. Journey Pattern can go through the same point multiple times.
* TIMING PATTERN: redo sequence TIMING POINTS for each JOURNEY PATTERN determined by TIMING PATTERN. The sequence scheduled stop points (from journey pattern) is determined by the SERVICE PATTERN. Service Pattern (= variant ROUTE) is a subset of a JOURNEY PATTERN consisting of a stop point sequence.

A line (LINE) is usually defined as the sum of multiple ROUTEs with a public label (name, number). From a topological point of view ROUTS are usually very similar because the versions are basic ROUTE with some deviations. Two routes that share the same infrastructure path (or parallel path), but with the opposite orientation usually belong to the same LINE.

An XML document is a physical record of public passenger transport data used for the exchange between sender and recipient of EPIP-compliant data.

It is recommended that the XML document name be written as follows:

* The name of the document (prefix) is NETEX_PI
* The main version of EPIP; currently 01
* ISO 3166-2 Country Code
* Sender name (use NAP if data comes from National access point)
* Document type (LINE, NETWORK , or STOP)
** LINE: The document contains a description of one line: line number or name if no number is available (short name, fewer than 15 characters, made only of letters (uppercase and lowercase), numbers and "-")
** NETWORK: Document contains a description of two or more lines
** STOP: Document contains a description of all stops

* Date Created (YYMMDD)

* All fields are separated by a "_" character.

=== Use cases ===
During the implementation of the NAP for multimodal traffic information and the development of a local journey planner, GTFS files were primarily transposed into NeTEx files. Currently, at NAP, data from several PTA/PTO providers (GPP Osijek, ZET, Pulapromet – bus, HŽ – train, and Jadrolinija – ferry) are available in the NeTEx standard. Additionally, the LJP was developed with all available PTA/PTO data. More information are accessible [https://www.promet-info.hr/ljp/?lang=en here].

In Croatia, the following projects utilize NeTEx and Datex standards:

* '''Smart City Rijeka, City of Rijeka - CEKOM Project''': Application of NeTEx and Datex standards for traffic management and passenger information.
* '''OLGA Green and Holistic Airport, City of Zagreb''': Application of NeTEx and Datex standards for traffic management and public transport optimization.
* '''Traffic Management System, City of Split''': Application of NeTEx and Datex standards for traffic management and passenger information.

=== Outcome ===
Most NAP users have expressed a strong interest in accessing PTA/PTO data, making it essential to ensure that all data available on NAP is updated in a timely manner, which is not always the case currently.

The implementation results have facilitated easier data exchange among various stakeholders. The harmonization of standards has led to the development of uniform applications, reducing the need for integrating non-standard data from third-party providers. This has decreased application development costs and increased the reusability of applications.

Draft:Denmark

2024-09-17T09:51:44Z

Anonymous:

== Overview in the National Level ==
[[File:Map DK.png|thumb|397x397px|Map of Denmark, with a focus on Greater Copenhagen]]

=== NeTEx and SIRI profiles ===
In Denmark, EU profiles for NeTEx and SIRI has been adopted. The implementation follows the European standards to ensure compatibility and data quality for journey planning and real-time information services.

Guidance on the national requirements and best practices is available in Danish through Trafikstyrelsen, the [https://www.trafikstyrelsen.dk/arbejdsomraader/kollektiv-trafik/statistik-og-data/krav-til-udstilling-af-data-til-rejseplanlaegning Danish Civil Aviation and Railway Authority], who is responsible for the implementation of NeTEx, SIRI and NAP on national level. For guidance in English, you can reach out to eudata@trafikstyrelsen.dk.

=== PTA's and PTO's ===
Movia is the PTA for buses and (certain) local trains in Greater Copenhagen. Other PTAs in this area are DSB (regional trains and S-trains) and Metro (Copenhagen metro and a tram line under construction).

Rejsekort & Rejseplan A/S is the company behind the national travel planner and electronic ticketing system in Denmark, which unites all regions and different transport operators into a common system.

== Use cases ==

=== Description ===
Movia is using NeTEx and SIRI as the main interfaces around a new ‘Traffic Management System’ TMS. The delivery of the TMS was tendered and the contract was awarded FARA in 2023 and is expected to be in operation in 2025.

The system will handle all PT bus and local train traffic within Greater Copenhagen and Sealand:

* Number of ServiceJourneys on a workday: ~20 000
* Number of Calls on a workday: ~700 000
* Number of concurrent journeys in rush hour: ~1 000
* Number of active stops (Quays): ~17 000
Rejsekort & Rejseplan A/S have used the NeTEx and SIRI standards nationwide, providing comprehensive coverage of the entire public transport network.

=== Architecture ===
The TMS will consume stops and schedules in NeTEx-format. We use a profile based on the [https://enturas.atlassian.net/wiki/spaces/PUBLIC/pages/728891481/Nordic+NeTEx+Profile Nordic Profile] with minor adaptions.

The system will expose NeTEx as well as SIRI data. NeTEx will be exposed using the Nordic-based profile as well as EPIP.
[[File:Data providers.png|center|thumb|589x589px|Data providers and consumers]]

The architecture implemented by Rejsekort & Rejseplan A/S relies on centralized data exports from subcontractors IVU Traffic Technologies and HaCon, which supply the necessary data to Rejsekort and Rejseplan. These systems use the NeTEx and SIRI profiles to ensure high compatibility and data consistency. This architecture allows for the effective aggregation of transport data across various operators and regions, supporting both journey planning and real-time passenger information services.

=== Use cases ===
Currently, there are no active users of NeTEx and SIRI. The national travel planner already provides comprehensive and well-functioning services across the country, and the introduction of these standards has not been able to contribute to any improvement.

=== Outcome ===
Movia is currently using a system based on NOPTIS interfaces. The choice of NeTEx/SIRI for the new system was driven by the fact that NOPTIS is only supported by few suppliers – NeTEx/SIRI are supported by EU, has status as CEN/TS, and are widely supported. We believe that the choice of NeTEx/SIRI has opened the competition with lower price as a result. Moreover, Movia expects that with NeTEx/SIRI it will be easier to integrate new consumers in the future.

As of now, no significant benefits from the implementation of NeTEx and SIRI have been observed in Denmark.

The largest Danish public transport authority is in the process of implementing NeTEx and SIRI, which may create new opportunities for enhanced data exchange and service improvements in the future. The full potential of these standards, however, has yet to be realized in Denmark.

Draft:Denmark

2024-09-17T09:51:01Z

Anonymous:

== Overview in the National Level ==
[[File:Map DK.png|thumb|397x397px|Map of Denmark, with a focus on Greater Copenhagen]]

=== NeTEx and SIRI profiles ===
In Denmark, EU profiles for NeTEx and SIRI has been adopted. The implementation follows the European standards to ensure compatibility and data quality for journey planning and real-time information services.

Guidance on the national requirements and best practices is available in Danish through Trafikstyrelsen, the [https://www.trafikstyrelsen.dk/arbejdsomraader/kollektiv-trafik/statistik-og-data/krav-til-udstilling-af-data-til-rejseplanlaegning Danish Civil Aviation and Railway Authority], who is responsible for the implementation of NeTEx, SIRI and NAP on national level. For guidance in English, you can reach out to eudata@trafikstyrelsen.dk.

=== PTA's and PTO's ===
Movia is the PTA for buses and (certain) local trains in Greater Copenhagen. Other PTAs in this area are DSB (regional trains and S-trains) and Metro (Copenhagen metro and a tram line under construction).

Rejsekort & Rejseplan A/S is the company behind the national travel planner and electronic ticketing system in Denmark, which unites all regions and different transport operators into a common system.

== Use cases ==

=== Description ===
Movia is using NeTEx and SIRI as the main interfaces around a new ‘Traffic Management System’ TMS. The delivery of the TMS was tendered and the contract was awarded FARA in 2023 and is expected to be in operation in 2025.

The system will handle all PT bus and local train traffic within Greater Copenhagen and Sealand:

* Number of ServiceJourneys on a workday: ~20 000
* Number of Calls on a workday: ~700 000
* Number of concurrent journeys in rush hour: ~1 000
* Number of active stops (Quays): ~17 000
Rejsekort & Rejseplan A/S have used the NeTEx and SIRI standards nationwide, providing comprehensive coverage of the entire public transport network.

=== Architecture ===
The TMS will consume stops and schedules in NeTEx-format. We use a profile based on the [https://enturas.atlassian.net/wiki/spaces/PUBLIC/pages/728891481/Nordic+NeTEx+Profile Nordic Profile] with minor adaptions.

The system will expose NeTEx as well as SIRI data. NeTEx will be exposed using the Nordic-based profile as well as EPIP.
[[File:Data providers.png|center|thumb|518x518px|Data providers and consumers]]

The architecture implemented by Rejsekort & Rejseplan A/S relies on centralized data exports from subcontractors IVU Traffic Technologies and HaCon, which supply the necessary data to Rejsekort and Rejseplan. These systems use the NeTEx and SIRI profiles to ensure high compatibility and data consistency. This architecture allows for the effective aggregation of transport data across various operators and regions, supporting both journey planning and real-time passenger information services.

=== Use cases ===
Currently, there are no active users of NeTEx and SIRI. The national travel planner already provides comprehensive and well-functioning services across the country, and the introduction of these standards has not been able to contribute to any improvement.

=== Outcome ===
Movia is currently using a system based on NOPTIS interfaces. The choice of NeTEx/SIRI for the new system was driven by the fact that NOPTIS is only supported by few suppliers – NeTEx/SIRI are supported by EU, has status as CEN/TS, and are widely supported. We believe that the choice of NeTEx/SIRI has opened the competition with lower price as a result. Moreover, Movia expects that with NeTEx/SIRI it will be easier to integrate new consumers in the future.

As of now, no significant benefits from the implementation of NeTEx and SIRI have been observed in Denmark.

The largest Danish public transport authority is in the process of implementing NeTEx and SIRI, which may create new opportunities for enhanced data exchange and service improvements in the future. The full potential of these standards, however, has yet to be realized in Denmark.

File:Data providers.png

2024-09-17T09:48:48Z

Anonymous:

Data providers and consumers

Draft:Denmark

2024-09-17T09:38:33Z

Anonymous:

== Overview in the National Level ==
[[File:Map DK.png|thumb|397x397px|Map of Denmark, with a focus on Greater Copenhagen]]

=== NeTEx and SIRI profiles ===
In Denmark, EU profiles for NeTEx and SIRI has been adopted. The implementation follows the European standards to ensure compatibility and data quality for journey planning and real-time information services.

Guidance on the national requirements and best practices is available in Danish through Trafikstyrelsen, the [https://www.trafikstyrelsen.dk/arbejdsomraader/kollektiv-trafik/statistik-og-data/krav-til-udstilling-af-data-til-rejseplanlaegning Danish Civil Aviation and Railway Authority], who is responsible for the implementation of NeTEx, SIRI and NAP on national level. For guidance in English, you can reach out to eudata@trafikstyrelsen.dk.

=== PTA's and PTO's ===
Movia is the PTA for buses and (certain) local trains in Greater Copenhagen. Other PTAs in this area are DSB (regional trains and S-trains) and Metro (Copenhagen metro and a tram line under construction).

Rejsekort & Rejseplan A/S is the company behind the national travel planner and electronic ticketing system in Denmark, which unites all regions and different transport operators into a common system.

== Use cases ==

=== Description ===
Movia is using NeTEx and SIRI as the main interfaces around a new ‘Traffic Management System’ TMS. The delivery of the TMS was tendered and the contract was awarded FARA in 2023 and is expected to be in operation in 2025.

The system will handle all PT bus and local train traffic within Greater Copenhagen and Sealand:

* Number of ServiceJourneys on a workday: ~20 000
* Number of Calls on a workday: ~700 000
* Number of concurrent journeys in rush hour: ~1 000
* Number of active stops (Quays): ~17 000
Rejsekort & Rejseplan A/S have used the NeTEx and SIRI standards nationwide, providing comprehensive coverage of the entire public transport network.

=== Architecture ===
The TMS will consume stops and schedules in NeTEx-format. We use a profile based on the [https://enturas.atlassian.net/wiki/spaces/PUBLIC/pages/728891481/Nordic+NeTEx+Profile Nordic Profile] with minor adaptions.

The system will expose NeTEx as well as SIRI data. NeTEx will be exposed using the Nordic-based profile as well as EPIP.
[[File:Data dk.png|center|thumb|454x454px|Data providers and consumers]]The architecture implemented by Rejsekort & Rejseplan A/S relies on centralized data exports from subcontractors IVU Traffic Technologies and HaCon, which supply the necessary data to Rejsekort and Rejseplan. These systems use the NeTEx and SIRI profiles to ensure high compatibility and data consistency. This architecture allows for the effective aggregation of transport data across various operators and regions, supporting both journey planning and real-time passenger information services.

=== Use cases ===
Currently, there are no active users of NeTEx and SIRI. The national travel planner already provides comprehensive and well-functioning services across the country, and the introduction of these standards has not been able to contribute to any improvement.

=== Outcome ===
Movia is currently using a system based on NOPTIS interfaces. The choice of NeTEx/SIRI for the new system was driven by the fact that NOPTIS is only supported by few suppliers – NeTEx/SIRI are supported by EU, has status as CEN/TS, and are widely supported. We believe that the choice of NeTEx/SIRI has opened the competition with lower price as a result. Moreover, Movia expects that with NeTEx/SIRI it will be easier to integrate new consumers in the future.

As of now, no significant benefits from the implementation of NeTEx and SIRI have been observed in Denmark.

The largest Danish public transport authority is in the process of implementing NeTEx and SIRI, which may create new opportunities for enhanced data exchange and service improvements in the future. The full potential of these standards, however, has yet to be realized in Denmark.

Austria

2024-09-17T09:34:36Z

Anonymous: rephrasing

== Overview in the National Level ==
For many implementations, the VDV standards (incl. VDV736) are preferred over other options, for them being tailored to the regional specifics.

[https://data.mobilitaetsverbuende.at/en MVO] publishes NeTEx data and preferably uses VDV736 (SIRI-SX) for situation information.

== Use cases ==

=== Description ===
For the purposes of operating and maintaining customer information channels (such as the WienMobil app, digital signage and departure boards, the website, on-board information, etc.), Wiener Linien has introduced an API gateway as a middleware component. This ensures that all customer-facing channels source their information from a single system (the API gateway), providing consistent information across all available platforms.

=== Architecture ===
Since the data sources connected to the API Gateway may provide different formats, or the data required for "customer information" may be scattered across various independent sources, Wiener Linien has implemented SIRI and/or NeTEx as the canonical data formats within the API Gateway. This approach facilitates the consolidation of information within the API Gateway, ensuring it serves as the single point of truth for all customer information channels.

The API Gateway can provide customer information channels with data in the canonical format (SIRI or NeTEx) or transform the data into any format required by the consuming system.

For specific use cases, the data can be enriched before being provided to the customer information channels:

* Automatic translation of SIRI-SX Situation Descriptions
* Generation of sign language videos
* Creation of workload or delay estimates using machine learning

=== Use cases ===
FIS+ involves on-board information screens in the latest subway rolling stock (X-Wagen). The necessary data, including station departures and current situations, is retrieved from internal data sources, transformed into the SIRI-SM and SIRI-SX canonical formats, and then converted into a proprietary format that contains only the most relevant information. This format is extremely lightweight due to limited bandwidth, and the information is subsequently forwarded to the rolling stock.

For the WienMobil App and WienMobil Monitor, the relevant information (station departures and current situations) is pulled from multiple data sources, including external sources from other transport operators like ÖBB. This data is transformed into the canonical SIRI-SM and SIRI-SX formats, cached within the API Gateway, and then delivered on demand to the app backend. The format is optimized by omitting redundant overhead to improve efficiency.

The e-Paper timetable follows a similar process. Station departure and current situation data are pulled from internal data sources, transformed into SIRI-SM and SIRI-SX, cached within the API Gateway, and sent to the e-Paper backend as needed.

For the generation of sign language videos, current situation data is regularly retrieved from internal sources, transformed into SIRI-SX, and sent to the SignTime API. SignTime processes the situation descriptions, generating a sign language video for each relevant entry. A link to the video is returned and can be added as a custom field in any subsequent SIRI-SX messages.

In the case of the WienMobil Alexa Skill, the required information (station departures) is sourced from internal and external data sources (such as ÖBB), transformed into SIRI-SM, cached in the API Gateway, and provided on demand to the backend system of the Alexa Skill.

=== Outcome ===
The chosen data standard framework is highly robust, accommodating virtually any use case. However, this flexibility introduces significant complexity, which can be challenging for some colleagues and implementors. Despite this, it is well-suited as a canonical data format for these reasons. With this framework in place, Wiener Linien is well-prepared to meet the requirements of EU Regulation 2017/1926.