Home » railML newsgroups » railml.timetable » Correct use of arrivalDay/departureDay
Re: Correct use of arrivalDay/departureDay [message #660 is a reply to message #658] Thu, 15 September 2005 08:14 Go to previous message
Daniel Huerlimann is currently offline  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
 
Read Message
Read Message
Read Message
Previous Topic: operatingDay
Next Topic: Proposal for new timetable schema version 2.0(?)
Goto Forum:
  


Current Time: Fri May 17 03:59:21 CEST 2024