Mandatory stop at level crossing (de: Zwangshalt am BÜ)
Description
There are sometimes local requirements to stop a train in front of a level crossing. Train staff has to protect the train run against the individual traffic on the street.
The German words for this szenario are: "Halt mit Sicherung durch Zugpersonal".
We can introduce a stop attribute in the levelCrossing element with a boolean type.
Additionally the timetable may mark this level crossing with a "non-commercial" stop (ocp).
Links
- Forum discussion:
- Susanne Wunsch, November 2012: https://www.railml.org/forum/index.php?t=msg&th=120&goto=444&#msg_444
- Christian Rahmig, 04.10.2024: https://www.railml.org/forum/index.php?t=msg&th=981&goto=3330&#msg_3330
- Gitlab tickets:
- Wiki documentation:
- railML 2 - SpeedChange: http://wiki.railml.org/index.php?title=IS:speedChange
- railML 3 - IS:stoppingPlace: https://wiki3.railml.org/wiki/IS:stoppingPlace
Proposed solution for railML 2.4
Mandatory stops shall be modelled using <speedChange>@mandatoryStop="true"
. Whether the mandatory stop is signalized or not, shall be indicated by using <speedChange>@signalised
. Further, a <signal>
shall be modelled to reference the <speedChange>
:
<signal><speed><speedChangeRef ref=""/>
Proposed solution for railML 3.x
In order to suit to all different types of use cases it was suggested to have an independent object for a railway vehicle stopping place, which can be referenced by different other elements.
This element is existing: //functionalInfrastructure/stoppingPlaces/stoppingPlace/
Currently, this stopping place is not explicitly linked with a level crossing.