| Re: [railML3] Semantics of the attributes arrivalDay and departureDay [message #2637 is a reply to message #2628] |
Mon, 18 January 2021 07:52   |
David Lichti
Messages: 13
Registered: December 2020
|
Junior Member |
|
|
On one hand, I think trains should be identified by explicit identifiers, not implicitly by their schedule.
But appart from identification, there is also the problem that many train line operations do not align with the 00:00-24:00 cycle. Actual operating times may rather resemble 05:00-01:00 or 04:00-02:00, where the latest trains of a given operating day actually run on the next calendar day. Rather than defining custom day cycles (which might differ between different lines in the same file, anyways), such trains could be modeled by having their first departure shifted by one day.
In example 2, it could also be necessary to have the train leave earlier at its first station, moving the departure from shortly after midnight to shortly before midnight. In this case, it would be desirable to even have negative integers as day offsets.
Best regards
David
|
|
|
|
Members
Search
Help
Login
Home
