Autoexport from the XML-Schema for element IL:hasLevelCrossingType of railML® version 3.2 | |
| Documentation | Classification of basic level crossing types. |
| Subschema | interlocking |
| Parents* | usesTypes |
| Children | designator (0..*) |
Attributes:
| |
| *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. | |
IL:hasLevelCrossingType
Jump to navigation
Jump to search
Introduction
Documentation
Syntax
Autoexport from the XML-Schema for element IL:hasLevelCrossingType of railML® version 3.1 | |
| Documentation | Classification of basic level crossing types. |
| Subschema | interlocking |
| Parents* | usesTypes |
| Children | any (0..*), designator (0..1) |
Attributes:
| |
| *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 IM uses normally a couple of standard types of level crossing equipment. They may have more individual interfaces but the major difference for interlocking is depending on the way of control. In the generic type description the following information can be included:
- @isControlType – This describes the way the interlocking controls the level crossing in relation to routes.
- autonomous – The level crossing is acting autonomous from interlocking in terms of activation and deactivation. It gives only feedback of its state to the interlocking. This is normally the way of control for level crossings on the open block line not in proximity of stations or operational control points.
- halfControlled – The level crossing is at least activated from interlocking only for one direction. Deactivation for this direction may be also commanded from interlocking. The remaining functions are autonomous. This applies normally for level crossings on open block line but in proximity of a station. Then the exit direction from the station is controlled from the interlocking.
- fullControlled – The level crossing is activated and deactivated only from interlocking independently of the direction. This is the case for level crossings within stations. The level crossing is activated by route setting and deactivated when the underlying TVD section is released from route.
- manuallyControlled – The level crossing is completely controlled by a separate operator but may indicate its status towards the interlocking. This is combined with @allowsLocalOperation.
- partiallyControlled – The level crossing is mainly operated by a separate operator but can be also operated from the interlocking in a limited way. This is combined with @allowsLocalOperation.
- @allowsLocalOperation – This flag indicates whether the level crossing has means for being operated locally independent from the interlocking.
- @hasBarrier – This flag indicates whether the level crossing has physical barriers to block road traffic. This may influence the way the interlocking is operating the level crossing and the amount of feedbacks.
- @hasTrafficWarning – This flag indicates whether the level crossing has means to indicate its status to road traffic, e.g. traffic warning lights. This may influence the way the interlocking is operating the level crossing and the amount of feedbacks.
The extract shows a level crossing equipped with barriers and traffic signals. It can be operated from onsite and is not activated or deactivated independent from the interlocking.
<hasLevelCrossingType id="lxt01" controlType="fullControlled" allowsLocalOperation="true" hasBarrier="true" hasTrafficWarning="true" >
<designator register="_SimpleRegister" entry="both sided controlled LX"/>
</hasLevelCrossingType>