RTM:linearPositioningSystem: Difference between revisions

From railML 3 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
m (typo)
(added RTM link)
 
Line 1: Line 1:
<!--Element '''{{{element}}}'''-->
<!--Element '''{{{element}}}'''-->
=={{introduction}}==
=={{introduction}}==
See {{topo|Linear_Positioning_/_referencing|linear positioning system in {{rtm|link=no}}}}'s wiki.
<!--{{#ifeq:{{{comment}}}||{{missing information|topic=the semantics|user=<br>This template was inserted Automatically on import by [[user:Roboter]]}}|{{{comment}}}}}-->
<!--{{#ifeq:{{{comment}}}||{{missing information|topic=the semantics|user=<br>This template was inserted Automatically on import by [[user:Roboter]]}}|{{{comment}}}}}-->
{{ImportComment}}
{{ImportComment}}

Latest revision as of 15:19, 19 April 2024

Introduction

See linear positioning system in RailTopoModel®'s wiki.

Documentation

Syntax

Autoexport from the XML-Schema for element RTM:linearPositioningSystem of railML® version 3.3
Documentation Linear positioning systems work in one dimension. They are a typical way to specifiy the location of an entity on a railway. The one given coordinate for an entity in a linear positioning system positions the entity following the layout of the track.
Subschema Rtm4railml
Parents* linearPositioningSystems
Children anchor (0..*), isValid (1..*), name (0..*)
Attributes:
  • endMeasure: last value in the direction on mileage of the line (at its end) associated with the enclosing linear positioning system (obligatory; xs:double),

  • linearReferencingMethod: specifies a way of how the coordinates were determined (obligatory; xs:string)
Possible values:
  • absolute: mileage i.e. distance from beginning of a line
  • interpolation: determine location by interpolating between two known locations along a route.
  • relative: relative to some point on a line, not a beginning of a line,

  • startMeasure: first value in the direction on mileage of the line (at its beginning) associated with the enclosing linear positioning system (obligatory; xs:double),

  • units: use SI units (e.g. metres) whenever possible (obligatory; xs:string; patterns: other:w{2,})
Possible values:
  • metres
  • miles,

  • 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:linearPositioningSystem of railML® version 3.2
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: last value in the direction on mileage of the line (at its end) associated with the enclosing linear positioning system (obligatory; xs:double),

  • linearReferencingMethod: specifies a way of how the coordinates were determined (obligatory; xs:string)
Possible values:
  • absolute
  • interpolation
  • relative,

  • startMeasure: first value in the direction on mileage of the line (at its beginning) associated with the enclosing linear positioning system (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
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

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.

Semantics

Private-cloud-icon.png 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


Best Practice / Examples

Additional Information

Notes

Open Issues