From railML 3 Wiki
Jump to navigation Jump to search

Automatic Schemaexport for Element trainDetectionElement

Autoexport from the XML-Schema for element IS:trainDetectionElement of railML® version 3.1
Documentation This element is not documented in the schema!
Subschema infrastructure
Parents* trainDetectionElements
Children any (0..*), areaLocation (0..*), designator (0..*), external (0..*), gmlLocations (0..*), isValid (0..*), limitsTrainDetectionElement (0..2), linearLocation (0..*), name (0..*), networkLocation (0..*), spotLocation (0..*)
  • basedOnTemplate: reference to a template train detection element/system (optional; xs:IDREF; 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}\}),

  • type: type of train detector (obligatory; xs:string)
Possible values:
  • axleCounter
  • axleCountingCircuit
  • clearancePoint
  • insulatedRailJoint
  • trackCircuit
  • virtualClearancePoint,

  • detectedObject: object (usually component of the railway vehicle) that is detected by the train detector (optional; xs:string)
Possible values:
  • wheel
  • train
  • endOfTrain
  • axle,

  • detectorMedium: medium (physical principle) that is used for detection by the train detection element (optional; xs:string)
Possible values:
  • radio
  • pneumatic
  • optical
  • mechanical
  • magnetic
  • inductive
  • hydraulic,

  • layout: constructional layout of the train detection element (optional; xs:string)
Possible values:
  • tripleLoop
  • singleSensor
  • singleLoop
  • railCircuitStandAlone
  • doubleSensor
  • doubleLoop,

  • id: the identifier of the object; this can be either of type xs:ID or UUID (obligatory; 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
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.