Introduction
Documentation
Syntax
Autoexport from the XML-Schema for element IL:routeExit of railML ® version 3.3 |
| Documentation
|
Description of the route destination point. In most cases the route destination is a signal or a buffer stop.
|
| Subschema
|
interlocking
|
| Parents*
|
route
|
| Children
|
belongsToOperationalPoint (0..*), designator (0..*), elementState (0..*), hasCommand (0..*), hasDangerPoint (0..*), hasIndication (0..*), hasIndicator (0..1), hasOverlap (0..*), hasRouteReleaseTrigger (0..1), objectName (0..*), refersTo (1..1)
|
Attributes:
- 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:routeExit of railML ® version 3.2 |
| Documentation
|
Description of the route destination point. In most cases the route destination is a signal or a buffer stop.
|
| Subschema
|
interlocking
|
| Parents*
|
route
|
| Children
|
belongsToOperationalPoint (0..*), designator (0..*), hasCommand (0..*), hasDangerPoint (0..1), hasIndication (0..*), hasIndicator (0..1), hasOverlap (0..*), objectName (0..*), refersTo (1..1)
|
Attributes:
- 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:routeExit of railML ® version 3.1 |
| Documentation
|
Description of the route destination point. In most cases the route destination is a signal or a buffer stop.
|
| Subschema
|
interlocking
|
| Parents*
|
route
|
| Children
|
any (0..*), designator (0..1), hasDangerPoint (0..1), hasOverlap (0..*), refersTo (1..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}}); 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 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 children have been changed.
The attributes have been changed.
Semantics
Best Practice / Examples
The end of a route path as its destination is defined in <routeExit>. This element refers onto the asset, which marks this destination. It may be enhanced by information about necessary safety precautions in advance of the destination signal.
- <refersTo> – This is the reference to the physical end of the route path. This is in most cases a signal but can also be a buffer stop or just a train detection device when continuing into a track area outside the interlocking responsibility (“terra incognito”). Preferable the reference shall be made to the element with the interlocking attributes instead of the pure infrastructure element.
- <hasDangerPoint> – This is the reference to the danger point in advance of the destination signal.
- <hasOverlap> – This is the reference to the path in advance of the destination signal as safety precaution.
The extract shows the skeleton of a <routeExit>.
<routeExit id="rtd_69A">
<designator register="_SimpleRegister" entry="Dest 69A"/>
<refersTo ref="ls_sig04"/>
<hasDangerPoint ref="dp01" />
<hasOverlap ref="ov01" />
</routeExit>
Additional Information
Notes
Open Issues