Introduction
Documentation
Syntax
Autoexport from the XML-Schema for element IL:tunnelGateIL of railML ® version 3.2
|
Documentation
|
The contained tunnelGateIL element
|
Subschema
|
interlocking
|
Parents*
|
tunnelGatesIL
|
Children
|
activationCondition (0..*), assetName (0..*), belongsToOperationalPoint (0..1), deactivatedBy (0..*), designator (0..*), hasCommand (0..*), hasGateSection (0..*), hasIndication (0..*), hasInterface (0..1), hasTvdSection (0..*), refersTo (1..1)
|
Attributes:
- preferredPosition: The preferred position of the tunnel gate. For route dependent gates this would be the blocking position. (optional;
xs:string )
- Possible values:
- blockingClosed: The gate is in a closed position, which blocks the railway traffic through it.
- passableOpen: The gate is in an open position, which allows the passage of railway traffic through it.
- unknown: The gate position is not known,
- typicalTimeToOpen: The typical time required to open the tunnel gate, i.e. the time to bring the gate from blocking into the supervised open/passable position. (optional;
xs:duration ),
- elementNumber: element number for internal referencing in the engineering data (optional;
xs:nonNegativeInteger ),
- 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.
|
This element does not appear in railML® 3.1 within the IL subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further questions.
Changes 3.1→3.2
Introduced with version 3.2.
Semantics
Best Practice / Examples
Additional Information
Notes
Open Issues