From railML 3 Wiki
Jump to: navigation, search




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..*), any (0..*), assetName (0..*), belongsToOperationalPoint (0..1), deactivatedBy (0..*), designator (0..*), hasCommand (0..*), hasGateSection (0..*), hasIndication (0..*), hasInterface (0..1), hasTvdSection (0..*), refersTo (1..1)
  • preferredPosition: The preferred position of the tunnel gate. For route dependent gates this would be the blocking position. (optional; xs:string)
Possible values:
  • unknown
  • passableOpen
  • blockingClosed,

  • 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 (optional; 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}\})
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. It is available only in railML® 3.2. Do not hesitate to contact for further questions.


Best Practice / Examples

Additional Information


Open Issues