From railML 3 Wiki
Jump to navigation Jump to search




Autoexport from the XML-Schema for element IL:hasIndication of railML® version 3.2
Documentation References to pre-defined indications on HMI for this element.
Subschema interlocking
Parents* combinedRoute,

conflictingRoute, dangerPoint, derailerIL, destinationPoint, endOfTrack, genericDetector, implementsElementGroup, interface, keyLockIL, levelCrossingIL, localOperationArea, movableBridge, movableCrossing, overlap, permissionZone, powerSupplyIL, radioBlockCentre, route, routeEntry, routeExit, routeRelation, routeReleaseGroupAhead, routeReleaseGroupRear, routeSequence, routeStatusIndicator, shuntingZone, signalBox, signalIL, signalIndicator, stationIndicator, switchIL, trackIL, trainNumberField, tunnelGateIL, tvdSection, workZone

Children None
  • entityCode: It is necessary for the coding of command/indication for relay interlockings. Each command/indication is coded of a byte/bit information, but this coding is different for each interlocking instance and therefore also for each infrastructure element instance (optional; xs:string),

  • ref: reference is required because it's the purpose of the element (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}})
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 for further questions.

Changes 3.1→3.2

Introduced with version 3.2.


Best Practice / Examples

Additional Information


Open Issues