| Re: Ocp Timezones [message #261 is a reply to message #260] |
Tue, 17 May 2011 07:07   |
Joerg von Lingen
Messages: 148
Registered: May 2011
|
Senior Member |
|
|
Hi everybody,
although it is not relevant for rolling stock I would add some thoughts on daylight saving time.
1) A simple flag (boolean) can only be used in timetable as it has a meaning only in relation to a
certain date.
2) The information is a "feature" of an ocp, however, it has to be much more detailed in order to be
valid in general for an infrastructure item independent of any date. Subsequently it would require
to name start and end date/time of the daylight saving period for each year as this may be subject
to changes.
But do we really need that information?
Regards,
Jörg.
Christian Rahmig wrote:
> Hello Tuomas,
>
>>> Time changes that are only temporarily, e.g. daylight saving time, are
>>> not considered in this list and shall not be used in the infrastructure
>>> schema.
>>
>> Could there be some solution for daylight saving time implemented? One
>> option would be boolean like "OCPinDaylightSavingArea", or what would be
>> the preferred way to know if OCP obeys daylight saving time or not?
>> Comments, please.
>
> That is a difficult question. In my understanding the daylight saving time resp. the boolean you
> suggested is a changing parameter and not fixed like the timezone information of an ocp. Therefore,
> I would not consider it within the infrastructure schema, but somewhere in the timetable schema,
> since it is relevant for operation and depends on the current date/time.
>
> However, I want to hear Joachim's opinion on this first before implementing it.
>
> Best regards
> Christian
>
> ---
> Christian Rahmig
> railML.infrastructure coordinator
|
|
|
|
Members
Search
Help
Login
Home
