| Description | A Point is defined by a single coordinate tuple. The direct position of a point is specified by the pos element which is of type DirectPositionType. |
| Subschema | infrastructure |
| Parents* | |
| Children** |
name (0..*), identifier (0..1), descriptionReference (0..1), description (0..1), pos (1..1) |
Attributes:
| |
| *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 The W3C Recommendation on XML Schema | |
IS:point
Jump to navigation
Jump to search
Introduction
Documentation
Syntax
| Description | A Point is defined by a single coordinate tuple. The direct position of a point is specified by the pos element which is of type DirectPositionType. |
| Subschema | infrastructure |
| Parents* | |
| Children** |
name (0..*), identifier (0..1), descriptionReference (0..1), description (0..1), pos (1..1) |
Attributes:
| |
| *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 The W3C Recommendation on XML Schema | |
| Description | This element is not documented in the schema! |
| Subschema | infrastructure |
| Parents* | |
| Children** |
description (0..1), descriptionReference (0..1), name (0..*), identifier (0..1), pos (1..1) |
Attributes:
| |
| *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 The W3C Recommendation on XML Schema | |
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 element documentation has 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 attributes have been changed.
Semantics
Best Practice / Examples
Please refer to Geographic positioning of functional infrastructure for an example.