Introduction
Documentation
Syntax
Autoexport from the XML-Schema for element IL:overlap of railML ® version 3.3 |
| 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..*), additionalRelation (0..*), belongsToOperationalPoint (0..*), designator (0..*), elementState (0..*), hasCommand (0..*), hasIndication (0..*), hasTvdSection (0..*), isLimitedBy (0..*), objectName (0..*), overlapRelease (0..1), relatedToTrackAsset (0..1), requiresLevelCrossingInState (0..*), requiresSwitchInPosition (0..*)
|
Attributes:
- length: Alternatively to a particular limit the length of the overlap in metres can be given. (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),
- overlapTimerStartLocation: Distance from the overlap timer start location to the End of Movement Authority in metres (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),
- releaseSpeed: Release speed in km/h associated with the overlap (optional;
xs:decimal),
- releaseSpeedSource: Allows specifying that the release speed may be taken from either an onboard calculation or the national values. (optional;
xs:string)
- Possible values:
- calculatedOnBoard: Indicates that the release speed for the danger point is calculated on board. Corresponds to the ETCS special value for M_RELEASEDP of 126
- nationalValues: Indicates that the release speed for the danger point is taken from national values. Corresponds to the ETCS special value for M_RELEASEDP of 127,
- elementNumber: element number of the object for internal referencing in the engineering data (optional;
xs:nonNegativeInteger),
- id: the identifier of the object; this can be either of type xs:ID or UUID (obligatory;
xs:ID); compare: Dev:Identities
|
*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.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..*), additionalRelation (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:
- length: Alternatively to a particular limit the length of the overlap in metres can be given. (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),
- releaseSpeed: Release speed in km/h associated with the overlap (optional;
xs:decimal),
- elementNumber: element number of the object for internal referencing in the engineering data (optional;
xs:nonNegativeInteger),
- id: unique identifier (obligatory;
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}}); compare: Dev:Identities
|
*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}}); compare: Dev:Identities
|
*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.
|
Changes 3.1→3.2
There exists an overview of all changes between railML® 3.1 and railML® 3.2 on page Dev:Changes/3.2.
The parents have been changed.
The children have been changed.
The attributes have been changed.
Changes 3.2→3.3
There exists an overview of all changes between railML® 3.2 and railML® 3.3 on page Dev:Changes/3.3.
The parents have been changed.
The children have been changed.
The attributes have been changed.
Semantics
Best Practice / Examples
Additional Information
Notes
Open Issues