RTM:intrinsicCoordinate

From railML 3 Wiki
Jump to navigation Jump to search

Introduction

See intrinsic coordinate in the RailTopoModel® Wiki.

Documentation

Syntax

Autoexport from the XML-Schema for element RTM:intrinsicCoordinate of railML® version 3.3
    
Documentation coordinate X after the start of the element in an interval from 0 to 1
Subschema Rtm4railml
Parents*

associatedPositioningSystem

Children

geometricCoordinate (1..1), linearCoordinate (1..1)

Attributes:
  • intrinsicCoord: value of coordinate X after the start of the element in an interval from 0 to 1 (obligatory; xs:double; minInclusive: 0; maxInclusive: 1),

  • id: the identifier of the object; this can be either of type xs:ID or UUID (obligatory; 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:intrinsicCoordinate of railML® version 3.2
    
Documentation coordinate X after the start of the element in an interval from 0 to 1
Subschema Rtm4railml
Parents*

associatedPositioningSystem

Children

geometricCoordinate (0..*), linearCoordinate (0..*)

Attributes:
  • intrinsicCoord: value of coordinate X after the start of the element in an interval from 0 to 1 (obligatory; xs:double),

  • 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:intrinsicCoordinate of railML® version 3.1
    
Documentation This element is not documented in the schema!
Subschema Rtm4railml
Parents*

associatedPositioningSystem

Children

geometricCoordinate (0..*), linearCoordinate (0..*)

Attributes:
  • intrinsicCoord: This attribute is not documented in the schema! (obligatory; xs:double),

  • 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

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.

The children have been changed.

The attributes have been changed.

Semantics

Private-cloud-icon.png Semantic Constraint "IS:024":
 
When specifying an <intrinsicCoordinate> with 0 < @intrinsicCoord < 1, it needs to be ensured that a given <linearCoordinate> is aligned with the referenced <linearPositioningSystem>.
 
Proposed on April 2nd 2025
Approved on October 13th 2025
https://www.railml.org/forum/index.php?t=msg&th=1045&start=0&

Please, recognize our guidelines on semantic constraints 

Best Practice / Examples

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

Additional Information

Notes

(introduced with version 3.3)

Please note that as of version 3.3 the child elements of <intrinsicCoordinate>, <linearCoordinate> and <geometricCoordinate> listed both with a multiplicity of 1..1 are organized in the schema as part of a xs:choice. This means that only one or the other is to be specified for each <intrinsicCoordinate>. It is syntactically not possible to specify both for the same <intrinsicCoordinate>.

Open Issues