| Correct use of arrivalDay/departureDay [message #655] |
Thu, 01 September 2005 11:57  |
tobias
Messages: 8
Registered: April 2005
|
Junior Member |
|
|
I have two questions regarding the correct use of arrivalDay and
departureDay in the entry element, which I feel are not sufficently
explained in the documentation. The description says "indicating an
arrival/departure after midnight on day n".
Q1: On which day is the train considered to start, on day 0 or on day 1?
Q2: If a train passes midnight, should the arrivalDay and departureDay
attributes be repeated for each subsequent entry element?
My guess is that the answer to Q1 is that the train starts on day 1 and
the answer to Q2 is yes, but I cannot tell from just reading the
documentation.
|
|
|
|
|
|
| Re: Correct use of arrivalDay/departureDay [message #660 is a reply to message #658] |
Thu, 15 September 2005 08:14  |
Daniel Huerlimann
Messages: 17
Registered: September 2004
|
Junior Member |
|
|
In article <dg97rp$jrd$1(at)sifaivifhgde>, jrubroeder(at)sma-partnerch
wrote:
> The arrivalDay / departureDay was meant as offset.
> Any train starts on day 0 (Q1). Without arrivalDay-attributes, everything
> is regarded as the same day = day 0.
> After midnight, any further atrribute arrivalDay and departureDay should
> be set to 1 (Q2) .
> The duration between start and arrival can be calculated as: "arrival +
> (arrivalDay * 24h ) - start".
>
> I thought that an arrivalDay = 1 should be repeated. But I like the idea
> of Dani, that an intelligent importing program sticks to day 1until the
> appearance of arrivalDay >= 2 and is able to deal with or without
> repetition.
>
> But you are right, I'll try to fix this point in the documentation.
>
> Best regard,
> Joachim
Thank you very much for your answer, Joachim. It is clear now so that I
can start implementing....
Best regards
Dani
|
|
|
|
Members
Search
Help
Login
Home
