National implementations
NeTEx national and EU minimum profiles inventory π
A number of national and transnational profiles have already been defined for different European countries, while there are new profiles under development. In the following 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.
** Profiles of this category have been specified before the definition of EU Minimum profile but they have been formed the basis for its specification.
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.