National Implementations
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
Profile Name | Status/
Availability |
NeTEx EPIP Based* | NeTEx EPIP Compatible** | Documentation |
---|---|---|---|---|
Australia - Victoria (AU) | Specified but not yet in operation | β | β | |
Austria (AT) | Specified but not yet in operation | β | Austrian profile | |
Belgium (BE) | Specified but not yet in operation | β | GitHUb | |
Croatia (HR) | Specified and in use | β | β | NPT - Croatian NAP |
Denmark (DK) | Specified but not yet in operation | β | Denmark profile - NAP in Denmark | |
France (FR) | Specified and in use | β | French profile - Common profile - Stop profile - Network profile - Timetable profile - Fare profile - Parking profile - Accessibility profile | |
Italy (IT) | Specified and in use | β | Italian profile | |
Netherlands (NL) | Specified but not yet in operation | β | Netherlands profile - Bison Fares | |
Nordic (Norway, Sweden, Finland, Denmark) | Specified and in use | β | Nordic profile | |
Portugal (PT) | Specified and in use | Portuguese profile | ||
Slovenija (SI) | Specified but not yet in operation | β | Slovenian profile | |
UK (GB) | Specified and in use | β | UK profile - Introduction - Stop and Timetables - Fares | |
Ireland (IE) | Specified and in use | Irish profile - Profile Elements - Profile Data Mappings | ||
Czech Republic (CZ) | Specified but not yet in operation | β |
*Profiles of this category have been specified based on EU Minimum profile and are based on XML technology as EU profiles.
** 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 MMTIS EU Regulation 490/2024
Level of service (LOS) | Static data |
---|---|
Static data - Level of service 1 (LOS 1 ) | |
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 |
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 |
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) |
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 | |
Static data - Level of service 2 (LOS 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 |
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 |
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. |
Static data - Level of service 3 (LOS 3) | |
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 |
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 |
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 |
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) |
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)
Data Categories | EPIP | AU | AT | BE | HR | DK | FR | IT | NL | Nordic (SE, NOR, DK, FIN) | PT | SI | GB |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
LOS 1-1 | β | β | β | β | |||||||||
LOS 1-2 | β | β | β | β | β | β | β | ||||||
LOS 1-3 | β | β | β | β | β | ||||||||
LOS 1-4 | β | β | β | β | β | β | β | β | β | β | β | ||
LOS 1-5 | β | β | β | β | β | β | β | β | β | ||||
LOS 1-6 | β | β | β | β | β | β | β | β | |||||
LOS 1-7 | β | β | β | β | β | β | |||||||
LOS 1-8 | |||||||||||||
LOS 1-9 | β | β | β | β | β | β | β | β | β | β | β | β | β |
LOS 1-10 | β | β | β | β | β | β | β | β | β | β | β | β | |
LOS 1-11 | β | β | β | β | β | β | β | β | β | β | β | β | β |
LOS 1-12 | β | β | not existent | β | β | β | For connection links we use journey planner based on OSM map data, road, cycle, and pedestrian network is based on OpenStreetMap | β | β | ||||
LOS 1-13 | β | β | β | β | β | β | β | β | β | ||||
LOS 1-14 | β | β | β | ||||||||||
LOS 1-15 | β | β | β | β | β | β | β | β | β | β | |||
LOS 1-16 | β | β | β | β | β | β | β | β | |||||
LOS 1-17 | β | β | β | β | β | β | β | ||||||
LOS 1-18 | β | β | β | ||||||||||
LOS 1-19 | β | β | β | ||||||||||
LOS 1-20 | β | β | β | β | |||||||||
Framework data | β |
Static data - Level of service 2 (LOS 2)
Data Categories | EPIP | AU | AT | ΞΞ | HR | DK | FR | IT | NL | Nordic (SE, NOR, DK, FIN) | PT | SI | GB |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
LOS 2-1 | β | for off-street only | β | ||||||||||
LOS 2-2 | β | β | β | β | β | β | |||||||
LOS 2-3 | β | β | |||||||||||
LOS 2-4 | β | β | β | β | β | β | |||||||
LOS 2-5 | β | β | β | β | β | β | |||||||
LOS 2-6 | β | β | in off-street car parks only | β | β | β | |||||||
LOS 2-7 | β | β | |||||||||||
LOS 2-8 | β | β | β | β | β | ||||||||
LOS 2-9 | β | β | β | β | β | ||||||||
LOS 2-10 | β | β | β | β | β | β | β | ||||||
LOS 2-11 | β | β | β | β | β | β | β | ||||||
LOS 2-12 | β | β | β | β | β | ||||||||
LOS 2-13 | β | β | β | β | β | β | β |
Static data - Level of service 3 (LOS 3)
Data Categories | EPIP | AU | AT | BE | HR | DK | FR | IT | NL | Nordic (SE, NOR, DK, FIN) | PT | SI | GB |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
LOS 3-1 | β | β | β | β | β | β | |||||||
LOS 3-2 | β | β | β | β | β | ||||||||
LOS 3-3 | β | β | β | β | |||||||||
LOS 3-4 | β | β | |||||||||||
LOS 3-5 | β | ||||||||||||
LOS 3-6 | β | ||||||||||||
LOS 3-7 | β | ||||||||||||
LOS 3-8 | β | β | |||||||||||
LOS 3-9 | β | β | |||||||||||
LOS 3-10 | β |
Static data - Level of service 4 (LOS 4)
Data Categories | EPIP | AU | AT | BE | HR | DK | FR | IT | NL | Nordic (SE, NOR, DK, FIN) | PT | SI | GB |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
LOS 4-1 | |||||||||||||
LOS 4-2 | |||||||||||||
LOS 4-3 | |||||||||||||
LOS 4-4 | |||||||||||||
LOS 4-5 | |||||||||||||
LOS 4-6 | β | ||||||||||||
LOS 4-7 | |||||||||||||
LOS 4-8 | |||||||||||||
LOS 4-9 | |||||||||||||
LOS 4-10 | β | β |
β οΈ If you believe that your use cases are resolved in an existing profile, it is highly recommended to adopt an existing solution and cooperate with the corresponding entity. You will save resources while you will ensure that your profile is interoperable.
π You can also find contact details for some of the entities responsible for the profiles in the documentation list. Otherwise you can contact us in DATA4PT.
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
Profile Name | Status/
Availability |
EU Minimum profile based* | EU Minimum SIRI profile compatible** | Documentation |
---|---|---|---|---|
Australia - Victoria (AU) | Specified but not yet in operation | β | β | |
Croatia (HR) | Using an existing profile | β | ||
France (FR) | Specified and in use | β | French SIRI profile | |
Italy (IT) | Specified and in use | β | Italian SIRI profile | |
Netherlands (NL) | Specified but not yet in operation | β | ||
Nordic (Norway, Sweden, Finland, Denmark) | Specified and in use | β | Nordic SIRI profile | |
UK (GB) | Specified and in use | β |
*Profiles of this category have been specified based on EU Minimum profile and are based on XML technology as EU profiles.
** 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 MMTIS EU Regulation 490/2024
Level of service (LOS) | Types of the dynamic travel and traffic data |
---|---|
Dynamic data - Level of service 1 (LOS 1 ) | |
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 |
Dynamic data - Level of service 2 (LOS 2) | |
LOS 2-1 | a. Information service on parking tariffs β for transport on demand and personal transport |
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) |
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)
Data Categories | AU | HR | FR | IT | NL | Nordic (SE, NOR, DK, FIN) | GB |
---|---|---|---|---|---|---|---|
LOS 1-1 | β | β | β | β | β
dynamic platform is included |
β | |
LOS 1-2 | β | β | β | β | β | β
dynamic platform is included |
β |
LOS 1-3 | β | β | β | β
dynamic platform is included |
Dynamic data - Level of service 2 (LOS 2)
Data Categories | AU | HR | FR | IT | NL | Nordic (SE, NOR, DK, FIN) | GB |
---|---|---|---|---|---|---|---|
LOS 2-1 | |||||||
LOS 2-2 | only for car sharing and bike sharing | β | β | ||||
LOS 2-3 | off-street only | β | β |
Dynamic data - Level of service 3 (LOS 3)
Data Categories | AU | FR | IT | NL | Nordic (SE, NOR, DK, FIN) | GB |
---|---|---|---|---|---|---|
LOS 3-1 | β | β | β |
β οΈ If you believe that your use cases are resolved in an existing profile, it is highly recommended to adopt an existing solution and cooperate with the corresponding entity. You will save resources while you will ensure that your profile is interoperable.
π You can also find contact details for some of the entities responsible for the profiles in the documentation list. Otherwise you can contact us in DATA4PT.
Implementations per Country
In progress