| Passing times in timetable [message #694] |
Wed, 02 September 2009 16:35  |
at
Messages: 2
Registered: August 2013
|
Junior Member |
|
|
Hi everybody,
we are just working on a project concerning Intercity train traffic and
in the timetables of intercity trains we found some passing times
mentioned for intermediate stations. I am wondering how to put them in
railML.
I think that from an operational point of view, exact passing times
should be mentioned somewhere.
I suggest using an additional option for
eEntry/stopDescription : passing
and to define an additional attribute for
eTimetableentries/entry such as passingTime.
Or shall I use one of the tSection attributes? But this doesn't seem as
clear as putting them somewhere explicitely.
Regards
Thomas
--
________________________________________________
Dr.-Ing. Thomas ALBRECHT
Technische Universität Dresden
Institut für Verkehrstelematik
Lehrstuhl für Verkehrsleitsysteme und -prozessautomatisierung
01062 Dresden
|
|
|
|
| Re: Passing times in timetable [message #695 is a reply to message #694] |
Fri, 04 September 2009 11:12  |
Joachim Rubröder railML
Messages: 0
Registered: November 2019
|
|
|
|
Hi Thomas,
a passing time (at which the train passes the operation control point) is
typically mentioned as normal "departure" time for the entry. The
attribute type="pass" (V 1.1) or ocpType="pass" (V2.0) indicates, that
there is no stop at this station. But if you think of a passing time in
the sense of "a duration for passing a station", we would need a new
attribute.
By the way, I'm thinking of a redesign of all the confusing different
"times" attributes in railML 2.0:
"times"
as subelement of an entry (V1.1) = ocpTT (2.0) would contain all kinds of
arrival and departure times (published, calculated, earliest, ...)
"stopTimes"
as subelement of a "stopDescription" would contain all kinds of stopping
durations
- minimal stop time (minStopTime)
- operational stop time reserve (opStopTimeReserve = addStopTime in
V1.1), could be used for "stop on demand"
- additional stop time reserve (addStopTimeReserve = supStopTime in V1.1)
- shuntingTime (new, needed for rostering)
- clearance time (new)
"runTimes"
as subelement of a "sectionTT" would contain all kinds of running
durations between ocpTTs, beginning at this ocpTT
- minimal run time (minRunTime)
- operational run time reserve (opRunTimeReserve = addRunTime in V1.1),
typically containing maitenance reserves
- additional run time reserve (addRunTimeReserve = supRunTime in V1.1),
for other purposes e.g. cadencial timetables
do you think, this would be more understandable and reasonable?
Kind regards,
Joachim
--
Joachim Rubröder
Schema Coordinator: railML.timetable
|
|
|
|
Members
Search
Help
Login
Home
