Home » railML newsgroups » railml.timetable » Delay Causes Representation in RailML
Re: Delay Causes Representation in RailML [message #829 is a reply to message #828] Thu, 18 October 2012 11:27 Go to previous messageGo to previous message
Dirk Bräuer is currently offline  Dirk Bräuer
Messages: 311
Registered: August 2008
Senior Member
Dear Susanne,

ok, I understood that

>>> <delayCause id="dc1" time="17:12:00Z" date="2012-10-14"

is not the date of the delay but the date of the cause. So it is not
redundant to "planned arr/dep" + "delay arr/dep" and I do not need to fill
it.

Ok, sorry for the misunderstanding - subject is closed from my side.

---
>> At least, this means to document that <trains>/<trainParts>
>> which a 'scope="actual"' do need an <operatingDay> for only one day
>> (bitMask with only one '1').

> I would expect that the whole railML file either covers planning data or
> "actual" (running) data. AFAIK the SBB saves all "actual" timetable data
> of a day in a single railML file.

This is very important. I think we should fix it either in a general
attribute or at least in Wiki.

Best regards,
Dirk.

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: reference from timetable's <stopDescription> to infrastructure's <stopPost>
Next Topic: Internationalized 'messageText' in 'connection'
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Sun May 26 11:17:44 CEST 2024