Real-time and forecast data

The basis of public transport is the timetable, which is planned annually and updated continuously.

Real-time data describes the current status of the timetable (e.g. delays). After the now, the actual comes, i.e. the actual data describes the actual or forecast journeys.

Overview of timetable data

Data and interfaces

Real-time and forecast data

GTFS Realtime
(GTFS-RT)

SIRI Planned Timetable
(SIRI-PT)

SIRI Estimated Timetable
(SIRI-ET)

Business organizations with real-time data

Train Formation Service (Train Composition)

Occupancy forecast SIRI-ET

Occupancy forecast JSON

We publish real-time data (e.g. delays) in the formats GTFS-RT (Trip updates) as well as SIRI-ET and SIRI-PT. To link planned, real-time and event data, a matching is required (special case: HRDF+GTFS-RT). Availability varies by transport company; see the ‘Business organisations with real-time data’ record for details.

For selected railway operations, we offer additional forecast data. Train formation combines real-time and forecast data on wagon sequence and properties. Available up to 3 days in advance (accuracy and completeness until departure). The occupancy forecast shows the expected occupancy rate of trains.

The number of queries on SIRI PT is limited to 24 per day and 10 per hour. The volume of data is very large and after the data has been transmitted around 04:00-05:00, there are actually no more updates. In other words, SIRI PT should only be used for the actual timetable transmission for the operating day.

Explanation of terms

Term	Explanation
Real-time – delay forecasts	Real-time and forecast data (including its quality) is delivered exactly as it is delivered. The threshold for delays is differentiated between ‘railway’ and ‘tram/bus’: Train: 3 minutes Tram/bus: 1 minute The threshold is higher in the case of ‘railways’ because the journey time between two stops typically takes longer. In addition, the frequency of traffic is lower. The highest priority is to ensure that forecasts of delays are presented logically for the customer and consistently for each channel. The display of forecasts for delays of as little as 1 minute takes precedence in some cases to other criteria (e.g. data quality). Depending on the situation, it is possible that threshold values for media/channels, type of information (acoustic/visual or area of application) and data quality may differ. For delays, it is recommended that the minutes be rounded up according to the following criteria: – At departure times, delays should be rounded up for the sake of passenger safety. – At arrival times, delays are rounded up rather. It is recommended that delays of up to 20 minutes be shown in minute intervals if possible.

Term

Explanation

Real-time – delay forecasts

Real-time and forecast data (including its quality) is delivered exactly as it is delivered.

The threshold for delays is differentiated between ‘railway’ and ‘tram/bus’:
Train: 3 minutes
Tram/bus: 1 minute

The threshold is higher in the case of ‘railways’ because the journey time between two stops typically takes longer. In addition, the frequency of traffic is lower.

The highest priority is to ensure that forecasts of delays are presented logically for the customer and consistently for each channel. The display of forecasts for delays of as little as 1 minute takes precedence in some cases to other criteria (e.g. data quality). Depending on the situation, it is possible that threshold values for media/channels, type of information (acoustic/visual or area of application) and data quality may differ.

For delays, it is recommended that the minutes be rounded up according to the following criteria:
– At departure times, delays should be rounded up for the sake of passenger safety.
– At arrival times, delays are rounded up rather. It is recommended that delays of up to 20 minutes be shown in minute intervals if possible.

Further links

Access to APIs

A description of how to access the APIs can be found here

Access to APIs