| [railML 3] Qualifier for train times [message #4006] |
Tue, 19 May 2026 08:10  |
David Lichti
Messages: 57
Registered: December 2020
|
Member |
|
|
Hi all,
We (Hacon) are currently looking into a way to distinguish different qualities of a train schedule's (stop:times and pass:times). While our runtime calculation can automatically derive all these times for a given itinerary, our tool also allows the planner to manually set and fix selected arrival/departure/pass times.
In railML 2, this could be expressed with times@scope="calculated". Though this was mutually exclusive with the values operational/commercial in the same attribute.
In railML 3, the enumeration for the times@scope attribute has only the values operational and commercial. Additionally, our TPS.plan allows to fix arrival and/or departure times independently of each other. So, the times element would not have the sufficient granularity.
We suggest to add an attribute like quality to the arrival, departure and passingTime elements. It should support values like calculated and fixed.
[Updated on: Tue, 19 May 2026 08:11] Report message to a moderator |
|
|
|
Members
Search
Help
Login
Home
