Reference NeTEx profile for each country (EU member state) is based on “Passenger Information European Profile” (EPIP), which is described in
Typical use cases of the EPIP:
- provision of data for journey planners
- provision of data to a path mapping software tool on an (interactive) map
- provision of timetable printout data
- provision of station information
Since 2017, EPIP has received a great deal of attention from IT developers in the field of public transport, which they implement in journey planning software solutions.
The current version of EPIP is a subset of two parts (out of three) of the full version of NeTEx, namely:
- NeTEx Part 1 (Public transport — Network and Timetable Exchange (NeTEx) — Part 1: Public transport network topology exchange format, CEN TS 16614-1:2014), in
- NeTEx Part 2 (Public transport — Network and Timetable Exchange (NeTEx) — Part 2: Public transport scheduled timetables exchange, CEN TS 16614-2:2014).
EPIP represents an agreed minimum of concepts and data structures for the exchange of public transport data for EU countries. Most of the countries that participated in the preparation of the EPIP have a very diverse public transport (F, NL, UK, NO, CH, DE), so we can expect that the data of public transport in Slovenia will be easily converted into NeTEx or EPIP. The fact that EPIP includes more than one main form of public transport (air, bus, trolleybus, coach, funicular, metro, tram, cableway, rail, water, ferry, elevator and other) ensures the translation of Slovenian public transport data into EPIP or NeTEx. In addition to forms of public transport, other forms of transport (walk, car, taxi, cycle, movingWalkway) are also supported by NeTEx, because they relate to public transport and are also interesting for Slovenia.
EPIP does not yet include ticket concepts already defined in the third part of NeTEx (Public transport — Network and Timetable Exchange (NeTEx) — Part 3: Public transport fares exchange format, CEN TS 16614-3:2016). The ticket description can be included in the EPIP-based data exchange, but it should be noted that over time it will be necessary to adapt to the ticket profile for which there is an initiative as a »complementary and separate European Fare Profile«. We can also expect an extension of EPIP with Accessibility Profile (accesibility concepts for passengers with disabilities). These extentions refer to new technical specification documents and XSD schemas for XML. Due to the modularity of XML schemas, these extensions will not devalue existing EPIP-compliant documents, they will only need to be extended with references to new schemas and use additional XML elements.