Home » railML newsgroups » railML.infrastructure » [railML3] transfer times for connections (Request for modelling of transfertimes from platform to platform in context of connecting trains)
Re: [railML3] transfer times for connections [message #2929 is a reply to message #2857] Tue, 01 March 2022 11:18 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 continue this topic I have prepared a draft of what we could add in timetable:

https://forum.railml.org/userfiles/2022-03-01_railml_railml3-connectiontransfertimes.png

Basically we would add this directly below <timetable> as a list of <connectionTransferTime> elements. Each would refer to a startLocation and to a set of transferLocations. I used locationRef, platformEdgeRef and trackRef as values to identify the location because we are using exactly this set of values to identify where a train is stopping in timetable. As Dirk pointed out transfer times may change from time to time, thats why I added an optional reference to a timetable period to the <connectionTransferTime> element. The whole structure would look like this in XML:

<timetable>
  <timetablePeriods>
    <timetablePeriod id="ttp-1" startDate="2022-01-01" endDate="2022-06-30"/>
  </timetablePeriods>
  <connectionTransferTimes>
    <connectionTransferTime timetablePeriodRef="ttp-1">
      <startLocation locationRef="op-1" trackRef="tr-4"/>
      <transferLocations>
        <transferLocation locationRef="op-1" trackRef="tr-3" duration="PT3M"/>
        <transferLocation locationRef="op-1" trackRef="tr-2" duration="PT3M30S"/>
        <transferLocation locationRef="op-1" trackRef="tr-1" duration="PT4M"/>
        <transferLocation locationRef="op-2" duration="PT7M"/> <!--some nearby OP, no matter which track over there-->
      </transferLocations>
    </connectionTransferTime>
    <connectionTransferTime timetablePeriodRef="ttp-1">
      <startLocation locationRef="op-2"/>
      <transferLocations>
        <transferLocation locationRef="op-1" trackRef="tr-4" duration="PT7M"/>
        <transferLocation locationRef="op-1" trackRef="tr-3" duration="PT5M"/>
        <transferLocation locationRef="op-1" trackRef="tr-2" duration="PT5M"/>
        <transferLocation locationRef="op-1" trackRef="tr-1" duration="PT5M"/>
      </transferLocations>
    </connectionTransferTime>
  </connectionTransferTimes>
</timetable>

Semantically the idea would be that this matric of transfertimes would be the basic configuration of transfer times. A connection can always specify a transfertime that is different from this and would override the basic configuration that way.

What do you think of this? If you have ideas on how to improve the modelling or have additional requirements that need considering, please let me know.

Thanks in advance.

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
Read Message
Previous Topic: [railML 3.2] "isSpeedSignal": Suggestion to delete the value "midOfTrain" of element "trainRelation"
Next Topic: [railML3] ETCS signal/panel
Goto Forum:
  

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

Current Time: Sun Apr 28 21:18:45 CEST 2024