Introduction
Documentation
Syntax
Autoexport from the XML-Schema for element IL:hasRouteType of railML ® version 3.2 |
| Documentation
|
Classification of route types.
|
| Subschema
|
interlocking
|
| Parents*
|
usesTypes
|
| Children
|
designator (0..*)
|
Attributes:
- genericRouteType: The classification of the route types. (obligatory;
xs:string; patterns: other:w{2,})
- Possible values:
- auxilliary: The route type is used for auxiliary purpose as part of a complete route (from signal to signal). Often it marks a route part at the interface between two signalboxes (block interface) or the interface between a station and open line (line interface).
- block: This route type is used only on open line. These routes are often automatically handled by the interlocking.
- callOn: This is a special route type for situations, where the interlocking cannot fully secure the route for a train but safety is established by operator rules.
- nonElectrified: This is the route type for securing the path of the trains in the standard way but allows the running path to be without electrification, i.e. it shall be used for diesel or battery trains only.
- normal: This is the route type for securing the path of the trains in the standard way
- occupied: The route leads to an already occupied TVD section, i.e. the destination tracks must be occupied
- shunting: Such routes are typically used for splitting or merging formations of railway vehicles with a reduced amount of safety as the train movement is performed on low speed under responsibility of the driver. Parts of the running path can be occupied
- siding: This special route type is used for exit routes with destination of a siding on open line (de: Ausweichanschlussstelle). It is used for automatic release of the key lock associated with the siding.
- tunnel: The route leads to a tunnel section, which has restrictions w.r.t. vehicle acceptance, i.e. the vehicles shall be equipped with emergency brake cancellation,
- id: unique identifier (obligatory;
xs:string; patterns: (urn:uuid:)?[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}|{[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}}); compare: Dev:Identities
|
*Notice:
Elements may have different parent elements. As a consequence they may be used in different contexts.
Please, consider this as well as a user of this wiki as when developing this documentation further.
Aspects that are only relevant with respect to one of several parents should be explained exclusively in the documentation of the respective parent element.
|
Autoexport from the XML-Schema for element IL:hasRouteType of railML ® version 3.1 |
| Documentation
|
Classification of route types.
|
| Subschema
|
interlocking
|
| Parents*
|
usesTypes
|
| Children
|
any (0..*), designator (0..1)
|
Attributes:
- genericRouteType: The classification of the route types. (obligatory;
xs:string; patterns: other:w{2,})
- Possible values:
- tunnel
- siding
- shunting
- occupied
- normal
- nonElectrified
- callOn,
- id: unique identifier (optional;
xs:ID; patterns: (urn:uuid:)?[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}|{[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}}); compare: Dev:Identities
|
*Notice:
Elements may have different parent elements. As a consequence they may be used in different contexts.
Please, consider this as well as a user of this wiki as when developing this documentation further.
Aspects that are only relevant with respect to one of several parents should be explained exclusively in the documentation of the respective parent element.
|
Changes 3.1→3.2
The children have changed.
The attributes have been changed.
Semantics
Best Practice / Examples
An interlocking has to handle different route types whose characteristics are defined by the IM. The details are given in the IM’s rule book but are not subject of the data exchange. The generic classification allows the interlocking to attribute the route with a particular set of commands and a set of features, e.g. possible occupation within the running path.
The list of generic route types offers the following possibilities:
- callOn – This is a special route type for situations, where the interlocking cannot fully secure the route for a train but safety is established by operator rules.
- nonElectrified – This is the route type for securing the path of the trains in the standard way but allows the running path to be without electrification, i.e. it shall be used for diesel trains only.
- normal – This is the route type for securing the path of the trains in the standard way.
- occupied – The route leads to an already occupied TVD section, i.e. the destination tracks must be occupied.
- siding – This is a normal route onto the open line, which is destined for entering a key locked siding on that line.
- shunting – Such routes are typically used for splitting or merging formations of railway vehicles with a reduced amount of safety as the train movement is performed on low speed under responsibility of the driver. Parts of the running path can be occupied.
- tunnel – The route leads to a tunnel section, which has restrictions w.r.t. vehicle acceptance, i.e. the vehicles shall be equipped with emergency brake cancellation.
- withoutDependency – The route is used when it leads into a non-supervised area, i.e. only the first part is secured by the interlocking. The safety of the complete route path has to be ensured by operator procedures. It applies for example to "telephone block lines", where there is no technical mean to ensure the safe use of the line between two stations but verbal agreement via telephone is used.
- other:… – The route is of another type. This is the optional extension of the list. Each entry needs to start with the string “other:” and shall have at least two letters in addition.
The extract from the example shows the definition of a standard main route type and a route type for shunting purpose. The selection of route type is an indication for the interlocking for the related commands for route setting and release.
<hasRouteType id="rt_main" genericRouteType="normal">
<designator register="_SimpleRegister" entry="normal main route for trains"/>
</hasRouteType>
<hasRouteType id="rt_shunt" genericRouteType="shunting" >
<designator register="_SimpleRegister" entry="shunting route"/>
</hasRouteType>
Additional Information
Notes
Open Issues