IL:overlap

From railML 3 Wiki
Jump to: navigation, search

Introduction

Documentation

Syntax

Autoexport from the XML-Schema for element IL:overlap of railML® version 3.2
Documentation track(s) in advance of a stop signal, or a stopping point in a continuous signalling system, which must be kept clear to avoid the risk of collision should a train inadvertently run past the signal or the stopping point
Subschema interlocking
Parents* overlaps
Children activeForApproachRoute (0..*), any (0..*), belongsToOperationalPoint (0..*), designator (0..*), hasCommand (0..*), hasIndication (0..*), hasTvdSection (0..*), isLimitedBy (0..*), objectName (0..*), overlapRelease (0..1), relatedToTrackAsset (0..1), requiresLevelCrossingInState (0..*), requiresSwitchInPosition (0..*)
Attributes:
  • releaseSpeed: Release speed in km/h associated with the overlap (optional; xs:decimal),

  • overlapSpeed: Maximum speed in the overlap in km/h for other trains than the one using the related route. (optional; xs:decimal),

  • overlapValidityTime: The overlap validity time is the time that the train assumes the overlap to be locked. This is the ETCS validity time T_OL. (optional; xs:duration),

  • length: Alternatively to a particular limit the length of the overlap in metres can be given. (optional; xs:decimal),

  • elementNumber: element number of the object for internal referencing in the engineering data (optional; xs:nonNegativeInteger),

  • 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:overlap of railML® version 3.1
Documentation track(s) in advance of a stop signal, or a stopping point in a continuous signalling system, which must be kept clear to avoid the risk of collision should a train inadvertently run past the signal or the stopping point
Subschema interlocking
Parents* overlaps
Children activeForApproachRoute (0..*), any (0..*), designator (0..1), hasTvdSection (0..*), isLimitedBy (0..*), overlapRelease (0..1), relatedToTrackAsset (0..1), requiresLevelCrossingInState (0..*), requiresSwitchInPosition (0..*)
Attributes:
  • releaseSpeed: Release speed in km/h associated with the overlap (optional; xs:decimal),

  • overlapSpeed: Maximum speed in the overlap in km/h for other trains than the one using the related route. (optional; xs:decimal),

  • overlapValidityTime: The overlap validity time is the time that the train assumes the overlap to be locked. This is the ETCS validity time T_OL. (optional; xs:duration),

  • length: Alternatively to a particular limit the length of the overlap in metres can be given. (optional; xs:decimal),

  • 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

Overlap is a defined number of track sections in advance of a stop signal, or a stopping point in a continuous signalling system, which must be kept clear to avoid the risk of collision should the train inadvertently run past the signal or the stopping point.

Many IMs require overlap in advance of active routes to protect from overshoot. One or more sections in advance of the destination signal are locked out from use by other routes. The overlap is delimited by train detectors. Facing switches within the overlap are locked. Trailing switches in the overlap are may be not locked. Note that there is no need to explicitly identify the switches in the overlap because they can be derived from the begin and endpoints of the overlap. There may be several overlaps defined per destination signal.

The overlap can be released if the RBC deems that an approaching train is slow enough such that overshoot is unlikely.

Trains other than the one for which the route-overlap is locked may be attributed a permitted speed in the overlap. If the value is set to 0 it is not possible to set a route through the overlap. Compare this variable with the release speed that applies to the train that is being released beyond the danger point.

The overlap element can have the following information:

  • @overlapValidityTime – The overlap validity time is the time that the train assumes the overlap to be locked. This is the ETCS validity time T_OL.
  • @speedInOverlap – Maximum speed in the overlap in km/h for other trains than the one using the related route.
  • @releaseSpeed – Maximum speed in km/h for release from controlled braking curve when running towards the overlap. A release speed is a speed limit under which the train is allowed to run in the vicinity of the EoA (End of Authority: here routeExit or destinationPoint), when the target speed is zero. One release speed can be associated with the Overlap.
  • @length – The physical length of the overlap in metres can be given here as alternative to a particular track asset as limitation.
  • <activeForApproachRoute> – This is the reference to the related route using this overlap.
  • <relatedToTrackAsset> – This is the reference to the related track asset the overlap is connected to. This can be e.g. the destination signal of one or several routes.
  • <requiresAssetInPosition> – This is the definition of any movable element located within the overlap which is required to be in a certain position. For details refer to chapter 1.1.15above.
  • <hasTvdSection>- The list of references to the TVD sections within the path of this overlap. It is preferred to have an ordered list beginning at <routeExit>, however this cannot be enforced.
  • <isLimitedBy> – This is the reference to train detection element limiting the overlap. It can be more than one limiting element. It shall be used in conjunction to @length.
  • <overlapRelease> – This defines the way of automatic release of overlap after use.

Additional Information

Notes

Open Issues