Autoexport from the XML-Schema for element IS:isStopPost of railML® version 3.3 | |
| Description | use this child element to specify the stop post in more detail |
| Subschema | infrastructure |
| Parents* | |
| Children** |
refersToStoppingPlace (0..1) |
| Attributes:None | |
| *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. **Notice: To learn, how to interpret multiplicity information like (0..*) go to Class diagram (  ) | |
IS:isStopPost
Jump to navigation
Jump to search
Introduction
Stop Post is a physical marker on the trackside that shows the exact point where a train must stop, usually at stations, platforms, or operational points.
Documentation
Syntax
Autoexport from the XML-Schema for element IS:isStopPost of railML® version 3.2 | |
| Description | use this child element to specify the stop post in more detail |
| Subschema | infrastructure |
| Parents* | |
| Children** |
refersToStoppingPlace (0..1) |
| Attributes:None | |
| *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. **Notice: To learn, how to interpret multiplicity information like (0..*) go to Class diagram ( ) | |
Autoexport from the XML-Schema for element IS:isStopPost of railML® version 3.1 | |
| Description | use this child element to specify the stop post in more detail |
| Subschema | infrastructure |
| Parents* | |
| Children** |
refersToStoppingPlace (0..1), any (0..*) |
| Attributes:None | |
| *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. **Notice: To learn, how to interpret multiplicity information like (0..*) go to Class diagram ( ) | |
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.
Semantics
Best Practice / Examples
Please refer to Dev:Types_of_signals for examples.