Home » railML newsgroups » railml.timetable » Sequence of ocpTT elements
Re: Sequence of ocpTT elements [message #803 is a reply to message #802] Thu, 31 May 2012 13:43 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 and Andreas,

> Other/same opinions?

From my side, it is up to the reading software
- either to sort the times chronologically
- or to declare that OCPTTs have to be ordered on input (additionally to
RailML).

I do not see a big problem in the additional declaration. I think that
there always will be additional demands on the softwares dealing with
RailML.

Actually, we currently have arrival/departure times which come sometimes
in a non-sorted order (from an Austrian Infrastructure Company) for
reasons which I do not know. We sort them on input and refuse the input if
there are two with the same time. It is up to the data source to secure
data integrity.

From our side, a kind of "ordering index" as an additional attribute does
not change the situation very much: Either we sort by arrival/departure
times and refuse if there are two OCPTTs with the same times or we sort by
index and refuse if there are two OCPTTs with the same index...

If you consider introducing a new "ordering attribute", may be a "running
length" (meters calculated from the beginning of train's route) would be
solution which also allows a unique order but includes the additional
value of the distances which many reading programmes want to have and
which otherwise can only be calculated more difficulty.

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: Datatype for distance in sectionTT
Next Topic: dayOffset vs. arrival/departureDay
Goto Forum:
  

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

Current Time: Sun May 19 20:08:52 CEST 2024