| Re: dayOffset vs. arrival/departureDay [message #882 is a reply to message #881] |
Mon, 12 November 2012 20:10  |
Dirk Bräuer
Messages: 311
Registered: August 2008
|
Senior Member |
|
|
Dear Susanne,
> I try to recover why we introduced that attribute although the above
> mentioned "redundancy". Please correct me!
> * 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.
That was the original thought behind it, as I explained in my sentence:
>> The original thought was to allow bitmasks with one or more
>> digits than the there are days in the 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.
Yes. departureDay>0 would do the same.
Well, I did not wanted to start a big discussion again. I only wanted to
tell that <operatingPeriod>.dayOffset _can_ be avoided by using
departureDay="1" at the first <ocpTT> - believe me.
If you want to keep both attributes anyway - no problem, just redundancy.
Best regards,
Dirk.
|
|
|
|
Members
Search
Help
Login
Home
