Update on 13 October 2026: The disruption has been rectified. The last timetable exports have been published as usual. Update 8 October 2026: The fault with data preparation has now been rectified. However, we will not run an exceptional production operation. The next production of the HRDF export starts on Friday evening and will be…
Starting with one of the next feeds (probably September or later), we are planning some new features in GTFS RT Service Alerts. Separate feeds In order to better meet the needs of our users and to reduce the volume of data, we will introduce four separate feeds for the event data: Feed Category (Planned) Perspective…
Update 2026-07-30: TFS operation is working normally again, errors in the data due to the malfunction should no longer occur in the meantime. As of approx. 7pm yesterday 2026-07-28, some of the train formation service no longer works correctly. The error has been found and corrected. Errors in the data can still be expected for…
Here are the most important changes and improvements at a glance: The new functions can also be accessed via the OJP demonstrator be looked at. The complete changelog can be found here: Release 1.4.0: Fixed SLOID issues · openTdataCH/ojp-nova
As of 1 June 2026, the data set ‘Business organizations with real-time data‘ added an additional column. This new ‘siriVDV’ column is inserted between the ‘source’ and ‘etAUS’ columns. It indicates whether the business organisation in question delivers data in the SIRI or VDV format.
In the course of the upcoming migration, the logic for generating the SLOID (stop_id) adjusted. The aim is a more consistent and unambiguous representation of step and track information in the affected formats – GTFS, NeTEx* and OJP 1.0 and 2.0 – to be created. *NeTEx is not affected by the subsequent generation of the…
According to the HAFAS Raw Data Format (HRDF), the following change will be made in the *Z lines of the HRDF file FPLAN as of 17 February: In connection with the adjustment of the variants, there is also a change to the data record ‘Swiss Journey ID (SJYID) – list’: From 17 February, the information…
On 14 October, the new ‘SLOID’ column was added to both actual data files. Note: During the transition phase from BPUIC to SLOID, missing SLOID values are replaced by values from atlas supplemented, if available. Where possible, this is assigned at the boarding area; otherwise it is assigned at the level of the stop. Affected…
#AutoTranslate GTFS-RT is actually provided as a protobuffer. A JSON version can be called via ?format=JSON. This is not recommended – except for test cases. The next program update on our site will change the serialization. Unfortunately, this causes the responses in JSON to look slightly different. The following changes will be made: Graphic representation…
A new version 2 has been available since 13 July 2025, which also includes data from foreign stops and data from transport companies that deliver the new SLOID in the BPUIC field. The actual data refers to the journeys actually travelled from the point of view of customer information, i.e. for example when a vehicle…
From now on, Swiss traffic situations – known from radio reports – are available as Open Data on opentransportdata.swiss. Cookbook: Affected data and interfaces https://data.opentransportdata.swiss/en/dataset/trafficsituations
Next Monday, 2025-05-26, there will be a deployment for a bugfix to the traffic light signalling systems (LSA). This will result in a short-term (approx. 15 min) interruption to the LSA real-time data. Cookbook Affected data and interfaces
The old data catalogue was definitively switched off on 05 March 2025 and the data will only be made available via data.opentransportdata.swiss. All permalinks must be adjusted accordingly (see Information in the newsletter of 13 January 2025)
From this point onwards, it will no longer be possible to view the usage and the remaining quota of existing keys there. For this overview, you need to register in the new API Manager (only available from 3 March 2025), create new keys and replace the existing ones. The old keys remain valid until further…
Our archive of the actual data is now available at https://archive.opentransportdata.swiss/. Here you will find all the daily actual data files for each month in a ZIP archive. Data is available from 2016 to the last complete month. The data for the current month can be found at https://data.opentransportdata.swiss/en/dataset/istdaten. The actual data contains either actual…
From 17 February 2025 update: 20 February 2025, the following “LargeAPI” (LA) data will only be accessible via the new URLs. We ask you to switch to the new APIs immediately. Important additional information: Affected data and interfaces
Due to a change in the FOS service, you must create a new API key; the service is now called “Train formation services – Alpha”. Cookbook: Formation Service (Train Composition Data) Affected data and interfaces
“Go live” of our new CKAN data catalogue at https://data.opentransportdata.swiss/en/. All permalinks must be adapted by 5 February 2025. From now on, all our Cookbook pages will also link to the new catalogue. Affected data and interfaces