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 #2383 is a reply to message #2382] Mon, 09 March 2020 21:44 Go to previous messageGo to previous message
Dirk Bräuer is currently offline  Dirk Bräuer
Messages: 311
Registered: August 2008
Senior Member
Dear coordinators,

> But before we dive into modelling, let's ask the most
> important question: Who needs this information and for which
> purpose / application?

The minConnectionTime is needed
- as an input to the construction phase of a timetable to define the minimum time difference between arrival and departure to secure a connection,
- for a given timetable in the reverse sense, to calculate which connections can be reached / are offered and which not,
- in the operational phase to calculate prognoses due to late running while maintaining connections.

It is neither an infrastructure nor a strict timetable value; we rather regards it as a traffic-preset value. But for instance, calender data (timetable and operating periods) are the same character of information and in railML are assigned to <timetable>, so I also would assign them to timetable.

> From what I understand, the transfer time is a (static)
> information that describes the time needed to get from one
> platform to another one. This means, that the information
> should be connected to a <platform> element? And for each
> platform the information occurs several times
> (#platforms-1).

The information is not strictly static; it may change from time to time. It is typically static for a timetable period, which again is an argument to assign it at or somewhere near timetable periods.

Yes, it can be assumed to a matrix (#platforms x #platforms-1), but typically it can be eased with only 2-3 actually different values per station: 1) same platform, 2) near platform, 3) far platform (often no difference between 2-3).

So, a complete description could be something like:
<minConnTimes default="5" [mins]>
<minConnTime fromPlatformRef="pltf_1" time="3" [mins]>
<toPlatform ref="pltf_2a">
<toPlatform ref="pltf_2b">
<toPlatform ref="pltf_4">
<\minConnTime>
<\minConnTimes>

The attribute <minConnTimes>@default would apply for all combinations which are not mentioned.

Since <platform>@id's are unique in all the railML file, the <minConnTimes> list would not need to be placed at a certain <ocp> nor <platform> and can be placed at <timetable>. This allows giving <minConnTime>s which for connection between two <ocps>, as it would be necessary between two <ocp>s belonging to the same station (e. g. Berlin Hbf unten / oben / S-Bahn) or which are very close (Nordhausen <-> Nordhausen Nord).

Dirk.
 
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:
  


Current Time: Fri Mar 29 09:40:02 CET 2024