Home » railML newsgroups » railml.timetable » [railML2] Usage of //ocpTT/times/@scope
Re: [railML2] Usage of //ocpTT/times/@scope [message #2497 is a reply to message #2492] Thu, 16 July 2020 17:50 Go to previous messageGo to previous message
Mario Kröplin is currently offline  Mario Kröplin
Messages: 2
Registered: January 2018
Junior Member
For the purposes of passenger information, we distinguish the following types of times
(inspired by SIRI and Transmodel):
- scheduled (long-term planning)
- aimed (short-term planning)
- expected (forecast for delays)
- actual (detected arrival or departure time)

Currently, our use of railML ends with (very) short-term planning.
This means that we do not transmit expected times and actual times via railML.

The aimed times are the scheduled times of the corresponding train in a separate timetable (short-term planning).

By the way: extensions are used to express cancellations and extra stops explicitly in this separate timetable. A comparison with the annual timetable is therefore only needed to determine the aimed times and the aimed tracks.

The published times are usually rounded scheduled times. But since we also need rounded expected times, we ignore published times and do the rounding on our own.
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: @categoryPriority of <category> to be declared deprecated in version 2.5
Next Topic: railML3: definition of vehicle
Goto Forum:
  


Current Time: Sun May 05 14:29:17 CEST 2024