Home » railML newsgroups » railml.timetable » Extension suggestion for alternativeSectionTT (railML2, railML2.5, railML3 dev suggestion, nor:alternativeSectionTT)
Re: Extension suggestion for alternativeSectionTT [message #2545 is a reply to message #2544] Tue, 06 October 2020 12:49 Go to previous messageGo to previous message
Milan Wölke is currently offline  Milan Wölke
Messages: 139
Registered: April 2007
Senior Member
Hi all,

to keep you guys posted, this topic has been discussed in the last timetable developer telco. We decided to introduce a new element for the <ocpTT> named <alternativeSectionsTT>. Starting with railML 2.5 it will be possible to define alternative routes between the current and the following ocp along with a priority to help deciding which to choose if the default one specified as before with <sectionTT> does not seem appropriate anymore in operation. The idea here is that an alternative route does not impact the arrival and departure times of the followup stop.

The changes have been commited to the repository and can be viewed in the railML 2.5 development branch available here (https://svn.railml.org/railML2/branches/railML2.5-dev/).

Best regards, Milan

Milan Wölke – Timetable scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Attribute processStatus to be declared deprecated for <train>, <trainPart> and <trainGroup>
Next Topic: [railML2] Extension proposal: Stopping point reference for elements not of type <stopPost>
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Thu May 02 01:21:32 CEST 2024