RTM:geometricPositioningSystem

Introduction

Autoexport from the XML-Schema for element RTM:geometricPositioningSystem of railML^® version 3.2 UML-visualization of RTM
Documentation	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	isValid (1..), name* (0..*)
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`), id: the identifier of the object; this can be either of type xs:ID or UUID (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}}); 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
Documentation	This element is not documented in the schema!
Subschema	Rtm4railml
Parents^*	geometricPositioningSystems
Children	isValid (1..), name* (0..*)
Attributes: crsDefinition: This attribute is not documented in the schema! (optional; `xs:string`), id: the identifier of the object; this can be either of type xs:ID or UUID (obligatory; `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.

The element documentation has been changed.

The children have changed.

The attributes have been changed.