Home » railML newsgroups » railml.timetable » dayOffset vs. arrival/departureDay
Re: dayOffset vs. arrival/departureDay [message #881 is a reply to message #880] Mon, 12 November 2012 16:50 Go to previous messageGo to previous message
Susanne Wunsch railML is currently offline  Susanne Wunsch railML
Messages: 0
Registered: January 2020
Dear Dirk and all,

Dirk Bräuer <dirkbraeuer(at)irfpde> writes:

> in March 2012 we have created the <operatingPeriod>.dayOffset
> attribute. The original thought was to allow bitmasks with one or more
> digits than the there are days in the period. This was to describe a
> midnight-overrun before the station where the bitmask relates to.
>
> Since then, I have written some strange explanations at [1] and
> elsewhere but I am not satisfied with the redundancy which comes with
> <operatingPeriod>.dayOffset. With implementation, it becomes once more
> clear that it is always possible to avoid
> <operatingPeriod>.dayOffset>0 by using the already existing
> arrival/departureDay even at the first <ocpTT> of a <trainPart>. Even
> more worst, dayOffset leads by trend to define every
> <operatingPeriod> several times, one with dayOffset=0 and one with
> dayOffset=1 a.s.o.

I try to recover why we introduced that attribute although the above
mentioned "redundancy". Please correct me!

* If there are several train parts running long distances (over one or
more midnights) and are coupled with other train parts for building
some trains, how to define which 'departureDay' should one train part
take? Do all train parts start with departureDay="0" never mind when
another train parts started with whom it is coupled on the way?

(If not, we would have huge problems, I mean.)

* If the train part goes over midnight at the last day of its operating
period. It would operate on a day where it is not allowed by its
operating period.

The operating period gives the dates when the train part starts, the
'dayOffset' gives the count of days which the train runs over
midnight. It only shifts the planned operation days.

Of course, the departureDay/arrivalDay attributes of the ocpTTs during
the run should count from cero up to the 'dayOffset' value.

Why to start a train part with departureDay="1"?

> [1] http://wiki.railml.org/index.php?title=TT:times#notes

Thanks for the wiki documentation. :-)

Kind regards...
Susanne

--
Susanne Wunsch
Schema Coordinator: railML.common
 
Read Message
Read Message
Read Message
Previous Topic: Sequence of ocpTT elements
Next Topic: Re: A train with ETCS?
Goto Forum:
  


Current Time: Tue May 14 04:15:32 CEST 2024