IS:trackBegin: Difference between revisions
Jump to navigation
Jump to search
| [unchecked revision] | [unchecked revision] |
(Created using IS:absPosition and IS:relPosition contents) |
(Updated using new template (Vorlage:RailMLType)) |
||
| Line 16: | Line 16: | ||
|absPosOffset = | |absPosOffset = | ||
}} | }} | ||
|ownAttributes = | |||
* {{Attr|id}}: | |||
|notes = | |notes = | ||
| Line 25: | Line 28: | ||
|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|trackBegin}} then it should be used in {{IS:Tag|trackEnd}} 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|trackBegin}} then it should be used in {{IS:Tag|trackEnd}} for unambiguity reasons, too. | ||
}} | }} | ||
* {{Attr|id}} {{RailMLType|tGenericID}}, mandatory | |||
|backHome = IS:elements | |backHome = IS:elements | ||
}} | }} | ||
Revision as of 15:34, 6 December 2011
trackBegin
Scheme description / Schemenbeschreibung
Position of trackBegin in the XML-Tree / Position von trackBegin im XML-Baum
- Parent: <trackTopology>
- Children: <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".
Attributes of trackBegin / Attribute von trackBegin
- 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.
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".
- id:
Syntactic Constraints / Syntaktische Beschränkungen
- 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
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 <trackBegin> then it should be used in <trackEnd> for unambiguity reasons, too. - absPosOffset: xs:decimal, 6 fraction digits, length value measured in meter; optional
- id xs:ID, mandatory
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.