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 | NeTEx EPIP Based* | NeTEx EPIP Compatible** | Documentation |
|---|---|---|---|
| Austria (AT) | ✅ | Austrian profile | |
| Denmark (DK) | ✅ | Denmark profile - NAP in Denmark | |
| France (FR) | ✅ | French profile - Common profil - Stop Profile - Network Profil - Timetable profile - Fare Profile - Parking profile - Accessibility Profile | |
| Italy (IT) | ✅ | Italian profile | |
| Netherlands (NL) | ✅ | Netherlands profile - Bison Fares | |
| Nordic (Norway, Sweden, Finland, Denmark) | ✅ | Nordic profile | |
| Portugal (PT) | Portuguese profile | ||
| Slovenija (SI) | ✅ | Slovenian profile | |
| UK (GB) | ✅ | UK profile - Introduction - Stop and Timetables - Fares | |
| Ireland (IE) | Irish profile - Profile Elements - Profile Data Mappings | ||
| Czech Republic (CZ) | ✅ |
*Profiles of this category have been specified based on EU Minimum profile and produced files are interoperable without adaptation or transformation.
** 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, or after EU profiles but produced files they need adaptation to be interoperable.
Data categories
Data categories are identified based on MMTIS EU Regulation 1926/2017
| Level of service (LOS) | Static data |
|---|---|
| Static data - Level of service 1 (LOS 1 ) | |
| LOS 1-1 | Address identifiers (building number, street name, postcode) |
| LOS 1-2 | Topographic places (city, town, village, suburb, administrative unit) |
| LOS 1-3 | Points of interest (related to transport information) to which people may wish to travel |
| LOS 1-4 | Operational Calendar, mapping day types to calendar dates |
| LOS 1-5 | Identified access nodes (all scheduled modes) |
| LOS 1-6 | Geometry/map layout structure of access nodes (all scheduled modes) |
| LOS 1-7 | Connection links where interchanges may be made, default transfer times between modes at interchanges |
| LOS 1-8 | Network topology and routes/lines (topology) |
| LOS 1-9 | Transport operators |
| LOS 1-10 | Timetables |
| LOS 1-11 | Planned interchanges between guaranteed scheduled services |
| LOS 1-12 | Hours of operation |
| LOS 1-13 | Vehicles (low floor; wheelchair accessible.) |
| LOS 1-14 | Accessibility of access nodes, and paths within an interchange (such as existence of lifts, escalators) |
| LOS 1-15 | Existence of assistance services (such as existence of on-site assistance) |
| LOS 1-16 | Road network |
| LOS 1-17 | Cycle network (segregated cycle lanes, on-road shared with vehicles, on-path shared with pedestrians) |
| LOS 1-18 | Pedestrian network and accessibility facilities |
| Framework data | |
| Static data - Level of service 2 (LOS 2) | |
| LOS 2-1 | Park & Ride stops |
| LOS 2-2 | Bike sharing stations |
| LOS 2-3 | Car-sharing stations |
| LOS 2-4 | Publicly accessible refueling stations for petrol, diesel, CNG/LNG, hydrogen powered vehicles, charging stations for electric vehicles |
| LOS 2-5 | Secure bike parking (such as locked bike garages) |
| LOS 2-6 | Information service |
| LOS 2-7 | Where and how to buy tickets for scheduled modes, demand responsive modes and car parking (all scheduled modes and demand-responsive incl. retail channels, fulfillment methods, payment methods) |
| LOS 2-8 | Trip plans, auxiliary information, availability check |
| LOS 2-9 | Basic common standard fares (all scheduled modes) |
| LOS 2-10 | Fare network data (fare zones/stops and fare stages) |
| LOS 2-11 | Standard fare structures (point to point including daily and weekly fares, zonal fares, flat fares) |
| LOS 2-12 | Vehicle facilities such as classes of carriage, on-board Wi-Fi. |
| Static data - Level of service 3 (LOS 3) | |
| LOS 3-1 | Passenger classes (classes of user such as adult, child, student, veteran, impaired access and qualifying conditions and classes of travel such as 1st, 2nd.) |
| LOS 3-2 | Common fare products (access rights such as zone/point-to-point including daily and weekly tickets/single/return, eligibility of access, basic usage conditions such as validity period/operator/time of travel/interchanging, standard point to point fares prices for different point to point pairs including daily and weekly fares/zonal fare prices/flat fare prices) |
| LOS 3-3 | Special Fare Products: offers with additional special conditions such as promotional fares, group fares, season passes, aggregated products combining different products and add on products such as parking and travel, minimum stay |
| LOS 3-4 | Basic commercial conditions such as refunding/replacing/exchanging/transferring and basic booking conditions such as purchase windows, validity periods, routing restrictions zonal sequence fares, minimum stay. |
| LOS 3-5 | How to pay tolls (incl. retail channels, fulfillment methods, payment methods) |
| LOS 3-6 | How to book car sharing, taxis, cycle hire etc. (incl. retail channels, fulfillment methods, payment methods) |
| LOS 3-7 | Where how to pay for car parking, public charging stations for electric vehicles and refueling points for CNG/LNG, hydrogen, petrol and diesel powered vehicles (incl. retail channels, fulfillment methods, payment methods) |
| LOS 3-8 | Detailed cycle network attributes (surface quality, side-by-side cycling, shared surface, on/off road, scenic route, ‘walk only’, turn or access restrictions (e.g. against flow of traffic) |
| LOS 3-9 | Parameters needed to calculate an environmental factor such as carbon per vehicle type or passenger mile or per distance walked |
| LOS 3-10 | Parameters such as fuel consumption needed to calculate cost |
| LOS 3-11 | Estimated travel times by day type and time-band by transport mode/combination of transport modes |
Static data - Level of service 1 (LOS 1)
| Data Categories | EPIP | AT | DK | FR | IT | NL | Nordic (SE, NOR, DK, FIN) | PT | SI | GB |
|---|---|---|---|---|---|---|---|---|---|---|
| LOS 1-1 | ✅ | ✅ | ✅ | |||||||
| LOS 1-2 | ✅ | ✅ | ✅ | ✅ | ||||||
| LOS 1-3 | ✅ | ✅ | ✅ | |||||||
| LOS 1-4 | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |||
| LOS 1-5 | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ||||
| LOS 1-6 | ✅ | ✅ | ✅ | ✅ | ✅ | |||||
| LOS 1-7 | ✅ | ✅ | ✅ | ✅ | ✅ | |||||
| LOS 1-8 | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| LOS 1-9 | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |
| LOS 1-10 | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| LOS 1-11 | ✅ | not existent | ✅ | ✅ | For connection links we use journey planner based on OSM map data, road, cycle, and pedestrian network is based on OpenStreetMap | ✅ | ✅ | |||
| LOS 1-12 | ✅ | ✅ | ✅ | ✅ | ✅ | |||||
| LOS 1-13 | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ||||
| LOS 1-14 | ✅ | ✅ | ✅ | ✅ | ✅ | |||||
| LOS 1-15 | ✅ | ✅ | ✅ | ✅ | ||||||
| LOS 1-16 | ✅ | ✅ | ✅ | |||||||
| LOS 1-17 | ✅ | ✅ | ✅ | |||||||
| LOS 1-18 | ✅ | ✅ | ✅ | |||||||
| Framework data | ✅ |
Static data - Level of service 2 (LOS 2)
| Data Categories | EPIP | AT | DK | FR | IT | NL | Nordic (SE, NOR, DK, FIN) | PT | SI | GB |
|---|---|---|---|---|---|---|---|---|---|---|
| LOS 2-1 | ✅ | ✅ | ✅ | ✅ | ||||||
| LOS 2-2 | ✅ | ✅ | ✅ | ✅ | ||||||
| LOS 2-3 | ✅ | ✅ | ✅ | ✅ | ||||||
| LOS 2-4 | Only charging stations for electric vehicles | ✅ | ||||||||
| LOS 2-5 | ✅ | ✅ | ✅ | ✅ | ||||||
| LOS 2-6 | ✅ | ✅ | ✅ | ✅ | ||||||
| LOS 2-7 | ✅ | ✅ | ✅ | |||||||
| LOS 2-8 | ✅ | ✅ | ✅ | |||||||
| LOS 2-9 | ✅ | ✅ | ✅ | ✅ | ✅ | |||||
| LOS 2-10 | ✅ | ✅ | ✅ | ✅ | ||||||
| LOS 2-11 | ✅ | ✅ | ✅ | ✅ | ||||||
| LOS 2-12 | ✅ | ✅ | ✅ | ✅ | ✅ |
Static data - Level of service 3 (LOS 3)
| Data Categories | EPIP | AT | DK | FR | IT | NL | Nordic (SE, NOR, DK, FIN) | PT | SI | GB |
|---|---|---|---|---|---|---|---|---|---|---|
| LOS 3-1 | ✅ | ✅ | ✅ | |||||||
| LOS 3-2 | ✅ | ✅ | ✅ | |||||||
| LOS 3-3 | ✅ | ✅ | ✅ | |||||||
| LOS 3-4 | ✅ | ✅ | ||||||||
| LOS 3-5 | ✅ | |||||||||
| LOS 3-6 | ||||||||||
| LOS 3-7 | ✅ | |||||||||
| LOS 3-8 | ✅ | |||||||||
| LOS 3-9 | ✅ | |||||||||
| LOS 3-10 | ✅ | |||||||||
| LOS 3-11 | ✅ |
⚠️ If you believe that your use cases are resolved in an existing profile, it is highly recommended to adopt an existing solutionand cooperate with the corresponding entity. You will save resources while you will ensure that your profile is interoperable.
📄 You can also find contact details for some of the entities responsible for the profiles in the documentation list. Otherwise you can contact us in DATA4PT.
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 | Availability | EU Minimum profile based* | EU Minimum SIRI profile compatible** | Documentation |
|---|---|---|---|---|
| Nordic (Norway, Sweden, Finland, Denmark) | Specified and in use | ✅ | Nordic SIRI profile | |
| UK (GB) | Specified and in use | ✅ | ||
| France (FR) | In use in numerous cities and regions | ✅ | ||
| Netherlands (NL) | Specified but not yet in operation | ✅ | ||
| Italy (IT) | Specified and currently in use by Piedmont Region and Bolzano Province. More regions by the end of 2024 | ✅ | Italian SIRI profile |
*Profiles of this category have been specified after the specification of the EU Minimum profile and are based on it.
** Profiles of this category are specified before the specification of the EU Minimum profile and they have been formed the basis for the EU Minimum profile definition.
Data categories
Data categories are identified based on MMTIS EU Regulation 1926/2017
| Level of service (LOS) | Types of the dynamic travel and traffic data |
|---|---|
| Dynamic data - Level of service 1 (LOS 1 ) | |
| LOS 1-1 | Disruptions (all modes) |
| LOS 1-2 | Real-time status information — delays, cancellations, guaranteed connections monitoring (all modes) |
| LOS 1-3 | Status of access node features (including dynamic platform information, operational lifts/escalators, closed entrances and exit locations — all scheduled modes) |
| Dynamic data - Level of service 2 (LOS 2) | |
| LOS 2-1 | Estimated departure and arrival times of services |
| LOS 2-2 | Current road link travel times |
| LOS 2-3 | Cycling network closures/diversions |
| LOS 2-4 | Availability of publicly accessible charging stations for electric vehicles and refuelling points for CNG/LNG, hydrogen, petrol and diesel powered vehicles |
| LOS 2-5 | Car-sharing availability, bike sharing availability |
| LOS 2-6 | Car parking spaces available (on and off-street), parking tariffs, road toll tariffs |
| Dynamic data - Level of service 3 (LOS 3) | |
| Future predicted road link travel times | |
Dynamic data - Level of service 1 (LOS 1)
| Data Categories | FR | 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 | FR | NL | Nordic (SE, NOR, DK, FIN) | GB |
|---|---|---|---|---|
| LOS 2-1 | ✅ | ✅ | ✅ | ✅ |
| LOS 2-2 | ✅ | |||
| LOS 2-3 | ||||
| LOS 2-4 | ||||
| LOS 2-5 | ✅ | ✅ | ||
| LOS 2-6 | ✅ | ✅ |
Dynamic data - Level of service 3 (LOS 3)
| Data Categories | FR | NL | Nordic (SE, NOR, DK, FIN) | GB |
|---|
⚠️ If you believe that your use cases are resolved in an existing profile, it is highly recommended to adopt an existing solutionand cooperate with the corresponding entity. You will save resources while you will ensure that your profile is interoperable.
📄 You can also find contact details for some of the entities responsible for the profiles in the documentation list. Otherwise you can contact us in DATA4PT.
Implementations per Country
Austria
Italy
Overview in National Level
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.
For Italy, Passenger Information and PT contracts information exchange have been identified as primary Use Cases. In this perspective two levels profile has been defined:
- Passenger Information profile (level 1) - Contracts profile (level 2 – incremental)
The italian Profile will be then extended to cover Fares, Alternative Modes (sharing mobility, micromobility) and Accessibility Use Cases, in order to cover all the category data required by Del. Reg. 1926/2017.
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 - For the level 1 of the Italian Netex Profile, European Passenger Information Profile (EPIP) has been identified as defined in the CEN Technical Specification prTS 16614:PI Profile.
Contracts profile 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 Equipments (lift/ramps, wheelchair etc) The level 2 of the Italian Netex Profile, is defined upon the first level of European Passenger Information Profile (EPIP).
Italian implementation For the Italian NeTEx profile implementation , a dedicated Guideline document has been defined together with an example for each level that shows how to fill the needed structures: the first fully compliant with EPIP (European Passenger Information Profile) and the second including level 2 of NeTEx Italian Profile (e.g. contracts).
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:
Bolzano, STA (Südtiroler Transportstrukturen)
STA (Südtiroler Transportstrukturen), 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 needed a standard which allows then to exchange this kind of information considering the multilingual data. NeTEx provided this opportunity. STA is in the process of innovating their IT architecture. They 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.
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.
Projects
LinkingAlps is one of the EU projects in which they develop 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.
Also, for LinkingAlps, they chose to introduce standards that are ready for any future architecture and can accommodate future developments on for example MaaS and ticketing.