|
|
| (2 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| <!--Element '''{{{element}}}'''--> | | <!--Element '''{{{element}}}'''--> |
| =={{introduction}}== | | =={{introduction}}== |
| | See {{topo|Intrinsic positioning / referencing|intrinsic coordinate in the {{rtm|link=no}}}} 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}} |
| | |
| =={{documentation}}== | | =={{documentation}}== |
| ==={{syntax}}=== | | ==={{syntax}}=== |
| Line 13: |
Line 15: |
| =={{Additional Information}}== | | =={{Additional Information}}== |
| ==={{Notes}}=== | | ==={{Notes}}=== |
| | {{intro|3.3}} Please note that as of version 3.3 the child elements of {{RTM:Tag|intrinsicCoordinate}}, {{RTM:Tag|linearCoordinate}} and {{RTM:Tag|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 {{RTM:Tag|intrinsicCoordinate}}. It is syntactically not possible to specify both for the same {{RTM:Tag|intrinsicCoordinate}}. |
| ==={{Open issues}}=== | | ==={{Open issues}}=== |
Latest revision as of 10:38, 28 March 2025
Introduction
See intrinsic coordinate in the RailTopoModel® Wiki.
Documentation
Syntax
|
|
| 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.
|
|
|
| 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.
|
|
|
| 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 parents have 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 parents have been changed.
The children have been changed.
The attributes have been changed.
Semantics
Best Practice / Examples
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