IL:overlapRelease

From railML 3 Wiki
Revision as of 20:49, 29 January 2020 by Documentation (talk | contribs) ({{examples}}: Tutorial)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Introduction

Documentation

Syntax

Autoexport from the XML-Schema for element IL:overlapRelease of railML® version 3.2
Documentation Overlap is set in lockstep with the route. The interlocking releases the overlap when it is safe to presume that an approaching train will not overrun a closed destination signal. When the train occupied the last section (or destination area), an overlap release timer starts running. The timer value is defined by operational rules and the approaching speed. Upon expiry, the interlocking releases the overlap. Overlap is released together with the route or after expiration of the release timer. Overlap is released after a defined time in a timer that starts from a timerTriggerPoint.
Subschema interlocking
Parents* overlap
Children any (0..*), designator (0..*), overlapReleaseTimer (1..*), releaseTriggerSection (0..1)
Attributes:
  • id: unique identifier (optional; xs:string; patterns: (urn:uuid:)?[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}|\{[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}\})
*Notice:
Elements may have different parent elements. As a consequence they may be used in different contexts.
Please, consider this as well as a user of this wiki as when developing this documentation further.
Aspects that are only relevant with respect to one of several parents should be explained exclusively in the documentation of the respective parent element.

Autoexport from the XML-Schema for element IL:overlapRelease of railML® version 3.1
Documentation Overlap is set in lockstep with the route. The interlocking releases the overlap when it is safe to presume that an approaching train will not overrun a closed destination signal. When the train occupied the last section (or destination area), an overlap release timer starts running. The timer value is defined by operational rules and the approaching speed. Upon expiry, the interlocking releases the overlap. Overlap is released together with the route or after expiration of the release timer. Overlap is released after a defined time in a timer that starts from a timerTriggerPoint.
Subschema interlocking
Parents* overlap
Children any (0..*), designator (0..1), overlapReleaseTimer (1..*), releaseTriggerSection (0..1)
Attributes:
  • id: unique identifier (optional; xs:ID; patterns: (urn:uuid:)?[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}|\{[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}\})
*Notice:
Elements may have different parent elements. As a consequence they may be used in different contexts.
Please, consider this as well as a user of this wiki as when developing this documentation further.
Aspects that are only relevant with respect to one of several parents should be explained exclusively in the documentation of the respective parent element.

Semantics

Best Practice / Examples

The automatic release of an overlap after use is detailed in <overlapRelease>. The interlocking typically releases the overlap when the train approaching the destination signal has plausibly stopped. This is assumed a pre-set time after the train has either occupied or vacated a trigger section. Typically, the overlap release timer starts when the train occupies the section ending at the destination signal. Alternatively, the interlocking may release the overlap immediately or with a short delay after the train positively confirms to have stopped, e.g. by means of an ETCS position report.

The information for overlap release is described as follows:

  • <releaseTriggerSection> – This is the reference to the TVD section which is used as trigger for the overlap release.
  • <overlapReleaseTimer> – This details the timing for the overlap release.
  • @timer – The time that has to be elapsed after the trigger and before the overlap is physically released.
  • @overlapReleaseCondition – This defines the trigger condition for the release timer to start.
    • trainInitiatedTrigger – The release timer is triggered when the train has reported its halt.
    • startTimerAfterVacating – The release timer is triggered when the trigger section becomes clear after sequential occupation. Typically this refers to the section before the last one, i.e. the train has completely entered the last route section.
    • startTimerUponOccupation – The release timer is triggered when the trigger section becomes sequentially occupied. Typically this refers to the last section of the route.

The extract shows an overlap from signal 69A to the end of switch 69W03 inclusively. It is released after 60 s of occupation of the last track section in rear of signal 69A. The position of switch 69W03 in left is only check upon establishing the overlap.

<overlap id="ov01" overlapValidityTime="PT60S" overlapSpeed="0.0">
        <designator register="_SimpleRegister" entry="Overlap 69A-P2"/>
        <activeForApproachRoute ref="rt_sig02_sig04"/>
        <requiresSwitchInPosition mustOrShould="should" proving="oneOff">
                <relatedSwitchAndPosition inPosition="left">
                        <refersToSwitch ref="pt_swi02" />
                </relatedSwitchAndPosition>
        </requiresSwitchInPosition>
        <hasTvdSection ref="B03T"/>
        <hasTvdSection ref="B69W03T"/>
        <isLimitedBy ref="tde07"/>
        <overlapRelease id="ov01_rl">
                <designator register="_SimpleRegister" entry="ov01 Release"/>
                <releaseTriggerSection ref="X02T"/>
                <overlapReleaseTimer timerValue="PT60S" overlapReleaseCondition="startTimerUponOccupation" />
        </overlapRelease>
</overlap>

Additional Information

Notes

Open Issues