IL:tvdSection/3.1

Automatic Schemaexport for Element tvdSection

Autoexport from the XML-Schema for element IL:tvdSection of railML® version 3.1 UML-visualization of IL
Documentation	track vacancy detection (TVD) section reports train occupancy to the interlocking
Subschema	interlocking
Parents*	tvdSections
Children	any (0..*), designator (0..1), hasDemarcatingBufferstop (0..2), hasDemarcatingTraindetector (0..*), hasExitSignal (0..2), hasResetStrategy (0..1)
Attributes: isBerthingTrack: True if this section is part of a berthing track, i.e. track where trains may halt and change direction. Typically, an Interlocking assures that trains progress from section to section in an ordered sequence (aka. two/three phase release). This check would fail when a train changes direction. If this attribute is true, the interlocking doesn't carry out this check for this section. (optional; xs:boolean), residualRouteCancellationDelay: The delay after which the interlocking may clear a partial route left by an unusual train run. The timer starts running when the interlocking accepts the signal man request to clear the section (DE: Restfahrstrasse auflösen) or when the interlocking algorithm detects that the train has set back (automatic route release). (obligatory; xs:duration), partialRouteReleaseDelay: Delay time after which the section may be released for use in a new route (obligatory; xs:duration), technology: the technical type of the TVD section (optional; xs:string; patterns: other:\w{2,}) Possible values: trackCircuit axleCounter, frequency: The frequency in Hertz in case of a track circuit. Shall be zero for direct current. (optional; xs:decimal; minInclusive: 0; fractionDigits: 3), id: unique identifier (optional; 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
*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.