Level crossing characteristics (de: BUe-Eigenschaften)
Description
The levelCrossing element may be enhanced by a number of special characteristics.
The attribute protection has to be clarified.
- Ideas from Volker Knollmann on a Wiki page: "Clearness detection of the LX (Radar, visual)? Or "selbstüberwacht" ("Überwachungssignal") vs. block protected ("HP")? "
Background
Links
- Forum discussion
- Christian Rahmig, 08.03.2018: [https://www.railml.org/forum/index.php?t=msg&goto=1714&&srch=level+crossing#msg_1714]
- Christian Rahmig, 20.08.2018: [https://www.railml.org/forum/index.php?t=msg&goto=1916&&srch=level+crossing#msg_1916]
- Trac tickets
- Wiki documentation
- (railML 3 wiki not yet available)
Proposed solution in railML 3.x
In railML 3.1 the technical protection infrastructure of the level crossing is described in the child element .
The attribute @supervision is used to specify the supervision of the correct functioning of the level crossing. Possible values are infrastructureAutomatic (e.g. self-protected "ÜS"), infrastructureManual (e.g. by block protection "HP"), trainManual and none.
The attribute @activation is used to define how the technical closing of the level crossing is being triggered. Possible values are infrastructureAutomatic, infrastructureManual (e.g. a dispatcher closing the LX), trainAutomatic (e.g. train passing a switch-on contact), trainManual and none.
The attribute @obstacleDetection is used to define how the clearness detection at the level crossing is being done. Possible values are automatic (e.g. by a radar), manual (e.g. by local staff looking) and none.