Brief Description
Public transport is based on the timetable. It is planned annually and then continuously updated (see also Timetable data – overview).
Real-time data describes the status of the timetable in the now (e.g. delays).
After the ‘now’, the ‘actual’ comes, i.e. the ‘actual’ data describes the journeys actually made or forecast.
Data and interfaces
Note: A description of how to access the APIs can be found here: Howto: Access our APIs with API Keys
The most important data and interfaces:
Grouped under Real-Time, Event and Forecast Data: https://data.opentransportdata.swiss/group/currentdata
- Real-time:
- Forecast:
Functional Description
As a data format for real-time data, such as delays, we are currently publishing the following:
- GTFS-Realtime (GTFS-RT) (Trip Updates specifically)
- SIRI-Estimate Timetable (SIRI-ET) & SIRI-Planned Timetable (SIRI-PT)
Matching is needed to match the plan, real-time and event data (for the special case HRDF+GTFS-RT).
Not all business organisations provide us with their real-time. Which exactly do it is maintained in two separate datasets:
At the same time, we provide data about the train composition (formation) which is a mixture of real-time and forecast data. It describes the sequence of individual coaches of a train and its characteristics. The daily formation data extends up to three days in the future, but only with incomplete data. The accuracy of the data varies from the day of the actual departure.
We also offer occupancy forecast data, i.e. how full the train is likely to be.
Note: We only offer formation and forecast data for some rail-bound transport companies.
Explanations of terms
| Term | Description |
|---|---|
| Echtzeit – Verspätungsprognosen | Real-time and forecast data (including its quality) are delivered exactly as they are delivered. The threshold for delays is differentiated between ‘railway’ and ‘tram/bus’: Train: 3 minutes Tram/bus: 1 minute The threshold value is higher for ‘railways’ because the journey time between two stopping points typically takes longer. In addition, the frequency density is lower. The highest priority is to display delay forecasts which are logical and consistent for each channel for the customer. In some cases, displaying delay forecasts of as little as 1 minute is overridden by other criteria (for example, data quality). Depending on the situation, threshold values may differ depending on the media/channel, type of information (acoustic/visual or area of application) and data quality. For delay displays, it is a good idea to round the minutes according to the following criteria: In the case of departure times, delays should be more rounded off in favour of passenger safety. For arrival times, delays tend to be rounded up. It is recommended that delays of up to 20 minutes be shown in minute intervals if possible. |