RTM:linearPositioningSystem

Documentation

Syntax

Autoexport from the XML-Schema for element RTM:linearPositioningSystem of railML® version 3.2 UML-visualization of RTM
Documentation	Localization expressed in a linear reference system, generally a coordinate along a predefined axis.
Subschema	Rtm4railml
Parents*	linearPositioningSystems
Children	anchor (0..*), isValid (1..*), name (0..*)
Attributes: endMeasure: This attribute is not documented in the schema! (obligatory; xs:double), linearReferencingMethod: This attribute is not documented in the schema! (obligatory; xs:string) Possible values: absolute interpolation relative, startMeasure: This attribute is not documented in the schema! (obligatory; xs:double), units: use SI units (e.g. metres) whenever possible (obligatory; 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:linearPositioningSystem of railML® version 3.1 UML-visualization of RTM
Documentation	This element is not documented in the schema!
Subschema	Rtm4railml
Parents*	linearPositioningSystems
Children	anchor (0..*), isValid (1..*), name (0..*)
Attributes: linearReferencingMethod: This attribute is not documented in the schema! (obligatory; xs:string) Possible values: interpolation relative absolute, startMeasure: This attribute is not documented in the schema! (obligatory; xs:double), endMeasure: This attribute is not documented in the schema! (obligatory; xs:double), units: use SI units (e.g. metres) whenever possible (obligatory; 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.

Changes 3.1→3.2

The element documentation has been changed.

The children have changed.

The attributes have been changed.

Semantics

Proposed Semantic Constraint "IS:014":   @startMeasure and @endMeasure are start and end values of a railway <IS:line> associated with <RTM:linearPositioningSystem> not max and min values of a current file with e.g. line section   Proposed on April 08th 2024 Discuss this semantic constraint Please, recognize our guidelines on semantic constraints