Extend definition of <switch> and <crossing>
Description
Current implementation of switch and crossing is missing parameters for specifying operational / interlocking related details. In particular, it is missing:
- to indicate where the switch is being operated: remotely or locally
- to indicate whether the switch tongue positions are observed remotely
- to reference a keylock that locks the switch in a certain position
- the distance between the switch location (@pos) and the position of the switch clearance point
Background
This ticket was raised by Norway as part of the standardisation in Norway and shall be used commonly in the future.
Both, switches and crossings, are physical infrastructure elements, which connect tracks and are modelled in the same way in railML2.4nor. They are sub-elements to , which belongs to .
and have been expanded to included clearer definitions in order to better define the tracks and make the definitions of switches clearer.
Furthermore, both and contain the sub-element , which has also been given a clearer definition in railML2.4nor.
For more details see document “railML2.4nor Infrastructure Documentation“ (https://www.jernbanedirektoratet.no/railML), version 1.3, 03.07.2020, point 4.3.
Links
- Forum discussion:
- Torben Brand, 20.12.2016: [https://www.railml.org/forum/index.php?t=msg&th=485&goto=1459&#msg_1459]
- Trac tickets:
- #423 (closed)
- Wiki documentation:
- IS:switch: [http://wiki2.railml.org/wiki/IS:switch]
- IS:crossing: [http://wiki2.railml.org/wiki/IS:crossing]
Proposed solution in railML 2.5
remote operation and observation
It is suggested to extend and with attributes for indicating place of switch operation:
- @remoteOperated (boolean) to indicate if the switch is operated from a remote location.
- @remoteIndicated (boolean) to indicate that the switch tongue positions are communicated and observed from remote. Both parameters should be used together.
reference to keylock
It is suggested to add an explicit reference from and to a using @lockRef (tGenericRef) analogue as already defined for the reference to the .
distance to clearance point
The switch and the crossing are currently located via a single coordinate defined by @pos. In order to specify the distance between this point and the switch clearance point, it is suggested to introduce @clearancePosOffset (tLengthM). This value is always positive.