IS:trackEnd: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
m (Reordered attributes)
(+semcon)
Line 31: Line 31:
|absPos = If two {{IS:Doc|track}}s are connected, the {{Attr|absPos}} values of the connected {{IS:Tag|trackBegin}} and {{IS:Tag|trackEnd}} must be identical just in case both are provided and no {{IS:Doc|mileageChange}} at this point is defined and both tracks belong to the same "mileage system" (typically the same {{IS:Doc|line}} and same {{IS:Doc|owner}}). <br/> If {{Attr|absPos}} is used in {{IS:Tag|trackEnd}} then it should be used in {{IS:Tag|trackBegin}} for unambiguity reasons, too.
|absPos = If two {{IS:Doc|track}}s are connected, the {{Attr|absPos}} values of the connected {{IS:Tag|trackBegin}} and {{IS:Tag|trackEnd}} must be identical just in case both are provided and no {{IS:Doc|mileageChange}} at this point is defined and both tracks belong to the same "mileage system" (typically the same {{IS:Doc|line}} and same {{IS:Doc|owner}}). <br/> If {{Attr|absPos}} is used in {{IS:Tag|trackEnd}} then it should be used in {{IS:Tag|trackBegin}} for unambiguity reasons, too.
}}
}}
|semcon={{semcon|
*The value of {{@|pos}} in {{IS:Tag|trackBegin|attr=pos}} is allways "0".
*The value of {{@|pos}} in {{IS:Tag|trackEnd|attr=pos}} is identical with the length of the track.
*If {{@|absPos}} is used in {{IS:Tag|trackBegin|attr=absPos}}, it has to be given in {{IS:Tag|trackEnd|attr=absPos}}, too.
*If two {{IS:Tag|track}}s are connected, the {{@|absPos}} values of the connected {{IS:Tag|trackBegin|attr=absPos}} and {{IS:Tag|trackEnd|attr=absPos}} must be identical '''if'''
**both are provided and
**no {{IS:Tag|mileageChange}} is defined at this point and
**both tracks belong to the same mileage system.|status=proposed|proposed=2019-06-17}}
}}
}}

Revision as of 15:46, 17 June 2019


trackEnd
 


Schema description / Schemenbeschreibung

Position of trackEnd in the XML-Tree / Position von trackEnd im XML-Baum

Multiplicity / Anzahl

[1..1]

Semantics / Bedeutung

The trackEnd defines the end of a track in the railML file. It could be seen as a "vertex" in a "graph" where the track is an "edge".
 
Please, be aware of the semantic constraint(s)!

Attributes of trackEnd / Attribute von trackEnd

  • id: XML-file-wide unique, machine-interpretable identity, required for later referencing that element internally. For a detailed explanation see Dev:identities.
    XML-Datei-weit eindeutige, maschineninterpretierbare Identität, die für die spätere interne Referenzierung dieses Elements erforderlich ist. Für eine detaillierte Erklärung siehe Dev:identities.
  • pos: This is the position on a track defined as distance from its start (trackBegin) regardless the "absolute mileage" in @absPos.
    Das ist die Position des Elements auf einem Track i.S. der realen Entfernung zum trackBegin. Sie ist damit unabhängig von der mit absPos modellierten Strecken-Kilometrierung.
🗒️ For an explanation of the differences between @pos and @absPos see <mileageChange>
  • absPos: This is the position on a track as absolute mileage/chainage.
    Das ist die Position des Elements im Referenzsystem der Strecken-Kilometrierung.
🗒️ For an explanation of the differences between @pos and @absPos see <mileageChange>
  • absPosOffset (deprecated with version 2.1): The semantics of this attribute aren't very clear. It seems to be redundant to the definitions with mileageChanges in "overlapping regions".

Syntactic Constraints / Syntaktische Beschränkungen

  • id: xs:ID, required
    a string, starting with a letter (a..zA..Z) or an underscore (_),
    followed by a non-colonized and non-spaced string consisting of letters, digits, points (.), dashes (-) or underscores (_)
  • pos: tLengthM (xs:decimal, 6 fraction digits, length value measured in meter); required; must be greater than or equal to zero, less than or equal to the track's length
    The end of the track is defined by the "real" length of the track as distance from the trackBegin regardless the "absolute mileage" in absPos.
  • absPos: tLengthM (xs:decimal, 6 fraction digits, length value measured in meter); optional
    If two tracks are connected, the absPos values of the connected <trackBegin> and <trackEnd> must be identical just in case both are provided and no mileageChange at this point is defined and both tracks belong to the same "mileage system" (typically the same line and same owner).
    If absPos is used in <trackEnd> then it should be used in <trackBegin> for unambiguity reasons, too.
  • absPosOffset: xs:decimal, 6 fraction digits, length value measured in meter; optional

Semantic Constraints / Semantische Beschränkungen

Private-cloud-icon.png Proposed Semantic Constraint:
 

Best practice & Examples / Empfohlene Anwendung & Beispiele

Not yet described. / Noch nicht beschrieben.

Notes / Anmerkungen

General information on positioning

Positive pos values describe the distance from the track's begin. The track length is derived from the pos value in <trackEnd>.

The absolute mileage refered to by absPos is usually found on technical drawings of the track layout or on mileage posts next to the track.

Open issues / Offene Punkte/Pendenzen

Not yet described. / Noch nicht beschrieben.