| Re: 1.1R2 - sectionTT element [message #688 is a reply to message #687] |
Mon, 05 January 2009 16:57   |
Joachim Rubröder railML
Messages: 0
Registered: November 2019
|
|
|
|
Hi,
sectionRefID is an ID and you should never parse an ID for included
information!
For your two stations "A-1" and "A-2", you have to take your two ocpTTs
with ocpRefId "A-1" and "A-2" for localisation. Now you have to search
your infrastructure for any connections between A-1 and A-2.
This connection from A-1 to A-2 (if there is any) might be part of a line
"70005" and a section "XY" in a line/section model used by a certain
program. So an export could add helpful references like sectionRefId="XY"
lineRefId="70005". But there is no rule how to define a sectionID. I just
invented one possible usage of a sectionID="85ZVIA-85ZWIP" for the
example.
So maybe its better not to use this attribute unless it has its
counterpart inside an infrastructure schema. Or you are transferring
timetable data between two programs with the same infrastructure model and
a sectionID, well known by both.
Kind regards,
Joachim
|
|
|
|
Members
Search
Help
Login
Home
