IS:operationModeChange

operationModeChange
 

Schema description / Schemabeschreibung

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

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

Multiplicity / Anzahl

[0..∞]

Semantics / Bedeutung

A <operationModeChange> defines a point in which the operation mode (executive / legislative) of an operation control point changes.

Attributes of operationModeChange / Attribute von operationModeChange

• 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 operationModeChange 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).

In this article there is information missing with respect to attribute semantics. Please help improving the railML® Wiki by filling the gaps. Possibly, you will find further details on the discussion page. Ferri Leberl (talk) 15:55, 16 January 2017 (CET)

• modeLegislative

• modeExecutive

• clearanceManaging Possible values are:

• sight used while any other kind of signalling is unavailable.
• time clearance is guaranteed through the amount of time a train leaves the block section completely.
• blocking means to guarantee a minimum distance between trains running in the same direction and to guarantee that two trains running in opposite directions are not in the same section of track simultaneously. The source of definition is IEC 60050:821-06-01.
• LZB-blocking Continuous Train Control (LZB) transmits data continuously and bidirectionally. With LZB, a train can be automatically brought to a halt and can additionally be controlled. LZB consists of a line cable that is laid in the form of a loop in the track and an LZB radio block centre. Data telegrams are transmitted from the vehicle to the radio block centre and vice versa, via the line cable ETCS migration planning in Germany (external link).
• absBrakeDist wheel slide control systems. The most common of these operates rather like ABS (automatic braking systems) on road vehicles. The railway systems usually monitor the rotation of each axle and compare rotational speeds between pairs of axles. If a difference appears between a pair of axles during braking, the brake is released on those axles until the speeds equalise, when the brake is re-applied. All this occurs automatically. Modern systems also detect too rapid deceleration of an axle. Another form of slip/slide detection uses Doppler radar techniques. This measures the ground speed of the locomotive against the revolutions of each wheelset and uses the detection of a difference to regulate the control systems Integrail Glossary (external link).
• other:anything: Any value that does not fit any value from the previous enumeration list, fulfilling the constraint: at minimum two characters, whitespace is not allowed. Please, apply Dev:usingAny accordingly.

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; derived from tLaxDirection; optional
• modeLegislative xs:string, mandatory

• modeExecutive xs:string, mandatory

• clearanceManaging optional

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.