| Re: The correct use of trackRef under sectionTT [message #2376 is a reply to message #2336] |
Mon, 09 March 2020 12:20  |
Dirk Bräuer
Messages: 311
Registered: August 2008
|
Senior Member |
|
|
Dear Torben,
> For a macroscopic model with only a main track with or without station tracks there is no alternate path to choose from. So, do not use <sectionTT> as it does not give any added value.
I don't agree. We still use <sectionTT> in a macroscopic model
- to encode the line in case of parallel lines (attribute @lineRef),
- to encode the line-side track in case of double-track lines (sub-element <trackRef>),
- to encode the run times (sub-element <runTimes>),
- to encode the run time supplement (attribute @percentageSupplement)
and more.
> In the seldom case that there exist two lines between two
> OCP's with no intermediate OCP in between...
This is by far not a seldom case in Germany and other countries. How many examples should I describe...? ;-)
> ...unambiguous definition of the path of a sectionTT...
I am afraid I doubt that there will be an unambiguous definition by railML in general since we've learned the definition of what is a "station" is highly controversial. May be we can clarify it by some use cases of railML, ok.
For instance, in your example sketch, I see the following possibilities:
a) No description of the route in station B in a macroscopic model (as you mentioned it),
b) Station B is split into several (two) <ocp>s for timetabling,
c) Encode the detailed way through station B by using a route identification at <ocpTT>.@trackInfo.
Solution (b) may sound strange, but this is a very common solution for that problem for instance in Germany and other countries.
I want to point out that, in my opinion,
- <sectionTT>.<trackRef> is only intended to encode the track _between_ stations (<ocp>s) - not the tracks inside stations. That's why it is located at <sectionTT> - everything at <sectionTT> should concern the section between stations (<ocp>s).
- the route inside stations (<ocp>s) must be described, if necessary, by other attributes or elements - for instance <ocpTT>.@trackInfo or some more precise, standardised solution of future railML.
Best regards,
Dirk.
|
|
|
|
Members
Search
Help
Login
Home
