Introduction
| 🗒️
|
This article uses the unit label meter.
As the reference for this wiki is British English, the correct label is metre.
Wherever the label meter occurs, it is meant equivalently to metre.
|
|
|
Documentation
Syntax
Autoexport from the XML-Schema for element TT:shunting of railML ® version 3.3 |
| Documentation
|
Describes a shunting operation
|
| Subschema
|
timetable
|
| Parents*
|
block
|
| Children
|
endLocation (1..1), startLocation (1..1)
|
Attributes:
- runLength: Used to describe the traveled distance for the enclosing block. Value is given in meters. This may be useful if the traveled distance cannot be deduced from references to infrastructure or due to the fact that only sketchy information is available. (optional;
xs:decimal),
- endDayOffset: Allows specifying that the endTime given applies not to the same day. The offset given here is added to the date of the start day to calculate the date of the endTime. If no endDayOffset is specified it is assumed to be zero. (optional;
xs:unsignedInt; minInclusive: 0; fractionDigits: 0),
- endTime: Used to specify the time when the enclosing block is ending. Needs to be evaluated together with the attribute endDayOffset in case the enclosing block extends over midnight. (obligatory;
xs:time),
- startTime: Used to specify a time when the enclosing block is started. (obligatory;
xs:time)
|
*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.
|
This element does not appear in railML® 3.2 within the TT subschema. It is available only in railML® . Do not hesitate to contact railML.org for further questions.
This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® . Do not hesitate to contact railML.org for further questions.
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.
Introduced with version 3.3.
Semantics
Best Practice / Examples
Additional Information
Notes
Open Issues