IS:route
Jump to navigation
Jump to search
IS:route
|
Scheme description / Schemenbeschreibung
Position of IS:route in the XML-Tree / Position von IS:route im XML-Baum
- Parent: <routes>
- Children: <switchAndPosition>, <overlapSwitchAndPosition>, <releaseGroup>, <states>
Multiplicity / Anzahl
Semantics / Bedeutung
A route is a central element to ensure traffic safety in railway networks. The basic definition is a predetermined path for a traffic movement. This path starts from a starting point (usually a signal) and ends at a destination point (usually a signal), univocally identified by the list of switches and their position included in the path. In addition, there may be elements outside the (running) path of the route.(introduced with version 2.5)
Attributes of IS:route / Attribute von IS:route
- 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. - conditional Possible values are:
- ocpManned: The route is only used in case of the OCP is manned.
- ocpUnmanned: The route is only used in case of the OCP is unmanned.
- approachPointRef Used for a speed restriction on an approach zone in front of the route (Before RouteEntry) a train must obey if the route is closed (red light). The approachPoint refers to where the approach zone starts in front of the route. This may be the distant signal in front of the route.
- approachSpeed used together with approachPoint, ApproachSpeed can also be used for multiple route approach speed profiling.
- overlapEndRef The overlap always starts at the RouteExit signal. The reference of the overlapEnd is to the end of the overlap/slip. This is usually a train detection element. Only one type of overlap exists. The overlap is defined to always start at the end signal of the route. The end of the overlap can be defined at the end point (usually an axle counter or a track circuit border) for an unambiguous overlap path. For an ambiguous overlap path the protective elements need to be defined (switch and position, flank protection or head protection). The overlap is always released together with the route. Except if there is defined a trigger. If a trigger is defined it can have a timer. The timer is set in seconds. The overlap is released after the trigger is activated and the timer has elapsed. The trigger can be a trigger point (line side) which either reacts on the head of the train (occupy TVD after the trigger point) or the complete train (release TVD before the trigger point). Or the trigger can be activated according to the speed of the train (train side). Only speed 0 km/h is deemed relevant (standstill). This (train side) trigger is technology independent. This as it can relay both to ETCS (which can be designed to send a telegram after standstill for a certain time), or human interlocking of the local dispatcher who observes that the train has come to a standstill and after a handling time (reflected in the timer) releases the overlap.
- releaseTriggerRef Reference to the trigger point for the overlap release timer. This is usually a train detection element. If no overlapReleaseTimer is set, but a overlapValidityTime is set, the default value is that the timing starts from when the train has stopped on the route. This technology independent (ETCS standstill telegram or local dispatcher observance)
- releaseTriggerHead "true" = valid for first axle (head) of the train. "false" = valid for last axle (tail/rear) of the train
- overlapValidityTime Duration the overlap is active blocking potential overlapping routes from forming. The overlap is formed together with the route and is released after overlapValidityTime has run out after the overlapReleaseTimer (aka overlap validity time trigger point) value has been triggered.
- proceedSpeed Proceed speed is a speed restrictions by the route. This is valid for the whole route (from signal to signal). No value=track speed.
- releaseSpeed Release speed is the speed at which the brake curve intervention is removed and the train driver is unsupervised except from SPAD. This is valid for the whole route (from signal to signal).
- entryRef reference to the signal where the route starts.
- exitRef reference to the signal where the route ends.
Syntactic Constraints / Syntaktische Beschränkungen
None
Best practice & Examples / Empfohlene Anwendung & Beispiele
Not yet described. / Noch nicht beschrieben.
Notes / Anmerkungen
Not yet described. / Noch nicht beschrieben.
Open issues / Offene Punkte/Pendenzen
Not yet described. / Noch nicht beschrieben.