#AutoTranslate
Brief Description
First Data sets is available for long-distance bus timetables. These are:
- BlaBlaCar bus (generated from Blablacar Bus – Theoretical and real-time schedules of the European network – Data Europa EU)
- Flixbus (generated from a Flixbus API for the whole of Europe)
Go to the dates
Functional Description
The data is stored as NeTEx (cf. Cookbook). This is not yet the optimal solution at the moment and further work is required:
- Connecting bus stops with public transport stops (METABHF)
- Use more official stops for car terminals
- Checking the consistency of the data
The data sets are used, among other things, for testing the two NeTEx profiles.
The data is not currently included in the Swiss public transport collection.
It is planned to update the data at least on a quarterly basis.
The long-distance bus connections are now integrated in OJP 2.0. International long-distance buses are integrated according to the following rules:
- Data update: Once a month
- Exclusion of domestic connections: Purely Swiss domestic connections are automatically excluded.
- Footpath routing: Scheduled with a buffer of 60 seconds.
- Stop mapping via LIR: Stops can be read from LIR and are mapped as long as they have the same coordinates.
- Legal information: Provision of information on the cabotage ban.
Technical Description
The data is stored in accordance with the European minimum profile (EPIP, Part 4 European Passenger Information Profile – EPIP (CEN/TS 16614-4:2017) or VDV-462 is provided.
The import of long-distance bus data is done using the GTFS data files provided by the long-distance bus companies.
Long-distance buses are currently still classified in OJP using PtMode = Bus / BusSubmode = expressBus. A change to PtMode = coach / coachSubmode = internationalCoach will follow.
Further information
Known issues
- The mode must be set to ‘coach’ and the submode to ‘internationalCoach’.