RTM:geometricPositioningSystem

Documentation

Syntax

3.33.23.1

Autoexport from the XML-Schema for element RTM:geometricPositioningSystem of railML® version 3.3      UML-visualization of RTM
Description	a geometric positioning system allows positioning entities geographically. One typical geometric positioning system is WGS84.
Subschema	Rtm4railml
Parents*	geometricPositioningSystems
Children	name (0..*), isValid (1..*)
Attributes: crsDefinition: It is strongly recommended to make use of the EPSG code for this attribute in order to have a standardized notation. (optional: xs:string : xs:string), id: the file-internal ID of the object (obligatory: tID : xs:ID): compare: Dev:Identities
*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:geometricPositioningSystem of railML® version 3.2      UML-visualization of RTM
Description	a Geometrical Reference System, so it allows to locate a resource with its geometrical coordinates (x, y, z or ?, ?, h).
Subschema	Rtm4railml
Parents*	geometricPositioningSystems
Children	name (0..*), isValid (1..*)
Attributes: crsDefinition: It is strongly recommended to make use of the EPSG code for this attribute in order to have a standardized notation. (optional: xs:string : xs:string), id: the identifier of the object; this can be either of type xs:ID or UUID (obligatory: tID : 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}\}): compare: Dev:Identities
*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:geometricPositioningSystem of railML® version 3.1      UML-visualization of RTM
Description	This element is not documented in the schema!
Subschema	Rtm4railml
Parents*	geometricPositioningSystems
Children	name (0..*), isValid (1..*)
Attributes: crsDefinition: This attribute is not documented in the schema! (optional: xs:string : xs:string), id: the identifier of the object; this can be either of type xs:ID or UUID (obligatory: tID : xs:ID: 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}\}): compare: Dev:Identities
*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 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 element documentation has been changed.

The attributes have been changed.

Best Practice / Examples

🗒️ It's strongly recommended to provide @crsDefinition in the form "urn:ogc:def:objectType:EPSG:version:code" i.e. for WGS84 it's "urn:ogc:def:crs:EPSG::4326"

Please refer for an example to Geographic positioning of functional infrastructure.