Home » railML newsgroups » railml.timetable » Extension suggestion for alternativeSectionTT (railML2, railML2.5, railML3 dev suggestion, nor:alternativeSectionTT)
Re: Extension suggestion for alternativeSectionTT [message #2521 is a reply to message #2516] Tue, 25 August 2020 16:48 Go to previous messageGo to previous message
Jörg von Lingen is currently offline  Jörg von Lingen
Messages: 87
Registered: March 2016
Member
Dear all,

just for information we have already in interlocking the possibility to define
itineraries under controller element. Then any train in TT can refer to this
defined itineraries.


Best regards,
Joerg v. Lingen - Interlocking Coordinator
Am 24.08.2020 um 08:32 schrieb Stefan Hubrig:
> Hello,
>
> I support the idea of having alternative sections/itinerary
> in railML 3.x. There is more than one system which uses this
> for planning.
>
> Best regards,
> Stefan
  • Attachment: EA18.png
    (Size: 62.85KB, Downloaded 250 times)

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 04:13:31 CEST 2024