Introduction
Documentation
Syntax
Autoexport from the XML-Schema for element IL:tvdSection of railML ® version 3.3 |
| Documentation
|
A track vacancy detection (TVD) section reports train occupancy to the interlocking. This is a logical unit characterised by the delimiters of the section. Typically, a section is delimited by two insulated track joints or axle counters at the extremities. Sections with a switch or a crossing can have several such limits.
|
| Subschema
|
interlocking
|
| Parents*
|
tvdSections
|
| Children
|
assetName (0..*), belongsToOperationalPoint (0..1), designator (0..*), elementState (0..*), hasCommand (0..*), hasDemarcatingBufferstop (0..2), hasDemarcatingTraindetector (0..*), hasExitSignal (0..2), hasIndication (0..*), hasResetStrategy (0..1), hasTrackElement (0..*), hasTrainNumberField (0..*)
|
Attributes:
- frequency: The frequency in Hertz used for the TVD section in case of a track circuit. Shall be zero for direct current. (optional;
xs:decimal; minInclusive: 0; fractionDigits: 3),
- 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),
- partialRouteReleaseDelay: Delay time after which the section may be released for use in a new route (optional;
xs:duration),
- 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). (optional;
xs:duration),
- technology: The technology used for the TVD section to detect the presence or absence of rail vehicles. (optional;
xs:string; patterns: other:w{2,}; consider Dev:UsingAny too.)
- Possible values:
- axleCounter: The TVD section is formed by axel counter detection points.
- trackCircuit: The TVD section is using track circuit equipment with insulated rail joints or virtual ones as delimiters.,
- elementNumber: element number for internal referencing in the engineering data (optional;
xs:nonNegativeInteger),
- id: the identifier of the object; this can be either of type xs:ID or UUID (obligatory;
xs:ID); 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.
|
Autoexport from the XML-Schema for element IL:tvdSection of railML ® version 3.2 |
| Documentation
|
track vacancy detection (TVD) section reports train occupancy to the interlocking
|
| Subschema
|
interlocking
|
| Parents*
|
tvdSections
|
| Children
|
assetName (0..*), belongsToOperationalPoint (0..1), designator (0..*), hasCommand (0..*), hasDemarcatingBufferstop (0..2), hasDemarcatingTraindetector (0..*), hasExitSignal (0..2), hasIndication (0..*), hasResetStrategy (0..1), hasTrackElement (0..*), hasTrainNumberField (0..*)
|
Attributes:
- frequency: The frequency in Hertz used for the TVD section in case of a track circuit. Shall be zero for direct current. (optional;
xs:decimal; minInclusive: 0; fractionDigits: 3),
- 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),
- partialRouteReleaseDelay: Delay time after which the section may be released for use in a new route (optional;
xs:duration),
- 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). (optional;
xs:duration),
- technology: The technology used for the TVD section to detect the presence or absence of rail vehicles. (optional;
xs:string; patterns: other:w{2,}; consider Dev:UsingAny too.)
- Possible values:
- axleCounter: The TVD section is formed by axel counter detection points.
- trackCircuit: The TVD section is using track circuit equipment with insulated rail joints or virtual ones as delimiters.,
- 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.
|
Autoexport from the XML-Schema for element IL:tvdSection of railML ® version 3.1 |
| 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,}; consider Dev:UsingAny too.)
- 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.
|
Changes 3.1→3.2
There exists an overview of all changes between railML® 3.1 and railML® 3.2 on page Dev:Changes/3.2.
The parents have been changed.
The children have been changed.
The attributes have been changed.
Changes 3.2→3.3
There exists an overview of all changes between railML® 3.2 and railML® 3.3 on page Dev:Changes/3.3.
The element documentation has been changed.
The parents have been changed.
The children have been changed.
The attributes have been changed.
Semantics
Best Practice / Examples
Additional Information
Notes
Open Issues