Home » railML newsgroups » railml.timetable » 1.1R2 - sectionTT element
Re: 1.1R2 - sectionTT element [message #687 is a reply to message #686] Mon, 05 January 2009 14:33 Go to previous messageGo to previous message
Teemu Sirkiä is currently offline  Teemu Sirkiä
Messages: 5
Registered: December 2008
Junior Member
"Joachim Rubröder" <coord(at)timetablerailmlorg> kirjoitti viestissä
news:gjslp9$oo9$1(at)sifaivifhgde...
> Dear Teemu,
>
> the sectionTT element is meant for information concerning the section
> between two ocpTTs of a train. The two attributes sectionRefId and
> lineRefId are referencing section and line elements which are part of the
> infrastructure. Unfortunately there is no such section element in the
> infrastructure yet but I think there should be one. So I invented the
> usage sectionRefId="85ZVIA-85ZWIP" with a combination of two ocp elements.
> But it is still a RefId so it depends on the definition of a section.
>
> With the current structure of the infrastructure I agree that a
> combination sectionStartID/sectionEndID would fit better. But I hope that
> there will be soon a section concept in the infrastructure.
>
> What do you think as best connection between timetable and infrastructure
> by references? How would you describe a whole network with high-level
> connections from station to station in the terms of railML-infrastructure?

I understand that sectionRefId is an ID but I was just thinking how to parse
a RaiML file containing timetable with current structure.

As I said, there is no documentation how that ID is generated. Can I assume
that it is always two ocpRefIds combined with "-" character? If it is so
then it is easy to get for example trackInfo between two ocpTTs and there is
no problem.

But then the other part. What if I want to find train's departure and
arrival times in particular section defined by sectionRefId. I can split
sectionRefId attribute and find those two ocpTT having splitted parts of
sectionRefId as their ocpRefId if and only if sectionRefId contains only one
"-" character.

Let's assume that I have two stations: "A-1" and "A-2". Now I have two
ocpTTs with attributes ocpRefId "A-1" and "A-2". Again, this is not a
problem but then my sectionTT would have sectionRefId attribute "A-1-A-2".
Now there are three options how I can split that back: "A and 1-A-2", "A-1
and A-2" and "A-1-A and 2". How can I know which is the correct form? This
is the reason why I don't like this structure.

Maybe there should be sectionRefId that references to that section and also
startID and endID that references to ocpTT's ocpRefId attribute?

I hope you understood my point and and the reason why I'm worried about it.

-Teemu

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
Previous Topic: new draft V1.1-R2
Next Topic: Passing times in timetable
Goto Forum:
  

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

Current Time: Tue May 14 11:32:07 CEST 2024