RTM:geometricCoordinateBegin

From railML 3 Wiki
Jump to navigation Jump to search

Introduction

Documentation

Syntax

Autoexport from the XML-Schema for element RTM:geometricCoordinateBegin of railML® version 3.2
Documentation geometric coordinate of the beginning of area covered by some functional IS entity
Subschema Rtm4railml
Parents* associatedNetElement
Children None
Attributes:
  • x: longitude (obligatory; xs:double),

  • y: latitude (obligatory; xs:double),

  • z: altitude (optional; xs:double),

  • positioningSystemRef: reference an object using its UUID or GenericID (xs:ID) (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}})
*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:geometricCoordinateBegin of railML® version 3.1
Documentation This element is not documented in the schema!
Subschema Rtm4railml
Parents* associatedNetElement
Children None
Attributes:
  • x: This attribute is not documented in the schema! (obligatory; xs:double),

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

  • z: This attribute is not documented in the schema! (optional; xs:double),

  • positioningSystemRef: reference an object using its UUID or GenericID (xs:ID) (obligatory; xs:IDREF; 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}})
*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 attributes have been changed.

Semantics

Best Practice / Examples

Additional Information

Notes

Open Issues