Skip to content


Our “Cookbook” provides you with basic information, instructions and tips: similar to a classic cookbook. In the same analogy, the cookbook has no “red thread”, so it is only suitable for reading through to a limited extent.

Is something missing or wrong? Please let us know via the contact form.

All pages of the cookbook can be found via the search function. The overview below illustrates what you can search for.


Who we are and where our data comes from

The Open Data Platform Mobility Switzerland (ODMCH) is operated by the System Tasks Customer Information Plus team “SKI+” (German only) with partners/suppliers.

The work of SKI+ is carried out on behalf of the Federal Office of Transport (FOT) and is financed by the Rail Infrastructure Fund (RIF). The work serves as preparation for the NADIM (National Data Networking Infrastructure Mobility). With NADIM, the federal government wants to enable efficient, climate-friendly, multimodal, inclusive and safe mobility and ensure international connectivity with the EU. In addition to ODMCH, the SKI+ team (German only) is also responsible for the Open Journey Planner and is working on the design of the NADIM services.

Against the background of the implementation of the future NADIM, SKI+ is meanwhile publishing uniform (interface) standards (German only) on behalf of the FOT in order to make a positive contribution to the harmonisation of the system landscape in public transport.

You can find out more about the connections and the relevant peripheral systems in our Big Picture.

How you can access our services & data

You can access our services via the programming interface (API → howto).

You can access our data in two ways with equivalent results:

  1. Via a download (→ structured or unstructured)
  2. Via the Comprehensive Knowledge Archive Network (CKAN) programming interface (CKAN-API → howto)

Graphical overview of our services & data

The following graphic provides an overview of the data provided, its origins and access options:

The following illustration of a travel chain calculated with the OJP shows what can be done with this data:

Further background information on our services & data

Route planner

You can access two route planners via our programming interface (API).

  1. Open Journey Planner (OJP)
  2. Travellors Realtime Information Advisory Standard (TRIAS). WARNING: We are planning to switch off the TRIAS interface in 2024.
The most important interfaces

  • TRIAS-API WARNING: Reflects a current search query, as we are planning to switch off the TRIAS interface in 2024.

Timetable, real-time, event and actual data

A timetable provides information on which line runs with which means of transport, with which characteristics, when and along which places, and much more. For example, that the IC5 train (means of transport and line) on which bicycles are allowed (property) departs every Monday at 12:00 (when) from the Zurich main station stop (which location).

A draft timetable is published every year before the finalised (annual) timetable. The source system for all timetables (and drafts) is called INFO+ (German only).

We offer you timetable data in 3 data formats:

  1. General Transit Feed Specification (GTFS)
  2. Hafas Raw Data Format (HRDF)
  3. Network Timetable Exchange (NeTEx)

Note: The timetable data of certain cable cars and chairlifts are not covered by the current data collection structures.

Plans change! That’s why you need the real-time and event data for the timetables. Matching is required to bring the planned and real-time data together. We are currently publishing the data format for the real-time data:

We provide the following for event data such as faults:

In addition to the real-time and event data, we also publish the “actual data“. These are the journeys actually made or forecast in relation to the planned journeys (timetable) on the previous day. In other words: now is real time, and later is “actual”. It should be noted that certain threshold values for communication apply to delay forecasts in Swiss public transport.

The most important data and interfaces 

  • Real time:
    • GTFS-RT Trip Updates
    • Planned: SIRI-Estimate Timetable (SIRI-ET)
    • Planned: SIRI-Planned Timetable (SIRI-PT)

Stops, offices, journey

  • Journey in the timetable is carried out along certain stops and has a unique journey ID (new Swiss standard: Swiss Journey ID, concept see ö, German only).
  • stop, also known as an operating point, is a place where passengers have official access to public transport.
  • Service centre extends the stops to include locations that have an indirect function in public transport, e.g. travel agencies.

The source system for all offices (and therefore also stops) is called DiDok/ATLAS.

The most important data

Means of transport and lines

We currently offer data on various modes of transport, e.g. trainsbuses, (sharing) cars, (sharing) bicycles. Where possible, we are expanding the available data sets to include other means of transport and providers of multimodal mobility services related to public transport.

In public transport, the primary means of transport are trains and buses. These usually have a designation, e.g. “S5”. The so-called line or line designation helps public transport users to identify the means of transport to be used. However, the concept of the line goes much further than this “commercial” view. You can read about this in the Swiss line directory and in the sources linked in the article.

For some rail-bound transport companies, we are able to provide an occupancy forecast, i.e. how full the train is likely to be.

In addition, in cooperation with some rail network infrastructure managers or railway undertakings (RUs), we can also indicate the number of trains on the sections of the railway network, i.e. the frequency of the routes between certain stops.

The most important data

Road traffic

Our data goes beyond public transport and also includes road traffic: thanks to close cooperation with the Federal Office of Topography (swisstopo), the Federal Roads Office (FEDRO) and the Swiss Federal Office of Energy (SFOE), among others.

As soon as you want to switch back to public transport, the Park & Rail and bike parking spaces will help you.

If you don’t have your own bike or car, we refer you to the locations and availability of shared mobility offers from the SFOE. Or you can take the long-distance bus.

We are also currently working on modelling the vehicle pooling offers in Switzerland and then making this data available. Other terms for vehicle pooling are car pooling, ride sharing, carpooling, carpooling or car hire (rarely also car sharing).

On-demand transport, on the other hand, has already been modelled, i.e. services where you can use a journey “on demand” and possibly share the journey with other passengers. One example is the door-to-door service offered by PubliCar in Appenzell, which complements the existing public transport system. We provide the data as NeTEx (German only) and GTFS.

The most important data and interfaces (real time)

Sales information (tickets and subscriptions)

The basis for sales is the business organisations involved. A business organisation usually corresponds to a transport company. Some of the business organisations provide us with their real-time data.

The alliances of these companies (e.g. the Alliance SwissPass in public transport, German only) provide travelcards, such as the GA travelcard or Half-Fare travelcard, in Switzerland. We also provide data for analyses in this area.

The most important data and interfaces

Do you have any more questions?

Then our FAQ will certainly help you. If you can’t find the right answer there, you can reach us via the contact form.

Further information

Mini sitemap

Route planner:

Timetable data:

Stopping and service points:

Line directory:

Road traffic data:


Shared Mobility:

  • Information on Vehicle Pooling (aka. Car Pooling, Ride Sharing, Carpooling, Carpooling, or Car Service Organisation, (rarely also Car Sharing)):

Operational & other: