| Re: [railML2] Scope of ocpTT.trainReverse [message #2866 is a reply to message #2865] |
Tue, 21 December 2021 11:22   |
Milan Wölke
Messages: 139
Registered: April 2007
|
Senior Member |
|
|
Hi Andrea,
after discussing this internally, we have come to the conclusion that in general that statement is correct. <ocpTT>.trainReverse does apply to the full train and it is expected that all train parts that are travelling alongside it have it set as well. There are a few borderline cases like for example a train that changes direction partially when being split at a station, but even then it is the full commercial train (one of the two being split there) that changes direction completely. Looking at the operational trains its also a true statement, either you model this with 3 operational trains, which would mean that none really reverses direction as they are all starting or ending. Alternatively you could model it with two operational trains then one of them starts the other may change direction, but if it does then it does so completely.
The argumentation is that a train cannot really partially change direction. Originally the attribute was introduced to encode that a change of direction occurs at a station in order to allow printing a "<->" symbol in train schedules. In this use case usually detailed formation information is missing and the attribute was intended to also allow encoding direction change in such cases.
I hope that helps. If it doesnt please dont hesitate to ask further.
Best regards, Milan
Milan Wölke – Timetable scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
Members
Search
Help
Login
Home
