Skip to content

actual information

What is the difference between real-time, forecast and actual information?

The terms are often used synonymously in different combinations. Real-time information is data that is produced and transmitted on an ad hoc basis. It may comprise planning, forecast and/or actual information.
Forecast information refers to the data calculated based on the current situation, e.g. arrival and departure time at/from the next stop.
Actual information refers to data on when and where services actually ran. This information is rarely available in real time and can usually only be generated retrospectively.

Problems with the character set when importing the CSV files in Excel

The CSV files are coded in UTF-8. This can cause problems when opening the CSV files «normally» in Excel because Excel assumes a different character set.

The following procedure can help here: Create an empty Excel sheet and then select Data / Get External Data / From Text in the menu. After selecting the file, in the next dialogue step you can enter «Unicode (UTF-8)» under File Origin.

Which transport companies provide real-time data?

You can find an overview here:
https://opentransportdata.swiss/de/dataset/go-realtime
The list contains all transport companies/business organizations for which real-time is available.

How exactly is “Halt auf Dem Demand” published in the actual data?

The topic of stopping on demand is a complex one. Because it is not the same operationally and commercially. Stephan Bundi speaks of the commercial part. This is an attribute that is added to the customer timetable. INFO+ is a commercially oriented product. Operationally there is no’maybe’ stop. Either stop or drive through, you have to be able to plan the routes. As a rule, a stop is taken into account on request as a normal stop. When the train passes through, it can wait at a station or signal. The other way around, he can’t drive any faster. So it’s planned with the stop.

Here the normal case, e.g. 13.2. or at the example 18549:

 unbenannt

unbenannt

Here the BLS (please always mention train numbers, not lines): Example 15732 Ziegelbrücke

unbenannt

  • One recognizes the stop on demand by the fact that ZBR has the same arrival as departure in the COMMERCIAL time (first column). It’s the only way to tell the time.
  • In OPERATING planning (second column) the stop is planned as normal as in MEP (Marin). There is no’maybe’.
    You can see from the stop code that the train only stops (and the LF), which is 14 instead of 11 as usual (in the service timetable)
  • If the train has really stopped or passed through, you can see by the DIFFERENCE between the DIFFERENCE (measured time), which is 22 seconds late here and then suddenly 36 seconds early. That means the train went through there. There is no flag for easy query!
  • To make it more complicated: The train did not leave MEP (Marin) about 49 seconds too early. The graphic above shows the PROGNOSE. There is then the whole thing again with the ACTUAL values. There the train in Marin waits for the planned departure.