RTM:geometricCoordinate

Introduction

See geometric coordinate in the RailTopoModel^® Wiki for further information.

🗒️ In railML® 3.3 it is enforced to specify the relevant positioningSystemRef at the level of the associatedPositoiningSystem based on Positioning approach (link to the railML® website). Therefore coordinates were split into ones where positioningSystemRef is relevant (see <spotLocation:geometricCoordinate>) and the one where it's not (see <intrinsicCoordinate:geometricCoordinate>).

Documentation

Syntax

This element does not appear in railML^® 3.3 within the RTM subschema. It is available only in railML^® 3.1, 3.2. Do not hesitate to contact railML.org e.V. for further questions.

Autoexport from the XML-Schema for element RTM:geometricCoordinate of railML® version 3.2      UML-visualization of RTM
Documentation	localization expressed in a geometrical (or geographical) Reference System, so it defines the coordinates (x, y, z or geodetic latitude (north/south), longitude (east/west), and ellipsoidal height (also known as geodetic height)).
Subschema	Rtm4railml
Parents*	intrinsicCoordinate, linearLocation, spotLocation
Children	None
Attributes: x: longitude (obligatory; xs:double), y: latitude (obligatory; xs:double), z: altitude (optional; xs:double), positioningSystemRef: reference an object using its UUID or GenericID (xs:ID) (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}})
*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 RTM:geometricCoordinate of railML® version 3.1      UML-visualization of RTM
Documentation	This element is not documented in the schema!
Subschema	Rtm4railml
Parents*	intrinsicCoordinate, linearLocation, spotLocation
Children	None
Attributes: x: This attribute is not documented in the schema! (obligatory; xs:double), y: This attribute is not documented in the schema! (obligatory; xs:double), z: This attribute is not documented in the schema! (optional; xs:double), positioningSystemRef: reference an object using its UUID or GenericID (xs:ID) (obligatory; xs:IDREF; 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}})
*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 element documentation has 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.
Removed with version 3.3.

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

🗒️ This segment provides background information that is not relevant for the certification process.

For context see the following Git issues:

• #541
• #22