Home » railML newsgroups » railml.interlocking » Switch/Derailer/Crossing in Overlap requires a position ("inPosition" attribute either optional or needs an additional state)
Switch/Derailer/Crossing in Overlap requires a position [message #3108] Tue, 25 July 2023 14:30 Go to previous message
heidrun.jost@thalesgroup. is currently offline  heidrun.jost@thalesgroup.
Messages: 5
Registered: December 2022
Junior Member
Dear all,

for the route overlap definition, a position is required for a switch/derailer/crossing in an overlap.

But sometimes this position is not available, because a) the overlap ends before the heart or b) does not matter.

Using only the TvdSection is not a solution, because it could include several switches/derailers/crosings, which would then be to much.

<overlap id="IL_FMkw4WGpByf8V0i0u539i9" length="55">
<designator register="_costId" entry="Overlap:BGS_MR#1564"/>
<relatedSwitchAndPosition inPosition="right">
<refersToSwitch ref="IL_Z8wATeoLQQL7NLmHuC2c8Ca"/>
<hasTvdSection ref="TVD_Z8wATeoLQQL7NLmHuC2c8Ca"/>

So the parameter "inPosition" shall become either optional or provide an additional option for these cases.

Best regards,
Heidrun Jost
Data Manager TMS Norway
Ground Transportation Systems

Phone: +49 (0) 30 688306 423
Schützenstr. 25 10117 Berlin Germany
Read Message
Read Message
Previous Topic: [railML3] railway signal documentation, schema improvement
Next Topic: Definition of Emergency Stop Area for railML 3.3
Goto Forum:

Current Time: Tue Jul 23 13:32:35 CEST 2024