IS:speed signal

From railML 2 Wiki
Jump to navigation Jump to search


IS:speed signal
 


Scheme description / Schemenbeschreibung

Position of IS:speed signal in the XML-Tree / Position von IS:speed signal im XML-Baum

Multiplicity / Anzahl

[0..1]

Semantics / Bedeutung

Sub-element for defining a speed signal or panel

Attributes of IS:speed signal / Attribute von IS:speed signal

  • switchable: defining the signal to be switchable or fixed (panel)
  • kind: speed signal/panel kind (announcement, execution)
  • trainRelation: Reference to the part of the train from where on the signal is valid.

Syntactic Constraints / Syntaktische Beschränkungen

  • switchable: xs:boolean
  • kind: tSignalType (enumeration)
  • trainRelation: tTrainRelation (enumeration)

Best practice & Examples / Empfohlene Anwendung & Beispiele

Modelling of speed announcement and execution signals in railML® 2.3

With railML® 2.2 the signal subtype <speed> has been introduced. This allows a linking between the (physical) signal / panel that is standing outside next to the track with the (virtual) <speedChange> element where the speed information is given. Please note: the speed signal does not contain the speed information. Therefore, when modelling a physically signalised speed restriction or speed change, always both elements need to be modelled: the <speedChange> and the <speed> element of <signal>.

In the following example from Germany a speed restriction down to 20 km/h is announced and executed. The announcement is done by a panel “Lf6” and the execution is signalised by a panel “Lf7” (see German rulebook “Eisenbahn-Signalordnung (ESO)” at https://www.gesetze-im-internet.de/eso_1959/BJNR210220959.html (external link, 🇩🇪)).

The railML® syntax for a speed execution signal shall look like this:

<signal id="tr03_si04" pos="1900" absPos="2400" dir="up" ruleCode="DE:ESO:Lf7">
  <speed kind="execution" trainRelation="headOfTrain" switchable="false">
    <speedChangeRef ref="tr03_sc02"/>
  </speed>
</signal>

The referenced <speedChange> element is located at the same position like the speed execution signal and contains the speed information:

<speedChange id="tr03_sc02" pos="1900" absPos="2400" dir="up" 
             vMax="20" signalised="true"/>

The railML® syntax for the announcement of the speed restriction also references this <speedChange> element and shall look like this:

<signal id="tr03_si03" pos="1500" absPos="2000" dir="up" ruleCode="DE:ESO:Lf6">
  <speed kind="announcement" switchable="false">
    <speedChangeRef ref="tr03_sc02"/>
  </speed>
</signal>

The complete railML® 2.3 example of the speed announcement and execution signal looks like this:

<track id="tr03" ...>
  <trackTopology>
    ...
  </trackTopology>
  <trackElements>
    <speedChanges>
      <speedChange id="tr03_sc02" pos="1900" absPos="2400" dir="up" 
                   vMax="20" signalised="true"/>
    </speedChanges>
  </trackElements>
  <ocsElements>
    <signals>
      <signal id="tr03_si03" pos="1500" absPos="2000" dir="up" ruleCode="DE:ESO:Lf6">
        <speed kind="announcement" switchable="false">
          <speedChangeRef ref="tr03_sc02"/>
        </speed>
      </signal>
      <signal id="tr03_si04" pos="1900" absPos="2400" dir="up" ruleCode="DE:ESO:Lf7">
        <speed kind="execution" trainRelation="headOfTrain" switchable="false">
          <speedChangeRef ref="tr03_sc02"/>
        </speed>
      </signal>
    </signals>
  </ocsElements>
</track>

To summarize: speed signs (e.g. panels, signals) are modelled by <signal><speed>. The speed change contains the speed information and is modelled in <speedChange>. It is referenced from the <signal><speed>.

References

Notes / Anmerkungen

Not yet described. / Noch nicht beschrieben.

Open issues / Offene Punkte/Pendenzen

Not yet described. / Noch nicht beschrieben.