IS:trackBegin: Difference between revisions
[checked revision] | [checked revision] |
(Contribution by Лариса Жучий) |
(Link internalized) |
||
(5 intermediate revisions by 4 users not shown) | |||
Line 2: | Line 2: | ||
elementName = trackBegin | elementName = trackBegin | ||
|semantics = The {{IS:Doc|trackBegin}} defines the start of a {{IS:Doc|track}} in the | |semantics = The {{IS:Doc|trackBegin}} defines the start of a {{IS:Doc|track}} in the {{rml}} file. It could be seen as a "vertex" in a "graph" where the {{IS:Doc|track}} is an "edge". | ||
|parent = | |parent = | ||
Line 16: | Line 16: | ||
{{InheritPosition | {{InheritPosition | ||
|pos = | |pos = | ||
|absPos = | |absPos ={{semconHint|IS:003}} | ||
|absPosOffset = | |absPosOffset = | ||
}} | }} | ||
|ownAttributes = | |ownAttributes = | ||
*{{attr|absDir}} {{Intro|2.2}}: Defines whether the mileage increases ( | *{{attr|absDir}} {{Intro|2.2}}: Defines whether the mileage increases ({{Enum|raising}}) or decreases ({{Enum|falling}}) along the {{IS:Tag|track}} from this {{IS:Doc|trackBegin}}. | ||
{{note|The value "raising" is a misspelling of "rising".<br>For downward compatibility reasons, this cannot be changed.}} | {{note|The value "raising" is a misspelling of "rising".<br>For downward compatibility reasons, this cannot be changed.}} | ||
|notes = | |notes = | ||
Line 30: | Line 30: | ||
{{InheritPositionConstraints | {{InheritPositionConstraints | ||
|pos = The start of the track is described by a {{Attr|pos}} value of zero. | |pos = The start of the track is described by a {{Attr|pos}} value of zero. | ||
|absPos = If two {{IS:Tag|track}}s are connected, the {{Attr|absPos}} values of the connected {{IS:Tag|trackBegin}} and {{IS:Tag|trackEnd}} must be identical if both are provided and no {{IS: | |absPos =<!-- If two {{IS:Tag|track}}s are connected, the {{Attr|absPos}} values of the connected {{IS:Tag|trackBegin}} and {{IS:Tag|trackEnd}} 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" (typically the same {{IS:Tag|line}} and same {{IS:Tag|owner}}). <br/> If {{Attr|absPos}} is used in {{IS:Tag|trackBegin}} then it should be used in {{IS:Tag|trackEnd}} for unambiguity reasons, too.--> | ||
}} | }} | ||
*{{attr|absDir}}: {{railMLType|tMileageDirection}} | *{{attr|absDir}}: {{railMLType|tMileageDirection}} | ||
|example={{missing information|user=[[User:Ferri Leberl|Ferri Leberl]] ([[User talk:Ferri Leberl|talk]]) 16:52, 3 January 2018 (CET)|topic=best practice around mileage changes}} | |example={{missing information|user=[[User:Ferri Leberl|Ferri Leberl]] ([[User talk:Ferri Leberl|talk]]) 16:52, 3 January 2018 (CET)|topic=best practice around mileage changes}} | ||
|semcon={{ | |semcon={{IS:003}} | ||
|example= | |example= | ||
Consider | Consider the {{rml|2.3}} example of [https://www.railml.org/en/user/exampledata.html?file=files/download/exampledata/090318_Bahnkonzept_ExampleDataGPSinfradat_NorthUpperRhineNetworkRailML23.zip Middle Rhine Railway by GPSinfradat]. | ||
[[File:mip1.png|347x305px]] | [[File:mip1.png|347x305px]] | ||
Line 52: | Line 45: | ||
<nowiki /> | <nowiki /> | ||
This code example defines [ | This code example defines a [[IS:trackBegin|track begin]] that is an [[IS:openEnd|open end]]. | ||
<syntaxhighlight lang=xml> | <syntaxhighlight lang=xml> | ||
<trackBegin id="tB26301" pos="0" absPos="91050"> | <trackBegin id="tB26301" pos="0" absPos="91050"> | ||
Line 58: | Line 51: | ||
</trackBegin> | </trackBegin> | ||
</syntaxhighlight> | </syntaxhighlight> | ||
This code example defines [ | This code example defines a [[IS:trackBegin|track begin]] that is a [[IS:macroscopicNode|macroscopic node]]. | ||
<syntaxhighlight lang=xml> | <syntaxhighlight lang=xml> | ||
Line 66: | Line 59: | ||
</syntaxhighlight> | </syntaxhighlight> | ||
Consider | Consider the {{rml|2.2}} example of [https://www.railml.org/en/user/exampledata.html?file=files/download/exampledata/130416_iRFP_ExampleDataFBS_EastSaxonyRailML.zip East Saxony railway network by FBS]. | ||
<div class="res-img"> | <div class="res-img"> | ||
[[File:mip3.pdf]] | [[File:mip3.pdf]] | ||
</div> | </div> | ||
This code example defines [ | This code example defines [[IS:trackBegin|track begin]] that is a [[IS:macroscopicNode|macroscopic node]]. | ||
<syntaxhighlight lang=xml> | <syntaxhighlight lang=xml> |
Latest revision as of 16:04, 20 May 2024
trackBegin
Scheme description / Schemenbeschreibung
Position of trackBegin in the XML-Tree / Position von trackBegin im XML-Baum
- Parent: <trackTopology>
- Children: (introduced with version 2.2) <geoCoord>, <bufferStop>, <connection>, <openEnd>, <macroscopicNode>
Multiplicity / Anzahl
Semantics / Bedeutung
The trackBegin defines the start 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 trackBegin / Attribute von trackBegin
- 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.
|
- absPos: This is the position on a track as absolute mileage/chainage.
Please, be aware of semantic constraint IS:003!
Das ist die Position des Elements im Referenzsystem der Strecken-Kilometrierung.
|
- 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".
- absDir (introduced with version 2.2): Defines whether the mileage increases (raising) or decreases (falling) along the <track> from this trackBegin.
|
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 start of the track is described by a pos value of zero. - absPos: tLengthM (xs:decimal, 6 fraction digits, length value measured in meter); optional
- absPosOffset: xs:decimal, 6 fraction digits, length value measured in meter; optional
- absDir: xs:string, generic type for mileage direction statements; enumeration raising [Sic!], falling
Semantic Constraints / Semantische Beschränkungen
|
Best practice & Examples / Empfohlene Anwendung & Beispiele
Consider the railML® 2.3 example of Middle Rhine Railway by GPSinfradat.
TrackID | LineID | BeginElementType | EndElementType | OCP Start | OCP End |
---|---|---|---|---|---|
26301 | 2630 | oE | mN | KKO | FBGK |
35102 | 3510 | oE | mN | FMZ | FBGK |
35113 | 3511 | mN | oE | FBGK | SBKNG |
This code example defines a track begin that is an open end.
<trackBegin id="tB26301" pos="0" absPos="91050"> <openEnd id="oEb26301"/> </trackBegin>
This code example defines a track begin that is a macroscopic node.
<trackBegin id="tB35113" pos="0" absPos="-110"> <macroscopicNode ocpRef="ocpFBGK"/> </trackBegin>
Consider the railML® 2.2 example of East Saxony railway network by FBS.
This code example defines track begin that is a macroscopic node.
<trackBegin id='trn_DN_80.6212_1' pos='0' absPos='102100'> <macroscopicNode ocpRef='ocp_DN'/> </trackBegin>
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.