IS:border

border
 

Schema description / Schemabeschreibung

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

• Parent: <borders>
• Children: <additionalName> (introduced with version 2.1), <any>, <geoCoord>, <states>

Multiplicity / Anzahl

[0..∞]

Semantics / Bedeutung

A <border> is used to define a border, e.g. between tarif zones, countries, areas ...

Attributes of border / Attribute von border

• 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.
• code (introduced with version 2.1): Machine-interpretable string (e.g. an abbreviation) used for identification of the object across exchange partners, usecase specific uniqueness constraints may apply. Please see our description of the differences between id, code and human-readable identifiers.
  Maschineninterpretierbare Zeichenkette (z.B. Abkürzung), die zur Identifizierung des Objekts auch bei Austauschpartnern verwendet wird, wobei spezifische Eindeutigkeitsbeschränkungen gelten können. Bitte beachten Sie unsere Erläuterung zu den Unterschieden zwischen id, code and menschenlesbaren Kennzeichnungen.
• name: Established, human-readable short string, giving the object a name. Not intended for machine interpretation, please see our notice on human interpretable data fields.
  Etablierte, menschenlesbare kurze Zeichenkette, die das Objekt benennt. Nicht zur maschinellen Interpretation bestimmt, siehe Hinweise zu menschenlesbaren Datenfeldern.
• description: Human-readable, more detailed description as addition to the name. It should give additional explanations or hints to the contents of this element. Not intended for machine interpretation, please see our notice on human interpretable data fields.
  Menschenlesbare, detailliertere Beschreibung als Ergänzung zu name. Sie soll zusätzliche Erläuterungen oder Hinweise auf den Inhalt dieses Elements geben. Nicht zur maschinellen Interpretation bestimmt, siehe Hinweise zu menschenlesbaren Datenfeldern.
• xml:lang (introduced with version 2.1): This is a unique identifier of language. It uses basically the language standard IETF BCP 47 (external link) which may be different to ISO 639-1 (external link) or ISO 639-2 (external link). For mapping hints see relation to other standards (external link).
  This defines the language used for name and description. Use <additionalName> to provide a name and/or description in other languages.

• 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".

• dir: This defines the validity of border along the track. Possible values are:

• up: This denotes the direction from the <trackBegin> to the <trackEnd> (increasing relative position values).
• down: This goes opposite to up (decreasing relative position values).
• unknown: border is restricted to a certain direction, but this direction is not known.

• type: This is the border type. Possible values are:

• tarif: [Sic!] Shall be used for borders between two (or more) transport associations (Verkehrsverbünde).
• area: tracks, put to some purpose, for example, "Permanent shunting areas (PSA) are used to describe track areas mainly used for shunting." Compare Bane NOR Digitalisation and Technology. Signalling System Engineering Process Guideline Engineering Guidelines (external link).
• state: border between different states within one country
• country: border between different countries
• station: border between railway line and station, for example "station border" signal or entry signal
• project (introduced with version 2.5): defines the outer limits of a project area. The project area can be defined as the area where either changes are made to the infrastructure based on a specific project or an area that is relevant for a specific project. Compare forum discussion (link to the railML^® website)
• other:anything: Any value that does not fit any value from the previous enumeration list, starting with 'other:' followed by at least two letters and/or digits. Please see the section New enumeration value in Dev:usingAny for more information.

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 (_)
• code: xs:string, optional
• name: xs:string, optional
• description: xs:string, optional
• xml:lang: xs:language, language identification, optional

• 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
  
• 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

• dir: xs:string, generic type for more constrained direction statements: enumeration up, down, unknown; derived from tLaxDirection; optional
  

• type 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.

Using border types, different boundaries can be set in a project, depending on special needs and irrespective from physical or project's borders.

Open issues / Offene Punkte/Pendenzen

Not yet described. / Noch nicht beschrieben.