Introduction
Documentation
Syntax
|
|
| Documentation
|
This element is not documented in the schema!
|
| Subschema
|
Rtm4railml
|
| Parents*
|
spotLocation
|
| Children
|
None
|
Attributes:
- positioningSystemRef: reference an object using its UUID or GenericID (xs:ID) (obligatory;
xs:IDREF),
- x: longitude (obligatory;
xs:double),
- y: latitude (obligatory;
xs:double),
- z: altitude (optional;
xs:double)
|
*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 RTM subschema. It is available only in railML® 3.3. Do not hesitate to contact railML.org e.V. for further questions.This element does not appear in railML® 3.1 within the RTM subschema. It is available only in railML® 3.3. Do not hesitate to contact railML.org e.V. 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
| 🗒️
|
Please keep in mind that <geometricCoordinate x="0.0" y="0.0" positioningSystemRef="gps1"/> is not a valid coordinate.
|
|
|
Please refer for an example to Geographic positioning of functional infrastructure.
Additional Information
Additional Information
| 🗒️
|
This segment provides background information that is not relevant for the certification process.
|
|
|
Please refer for the context to:
Notes
Open Issues