Search results

Jump to navigation Jump to search
  • itinerary, key, keyLockIL, keyLockIS, keyLockInState, levelCrossingIL, levelCrossingIS, levelCrossingInState, line, lineLayout, linearElementProjection, loadingGauge
    506 bytes (4 words) - 17:35, 20 April 2020
  • keeper, key, keyLockIL, keyLockIS, keyLockInState, levelCrossingIL, levelCrossingIS, levelCrossingInState, line, linearElementProjection, loadingGauge
    518 bytes (58 words) - 12:39, 8 February 2024
  • keyLockInState, levelCrossingIL, levelCrossingIS, levelCrossingInState, line, loadingGauge, localOperationArea, masterAspect, message, movableCrossing, operationalPoint
    1 KB (156 words) - 17:49, 24 January 2022
  • </tvdSections> <levelCrossingsIL> <levelCrossingIL typicalTimeToClose="PT30S"> <!-- some kind of level crossing type (lxt01) --> <isLevelCrossingType ref="lxt01"/>
    18 KB (1,997 words) - 15:11, 4 June 2022
  • keeper, key, keyLockIL, keyLockIS, keyLockInState, levelCrossingIL, levelCrossingIS, levelCrossingInState, line, linearElementProjection, loadingGauge
    6 KB (5 words) - 15:44, 17 May 2024
  • itinerary, key, keyLockIL, keyLockIS, keyLockInState, levelCrossingIL, levelCrossingIS, levelCrossingInState, line, lineLayout, linearElementProjection, loadingGauge
    7 KB (5 words) - 14:21, 24 January 2020
  • itinerary, key, keyLockIL, keyLockIS, keyLockInState, levelCrossingIL, levelCrossingIS, levelCrossingInState, line, lineLayout, linearElementProjection, loadingGauge
    8 KB (5 words) - 16:13, 5 March 2021
  • keyLockInState, levelCrossingIL, levelCrossingIS, levelCrossingInState, line, loadingGauge, localOperationArea, masterAspect, message, movableCrossing, operationalPoint
    6 KB (5 words) - 14:21, 24 January 2020
  • <releaseTriggerSection> <relatedToTrackAsset> <requiresLevelCrossingInState> <relatedLevelCrossingAndState> <refersToLevelCrossing> <requiresSwitchInPosition> <relatedSwitchAndPosition>
    188 KB (2,767 words) - 13:38, 4 December 2023
  • activation of the level crossing protection trainAutomatic: level crossing is activated automatically from train side trainManual: level crossing is activated
    1,015 bytes (15 words) - 11:37, 13 May 2024
  • gradientCurve, horizontalCurve, keyLockIS, levelCrossingIS, line, loadingGauge, mileageChange, operationalPoint, overCrossing, platform, platformEdge, radioBlockCentreBorder
    515 bytes (4 words) - 18:41, 19 December 2019
  • keyLocksIS (0..1), levelCrossingsIS (0..1), lines (0..1), loadingGauges (0..1), mileageChanges (0..1), operationalPoints (0..1), overCrossings (0..1), platformEdges
    527 bytes (4 words) - 18:42, 19 December 2019
  • gradientCurve, horizontalCurve, keyLockIS, levelCrossingIS, line, loadingGauge, mileageChange, operationalPoint, overCrossing, platform, platformEdge, radioBlockCentreBorder
    518 bytes (9 words) - 18:41, 19 December 2019
  • crossesElement, crossing, customer, derailerIS, detector, electrificationSection, elementState, ellipticalProjection, etcsArea, etcsLevelTransition, genericArea
    512 bytes (58 words) - 12:39, 8 February 2024
  • <requiredLevelCrossingState> – This is the reference to the related level crossing, its state and the level of enforcement. The extract shows the relationship
    3 KB (283 words) - 20:54, 29 January 2020
  • keyLockIS, levelCrossingIS, line, linearPositioningSystem, loadingGauge, netElement, netRelation, networkResource, operationalPoint, overCrossing, platform
    750 bytes (15 words) - 13:44, 18 April 2024
  • requiredLevelCrossingState, requiresLevelCrossingInState Children refersToLevelCrossing (1..1) Attributes: inState: The state (open/closed) the level crossing
    531 bytes (9 words) - 18:49, 19 December 2019
  • gradientCurve, horizontalCurve, keyLockIS, levelCrossingIS, line, loadingGauge, mileageChange, operationalPoint, overCrossing, platform, platformEdge, radioBlockCentreBorder
    604 bytes (23 words) - 16:13, 19 April 2024
  • gradientCurve, horizontalCurve, keyLockIS, levelCrossingIS, line, loadingGauge, mileageChange, operationalPoint, overCrossing, platform, platformEdge, radioBlockCentreBorder
    608 bytes (23 words) - 16:14, 19 April 2024
  • after the level crossing was triggered. @delay – The time that has to elapse for the signal to change from stop to any proceed aspect after the level crossing
    4 KB (465 words) - 12:14, 30 May 2020
  • track/line at same level (usually only roads, streets and ways), it shall be named levelCrossing in railML 3 a railway track crossing another railway track
    3 KB (216 words) - 13:04, 13 May 2024
  • XML-Schema for element IL:levelCrossingInState of railML® version 3.2 UML-visualization of IL Documentation reference to any level crossing and its state inside
    523 bytes (9 words) - 18:49, 19 December 2019
  • side and the level of enforcement. For details refer to chapter 1.1.15below. <levelCrossingInState>- The reference to any level crossing which shall be
    3 KB (476 words) - 19:35, 29 January 2020
  • together with the protection side and the level of enforcement. <levelCrossingInState>- The reference to any level crossing which shall be in a particular state
    3 KB (452 words) - 05:55, 18 April 2022
  • track/line at same level (usually only roads, streets and ways), it shall be named levelCrossing in railML 3 a railway track crossing another railway track
    3 KB (242 words) - 11:48, 13 May 2024
  • gradientCurve, horizontalCurve, keyLockIS, levelCrossingIS, line, loadingGauge, mileageChange, operationalPoint, overCrossing, platform, platformEdge, radioBlockCentreBorder
    949 bytes (15 words) - 16:52, 19 April 2024
  • border, bufferStop, crossing, derailerIS, detector, electrificationSection, etcsArea, etcsLevelTransition, keyLockIS, levelCrossingIS, line, loadingGauge
    517 bytes (38 words) - 21:50, 25 April 2022
  • border, bufferStop, crossing, derailerIS, detector, electrificationSection, etcsArea, etcsLevelTransition, keyLockIS, levelCrossingIS, line, loadingGauge
    516 bytes (58 words) - 12:39, 8 February 2024
  • describes the way the interlocking controls the level crossing in relation to routes. autonomous – The level crossing is acting autonomous from interlocking in
    3 KB (405 words) - 15:31, 29 October 2023
  • refersToLevelCrossing (1..*) Attributes: type: type of the level crossing signal (obligatory; xs:string) Possible values: supervision: final level crossing
    524 bytes (9 words) - 18:44, 19 December 2019
  • element IL:requiredLevelCrossingState of railML® version 3.2 UML-visualization of IL Documentation References to a particular level crossing and its required
    544 bytes (9 words) - 12:00, 30 May 2020
  • element IL:requiresLevelCrossingInState of railML® version 3.2 UML-visualization of IL Documentation The reference to any level crossing in the overlap required
    546 bytes (9 words) - 12:01, 30 May 2020
  • changed. The children have changed. The attributes have been changed. The level crossing is automatically deactivated after the train has passed and no activation
    1 KB (101 words) - 12:13, 30 May 2020
  • @comString. A level crossing is a typical field element with a special interface to the interlocking. Here is the example of a particular level crossing type as
    13 KB (1,119 words) - 17:46, 30 January 2020
  • XML-Schema for element IL:levelCrossingsIL of railML® version 3.2 UML-visualization of IL Documentation container for all levelCrossingIL elements Subschema
    519 bytes (10 words) - 18:47, 19 December 2019
  • horizontalCurve, infrastructureManager, infrastructureState, keyLockIS, levelCrossingIS, line, linearElementProjection, linearPositioningSystem, loadingGauge
    507 bytes (58 words) - 18:40, 19 December 2019
  • XML-Schema for element IS:levelCrossingsIS of railML® version 3.2 UML-visualization of IS Documentation container element for all levelCrossing elements Subschema
    519 bytes (0 words) - 18:43, 19 December 2019
  • its state plus the level of enforcement Subschema interlocking Parents* levelCrossingInState Children relatedLevelCrossingAndState (1..1) Attributes: isNegated:
    533 bytes (0 words) - 18:49, 19 December 2019
  • controlled): IL:LevelCrossingIL @isLevelCrossingType - related track element, TVD section: LevelCrossingIS @trackPosition, LevelCrossingIL @hasTvdSection
    11 KB (828 words) - 13:25, 13 March 2023
  • destinationPoint, endOfTrack, genericDetector, keyLockIL, levelCrossingIL, movableBridge, movableCrossing, routeEntry, routeExit, signalIL, switchIL, trackIL
    511 bytes (15 words) - 18:47, 19 December 2019
  • is crossed by a bridge, level crossing or tunnel Subschema infrastructure Parents* levelCrossingIS, overCrossing, underCrossing Children name (0..*) Attributes:
    7 KB (15 words) - 10:54, 13 May 2024
  • version 3.2 UML-visualization of IL Documentation The activation of the level crossing is done by a train detection element. Subschema interlocking Parents*
    514 bytes (9 words) - 18:48, 19 December 2019
  • diamond crossing to interconnect two parallel tracks. This complete arrangement of four switches and the crossing is called “scissor crossing” or “scissor
    15 KB (1,510 words) - 19:13, 14 February 2022
  • element IL:isLevelCrossingType of railML® version 3.2 UML-visualization of IL Documentation Reference to the basic type of level crossing. It refers to
    522 bytes (5 words) - 18:47, 19 December 2019
  • for element IL:refersToLevelCrossing of railML® version 3.2 UML-visualization of IL Documentation The reference to the level crossing. Subschema interlocking
    524 bytes (5 words) - 18:49, 19 December 2019
  • bufferStop, crossing, derailerIS, electrificationSection, keyLockIS, levelCrossingIS, line, loadingGauge, operationalPoint, overCrossing, platform, restrictionArea
    511 bytes (58 words) - 18:42, 19 December 2019
  • protection of the level crossing Subschema infrastructure Parents* levelCrossingIS Children None Attributes: acoustic: technical level crossing protection: acoustic
    513 bytes (5 words) - 18:43, 19 December 2019
  • UML-visualization of IL Documentation Reference to physical description of level crossing interface with list of commands to the field and notifications from
    515 bytes (9 words) - 18:47, 19 December 2019
  • available only in railML® 3.1. There exists an element <generic:refersToLevelCrossing> that might have replaced it. Do not hesitate to contact railML.org for
    524 bytes (58 words) - 18:44, 19 December 2019
  • <relatedToTrackAsset> <requiresLevelCrossingInState> <any> <designator> <relatedLevelCrossingAndState> <any> <designator> <refersToLevelCrossing> <requiresSwitchInPosition>
    125 KB (1,906 words) - 03:09, 26 October 2023
  • track. Subschema interlocking Parents* derailerIL, keyLockIL, levelCrossingIL, movableCrossing, overlap, route, routeReleaseGroupAhead, routeReleaseGroupRear
    516 bytes (15 words) - 18:47, 19 December 2019
  • its position plus the level of enforcement Subschema interlocking Parents* crossingInPosition Children relatedCrossingAndPosition (1..1) Attributes: isNegated:
    534 bytes (0 words) - 18:49, 19 December 2019
  • element IL:requiredCrossingPosition of railML® version 3.2 UML-visualization of IL Documentation References to a particular movable crossing and its required
    542 bytes (9 words) - 11:59, 30 May 2020
  • either by a <crossing> in case of a simple crossing, or by a <switchIS> of type doubleSwitchCrossing or singleSwitchCrossing. <IS:underCrossing>, <IS:overCrossing>
    4 KB (579 words) - 16:49, 13 March 2023
  • version 3.2 UML-visualization of IL Documentation Activation of the level crossing may be delayed, depending on the aspect of the approach signal, thus
    521 bytes (9 words) - 18:47, 19 December 2019
  • over or next to the railway track, e.g. <balises>, <platformEdges> and <levelCrossingsIS>. See <functionalInfrastructure> Further located elements encompass
    3 KB (288 words) - 18:47, 20 March 2024
  • version 3.2 UML-visualization of IL Documentation After activation of the level crossing the opening of a signal is delayed. Subschema interlocking Parents*
    518 bytes (9 words) - 18:47, 19 December 2019
  • implementsElementGroup, interface, keyLockIL, levelCrossingIL, localOperationArea, movableBridge, movableCrossing, overlap, permissionZone, powerSupplyIL, radioBlockCentre
    528 bytes (38 words) - 16:15, 5 March 2021
  • IS:etcsLevelCrossing of railML® version 3.2 UML-visualization of IS Documentation container element for all ETCS related information of a level crossing
    520 bytes (38 words) - 21:50, 25 April 2022
  • implementsElementGroup, interface, keyLockIL, levelCrossingIL, localOperationArea, movableBridge, movableCrossing, overlap, permissionZone, powerSupplyIL, radioBlockCentre
    716 bytes (61 words) - 15:10, 14 May 2022
  • implementsElementGroup, interface, keyLockIL, levelCrossingIL, localOperationArea, movableBridge, movableCrossing, overlap, permissionZone, powerSupplyIL, radioBlockCentre
    516 bytes (38 words) - 16:16, 5 March 2021
  • which are used to indicate the level crossing status related to this track. Subschema interlocking Parents* levelCrossingIL Children None Attributes: ref:
    524 bytes (38 words) - 16:16, 5 March 2021
  • Please note To provide information about the allowed speed at switches and crossings, please use the attributes <*branch>@speedBranching and <*branch>@speedJoining
    5 KB (519 words) - 10:51, 15 May 2024
  • indicating the Level of Control which is most often ‘full control’. Track assets that aren't controlled by the interlocking, e.g. field controlled level crossing
    521 bytes (9 words) - 18:51, 19 December 2019
  • hasDetectorTypes (0..*), hasElementGroupType (0..*), hasHmiIndication (0..*), hasLevelCrossingType (0..*), hasOperatorCommand (0..*), hasRouteType (1..*), hasTVDresetStrategy
    512 bytes (8 words) - 18:52, 19 December 2019
  • is available only in railML® 3.2. There exists an element <CO:refersToLevelCrossing> that might have preceded it. Do not hesitate to contact railML.org for
    529 bytes (58 words) - 12:40, 8 February 2024
  • <relatedDetectorAndState> LevelCrossingAndState – This combines a levelCrossingIL with a possible state. <relatedLevelCrossingAndState> LockAndState – This
    5 KB (613 words) - 01:23, 16 May 2024
  • implementsElementGroup, interface, keyLockIL, levelCrossingIL, localOperationArea, movableBridge, movableCrossing, permissionZone, shuntingZone, signalIL, switchIL
    517 bytes (58 words) - 12:41, 8 February 2024
  • isDangerSignal (0..1), isEtcsSignal (0..1), isInformationSignal (0..1), isLevelCrossingSignal (0..1), isMilepost (0..1), isSpeedSignal (0..1), isStopPost (0
    623 bytes (15 words) - 10:23, 13 May 2024
  • (0..1), keyLocksIL (0..1), keys (0..1), levelCrossingsIL (0..1), localOperationAreas (0..1), movableCrossings (0..1), overlaps (0..1), permissionZones
    2 KB (272 words) - 12:02, 21 May 2022
  • keyLocksIL (0..1), keys (0..1), levelCrossingsIL (0..1), localOperationAreas (0..1), movableBridges (0..1), movableCrossings (0..1), overlaps (0..1), permissionZones
    3 KB (359 words) - 13:19, 29 May 2022
  • objectName (0..*), overlapRelease (0..1), relatedToTrackAsset (0..1), requiresLevelCrossingInState (0..*), requiresSwitchInPosition (0..*) Attributes: length: Alternatively
    5 KB (609 words) - 15:20, 4 April 2024
  • status to the interlocking, e.g. an autonomous working level crossing. In order to mark this level of control authority the attribute @extentOfControl is
    1 KB (154 words) - 16:40, 30 January 2020
  • </netRelation> </netRelations> <networks> <network id="nw01"> <level id="lv0" descriptionLevel="Micro"> <networkResource ref="ne_a01"/> <networkResource ref="ne_a02"/>
    9 KB (931 words) - 12:07, 4 April 2024
  • operated like the barriers of a level crossing with each route set. Therefore the tunnelGateIL is modelled similar to levelCrossingIL with activation conditions
    5 KB (599 words) - 14:26, 27 May 2022
  • is used for logical locking connections between switches, derailers, level crossings, or other signalling components Subschema infrastructure Parents* keyLocksIS
    512 bytes (15 words) - 18:43, 19 December 2019
  • IS:etcsArea IS:etcsAreas IS:etcsElectrification IS:etcsLevelCrossing IS:etcsLevelTransition IS:etcsLevelTransitions IS:from IS:functionalType IS:genericArea
    3 KB (758 words) - 14:47, 27 June 2022
  • Automatic Schemaexport for Element levelCrossingsIS
    380 bytes (5 words) - 16:14, 5 March 2021
  • Automatic Schemaexport for Element levelCrossingsIS
    380 bytes (5 words) - 18:43, 19 December 2019
  • Automatic Schemaexport for Element isLevelCrossingSignal
    1 KB (5 words) - 14:21, 24 January 2020
  • Automatic Schemaexport for Element isLevelCrossingSignal
    1 KB (5 words) - 15:46, 17 May 2024
  • Automatic Schemaexport for Element levelCrossingsIL
    354 bytes (5 words) - 18:47, 19 December 2019
  • Automatic Schemaexport for Element levelCrossingsIL
    369 bytes (5 words) - 21:51, 25 April 2022
  • Automatic Schemaexport for Element etcsLevelCrossing
    559 bytes (5 words) - 21:50, 25 April 2022
  • Automatic Schemaexport for Element relatedLevelCrossingAndState
    1 KB (5 words) - 12:42, 8 February 2024
  • Automatic Schemaexport for Element isLevelCrossingType
    831 bytes (5 words) - 16:16, 5 March 2021
  • Automatic Schemaexport for Element isLevelCrossingType
    830 bytes (5 words) - 18:17, 23 December 2019
  • Automatic Schemaexport for Element refersToLevelCrossing
    769 bytes (5 words) - 18:18, 23 December 2019
  • Automatic Schemaexport for Element refersToLevelCrossing
    770 bytes (5 words) - 16:17, 5 March 2021
  • Automatic Schemaexport for Element refersToLevelCrossing
    791 bytes (5 words) - 18:17, 23 December 2019
  • Automatic Schemaexport for Element refersToLevelCrossing
    799 bytes (5 words) - 15:46, 17 May 2024
  • Automatic Schemaexport for Element levelCrossingIL
    4 KB (5 words) - 15:47, 17 May 2024
  • Automatic Schemaexport for Element relatedLevelCrossingAndState
    1 KB (5 words) - 14:22, 24 January 2020
  • Automatic Schemaexport for Element hasLevelCrossingType
    2 KB (5 words) - 15:48, 17 May 2024
  • Automatic Schemaexport for Element requiresLevelCrossingInState
    1 KB (5 words) - 12:42, 8 February 2024
  • Automatic Schemaexport for Element requiredLevelCrossingState
    1 KB (5 words) - 12:42, 8 February 2024
  • Automatic Schemaexport for Element levelCrossingIS
    5 KB (5 words) - 15:46, 17 May 2024
  • Automatic Schemaexport for Element hasLevelCrossingTrack
    838 bytes (5 words) - 16:16, 5 March 2021
  • Automatic Schemaexport for Element levelCrossingInState
    995 bytes (5 words) - 14:22, 24 January 2020
  • Automatic Schemaexport for Element levelCrossingInState
    977 bytes (5 words) - 15:48, 17 May 2024
  • Automatic Schemaexport for Element levelCrossingIL
    3 KB (5 words) - 14:21, 24 January 2020
  • its state plus the level of enforcement Subschema interlocking Parents* levelCrossingInState Children relatedLevelCrossingAndState (1..1) Attributes: isNegated:
    1 KB (5 words) - 12:42, 8 February 2024
  • Automatic Schemaexport for Element requiresLevelCrossingInState
    1 KB (5 words) - 14:22, 24 January 2020
  • Automatic Schemaexport for Element requiredLevelCrossingState
    1 KB (5 words) - 14:22, 24 January 2020
  • Automatic Schemaexport for Element hasLevelCrossingType
    1 KB (5 words) - 14:22, 24 January 2020
  • plus the level of enforcement Subschema interlocking Parents* levelCrossingInState Children any (0..*), designator (0..1), relatedLevelCrossingAndState
    1 KB (5 words) - 14:22, 24 January 2020
  • Automatic Schemaexport for Element levelCrossingIS
    4 KB (5 words) - 14:21, 24 January 2020
  • for all dedicated physical interface elements to another signalbox, level crossing or other special device Subschema interlocking Parents* assetsForInterlocking
    513 bytes (10 words) - 18:48, 19 December 2019
  • protection of the level crossing Subschema infrastructure Parents* levelCrossingIS Children None Attributes: acoustic: technical level crossing protection: acoustic
    2 KB (5 words) - 12:40, 8 February 2024
  • protection of the level crossing Subschema infrastructure Parents* levelCrossingIS Children None Attributes: barriers: technical level crossing protection: barriers;
    2 KB (5 words) - 18:16, 23 December 2019
  • it is not really a main signal. Examples are the extra protection of level crossings or the case of the destination (berthing) track in a station, when it
    9 KB (1,314 words) - 10:15, 19 May 2023
  • its position plus the level of enforcement Subschema interlocking Parents* crossingInPosition Children relatedCrossingAndPosition (1..1) Attributes: isNegated:
    1 KB (5 words) - 12:42, 8 February 2024
  • Documentation reference to any switchable element (keylock, switch, derailer, level crossing etc.), which is released for local operation, when the work zone is
    528 bytes (11 words) - 18:49, 19 December 2019
  • position plus the level of enforcement Subschema interlocking Parents* crossingInPosition Children any (0..*), designator (0..1), relatedCrossingAndPosition (1
    1 KB (5 words) - 14:22, 24 January 2020
  • version 3.2 UML-visualization of IL Documentation The activation of the level crossing is done by a train detection element. Subschema interlocking Parents*
    740 bytes (5 words) - 17:41, 15 January 2024
  • version 3.1 UML-visualization of IL Documentation The activation of the level crossing is done by a train detection element. Subschema interlocking Parents*
    1 KB (5 words) - 14:22, 24 January 2020
  • border, bufferStop, crossing, derailerIS, detector, electrificationSection, etcsArea, etcsLevelTransition, keyLockIS, levelCrossingIS, line, loadingGauge
    2 KB (5 words) - 15:45, 17 May 2024
  • border, bufferStop, crossing, derailerIS, detector, electrificationSection, etcsArea, etcsLevelTransition, keyLockIS, levelCrossingIS, line, loadingGauge
    2 KB (5 words) - 15:45, 17 May 2024
  • balise, baliseGroup, border, bufferStop, crossing, derailerIS, detector, electrificationSection, etcsArea, etcsLevelTransition, genericArea, geometricPositioningSystem
    3 KB (5 words) - 12:39, 8 February 2024
  • Automatic Schemaexport for Element requiredCrossingPosition
    1 KB (5 words) - 12:42, 8 February 2024
  • Automatic Schemaexport for Element requiredCrossingPosition
    1 KB (5 words) - 14:22, 24 January 2020
  • description of deactivation conditions for this level crossing. Subschema interlocking Parents* levelCrossingIL, tunnelGateIL Children tvdDetectorRef (1..1)
    603 bytes (5 words) - 21:51, 25 April 2022
  • keyLocksIS (0..1), levelCrossingsIS (0..1), lines (0..1), loadingGauges (0..1), mileageChanges (0..1), operationalPoints (0..1), overCrossings (0..1), platformEdges
    2 KB (5 words) - 21:49, 25 April 2022
  • Parents* levelCrossingIS, overCrossing, underCrossing Children name (0..*) Attributes: type: type of the element that is crossed by the over/under/level crossing
    2 KB (5 words) - 18:16, 23 December 2019
  • gradientCurve, horizontalCurve, keyLockIS, levelCrossingIS, line, loadingGauge, mileageChange, operationalPoint, overCrossing, platform, platformEdge, radioBlockCentreBorder
    2 KB (5 words) - 12:39, 8 February 2024
  • gradientCurve, horizontalCurve, keyLockIS, levelCrossingIS, line, loadingGauge, mileageChange, operationalPoint, overCrossing, platform, platformEdge, radioBlockCentreBorder
    3 KB (5 words) - 12:39, 8 February 2024
  • is crossed by a bridge, level crossing or tunnel Subschema infrastructure Parents* levelCrossingIS, overCrossing, underCrossing Children name (0..*) Attributes:
    4 KB (5 words) - 15:46, 17 May 2024
  • version 3.2 UML-visualization of IL Documentation After activation of the level crossing the opening of a signal is delayed. Subschema interlocking Parents*
    573 bytes (5 words) - 21:51, 25 April 2022
  • of the possible activation conditions of this level crossing. Subschema interlocking Parents* levelCrossingIL, tunnelGateIL Children activatedBy (1..*),
    1 KB (5 words) - 12:41, 8 February 2024
  • gradientCurve, horizontalCurve, keyLockIS, levelCrossingIS, line, loadingGauge, mileageChange, operationalPoint, overCrossing, platform, platformEdge, radioBlockCentreBorder
    2 KB (5 words) - 21:49, 25 April 2022
  • crossesElement, crossing, customer, derailerIS, detector, electrificationSection, elementState, ellipticalProjection, etcsArea, etcsLevelTransition, genericArea
    5 KB (5 words) - 15:44, 17 May 2024
  • railway infrastructure elements Switch Crossing Track (Rail) Catenary Bridge Tunnel Embankments Line Section Level Crossing
    10 KB (129 words) - 16:01, 27 September 2023
  • (input for the start of an ETCS Level 2 trackside project based on a centralized technical solution; Details for ETCS Level 1 to follow with railML V3.3)
    5 KB (441 words) - 09:30, 12 June 2023
  • description of deactivation conditions for this level crossing. Subschema interlocking Parents* levelCrossingIL Children any (0..*), designator (0..1), tvdDetectorRef
    1 KB (5 words) - 14:21, 24 January 2020
  • version 3.2 UML-visualization of IL Documentation Activation of the level crossing may be delayed, depending on the aspect of the approach signal, thus
    944 bytes (5 words) - 21:51, 25 April 2022
  • passing speed when LX is in unprotected mode Subschema generic Parents* levelCrossingIS Children None Attributes: ref: reference is required because it's the
    526 bytes (58 words) - 12:40, 8 February 2024
  • UML-visualization of IL Documentation Reference to physical description of level crossing interface with list of commands to the field and notifications from
    965 bytes (5 words) - 14:21, 24 January 2020
  • UML-visualization of IL Documentation Reference to physical description of level crossing interface with list of commands to the field and notifications from
    1 KB (5 words) - 21:51, 25 April 2022
  • gradientCurve, horizontalCurve, keyLockIS, levelCrossingIS, line, loadingGauge, mileageChange, operationalPoint, overCrossing, platform, platformEdge, radioBlockCentreBorder
    2 KB (5 words) - 21:49, 25 April 2022
  • gradientCurve, horizontalCurve, keyLockIS, levelCrossingIS, line, loadingGauge, mileageChange, operationalPoint, overCrossing, platform, platformEdge, radioBlockCentreBorder
    3 KB (5 words) - 15:45, 17 May 2024
  • of the possible activation conditions of this level crossing. Subschema interlocking Parents* levelCrossingIL Children activatedBy (1..*), any (0..*), aspectRelatedDelay
    1 KB (5 words) - 14:21, 24 January 2020
  • (0..1), bufferStops (0..1), crossings (0..1), derailersIS (0..1), electrifications (0..1), keyLocksIS (0..1), levelCrossingsIS (0..1), lines (0..1), loadingGauges
    2 KB (5 words) - 14:21, 24 January 2020
  • version 3.1 UML-visualization of IL Documentation Activation of the level crossing may be delayed, depending on the aspect of the approach signal, thus
    1 KB (5 words) - 14:22, 24 January 2020
  • version 3.1 UML-visualization of IL Documentation After activation of the level crossing the opening of a signal is delayed. Subschema interlocking Parents*
    1 KB (5 words) - 14:22, 24 January 2020
  • indicating the Level of Control which is most often ‘full control’. Track assets that aren't controlled by the interlocking, e.g. field controlled level crossing
    1 KB (5 words) - 12:42, 8 February 2024
  • border, bufferStop, crossing, derailerIS, electrificationSection, geometryPoint, gradientCurve, horizontalCurve, keyLockIS, levelCrossingIS, line, loadingGauge
    2 KB (5 words) - 14:21, 24 January 2020
  • indicating the Level of Control which is most often ‘full control’. Track assets that aren't controlled by the interlocking, e.g. field controlled level crossing
    1 KB (5 words) - 14:22, 24 January 2020
  • bufferStop, crossing, derailerIS, electrificationSection, keyLockIS, levelCrossingIS, line, loadingGauge, operationalPoint, overCrossing, platform, restrictionArea
    2 KB (5 words) - 18:42, 19 December 2019
  • This element does not appear in railML® 3.2 within the IS subschema. It is available only in railML® . Do not hesitate to contact railML.org for further
    522 bytes (67 words) - 16:14, 5 March 2021
  • destinationPoint, endOfTrack, genericDetector, keyLockIL, levelCrossingIL, movableBridge, movableCrossing, routeEntry, routeExit, signalIL, switchIL, trackIL
    1 KB (5 words) - 21:51, 25 April 2022
  • derailerIL, destinationPoint, genericDetector, keyLockIL, levelCrossingIL, movableCrossing, routeEntry, routeExit, signalIL, switchIL Children None Attributes:
    1 KB (5 words) - 14:21, 24 January 2020
  • with uneven elasticity like bridges, tunnels, platforms, level crossings or switches/crossings is another important ingredient for efficient track works
    5 KB (737 words) - 16:12, 15 April 2024
  • border, bufferStop, crossing, derailerIS, electrificationSection, geometryPoint, gradientCurve, horizontalCurve, keyLockIS, levelCrossingIS, line, loadingGauge
    2 KB (5 words) - 14:21, 24 January 2020
  • implementsElementGroup, interface, keyLockIL, levelCrossingIL, localOperationArea, movableBridge, movableCrossing, permissionZone, shuntingZone, signalIL, switchIL
    1 KB (5 words) - 15:47, 17 May 2024
  • flank protection, TVD sections, intermediate signals, movable elements, level crossings etc. Although they are naturally important to route setting, they are
    9 KB (1,077 words) - 08:15, 7 May 2022
  • for all dedicated physical interface elements to another signalbox, level crossing or other special device Subschema interlocking Parents* assetsForInterlocking
    425 bytes (5 words) - 21:52, 25 April 2022
  • requiredCrossingPosition (0..*), requiredDerailerPosition (0..*), requiredDetectorState (0..*), requiredKeyLockState (0..*), requiredLevelCrossingState (0
    1 KB (5 words) - 14:22, 24 January 2020
  • element Subschema interlocking Parents* derailerIL, keyLockIL, levelCrossingIL, movableCrossing, overlap, route, routeReleaseGroupAhead, routeReleaseGroupRear
    1 KB (5 words) - 14:21, 24 January 2020
  • detectorInState (0..*), isLimitedBy (1..*), keyLockInState (0..*), levelCrossingInState (0..*), releasedForLocalOperation (0..*), signalWithAspect (0..*), switchInPosition
    1 KB (5 words) - 14:22, 24 January 2020
  • track. Subschema interlocking Parents* derailerIL, keyLockIL, levelCrossingIL, movableCrossing, overlap, route, routeReleaseGroupAhead, routeReleaseGroupRear
    1 KB (5 words) - 21:51, 25 April 2022
  • detectorInState (0..*), isLimitedBy (1..*), keyLockInState (0..*), levelCrossingInState (0..*), releasedForLocalOperation (0..*), signalWithAspect (0
    2 KB (5 words) - 14:22, 24 January 2020
  • requiredCrossingPosition (0..*), requiredDerailerPosition (0..*), requiredDetectorState (0..*), requiredKeyLockState (0..*), requiredLevelCrossingState (0
    2 KB (5 words) - 15:48, 17 May 2024
  • border, bufferStop, crossing, derailerIS, electrificationSection, geometryPoint, gradientCurve, horizontalCurve, keyLockIS, levelCrossingIS, line, loadingGauge
    2 KB (5 words) - 14:21, 24 January 2020
  • border, bufferStop, crossing, derailerIS, electrificationSection, geometryPoint, gradientCurve, horizontalCurve, keyLockIS, levelCrossingIS, line, loadingGauge
    2 KB (5 words) - 14:21, 24 January 2020
  • horizontalCurve, infrastructureManager, infrastructureState, keyLockIS, levelCrossingIS, line, linearElementProjection, linearPositioningSystem, loadingGauge
    3 KB (5 words) - 11:56, 14 February 2021
  • single switch crossings. <crossing> element is only used for simple crossings. Article Dev:Connection_between_tracks#Double_Switch_Crossing in the railML®
    29 KB (2,876 words) - 14:34, 13 March 2024
  • hasAspect (2..*), hasDetectorTypes (0..*), hasElementGroupType (0..*), hasLevelCrossingType (0..*), hasRouteType (1..*), hasTVDresetStrategy (0..*) Attributes:
    652 bytes (5 words) - 14:22, 24 January 2020
  • (0..1), keyLocksIL (0..1), keys (0..1), levelCrossingsIL (0..1), localOperationAreas (0..1), movableCrossings (0..1), overlaps (0..1), permissionZones
    2 KB (5 words) - 14:21, 24 January 2020
  • implementsElementGroup, interface, keyLockIL, levelCrossingIL, localOperationArea, movableBridge, movableCrossing, overlap, permissionZone, powerSupplyIL, radioBlockCentre
    2 KB (5 words) - 21:51, 25 April 2022
  • keyLockIS, levelCrossingIS, line, linearPositioningSystem, loadingGauge, netElement, netRelation, networkResource, operationalPoint, overCrossing, platform
    2 KB (5 words) - 14:21, 24 January 2020
  • hasDetectorTypes (0..*), hasElementGroupType (0..*), hasHmiIndication (0..*), hasLevelCrossingType (0..*), hasOperatorCommand (0..*), hasRouteType (1..*), hasTVDresetStrategy
    801 bytes (5 words) - 16:18, 5 March 2021
  • implementsElementGroup, interface, keyLockIL, levelCrossingIL, localOperationArea, movableBridge, movableCrossing, overlap, permissionZone, powerSupplyIL, radioBlockCentre
    3 KB (5 words) - 21:51, 25 April 2022
  • implementsElementGroup, interface, keyLockIL, levelCrossingIL, localOperationArea, movableBridge, movableCrossing, overlap, permissionZone, powerSupplyIL, radioBlockCentre
    3 KB (5 words) - 21:51, 25 April 2022
  • keyLocksIL (0..1), keys (0..1), levelCrossingsIL (0..1), localOperationAreas (0..1), movableBridges (0..1), movableCrossings (0..1), overlaps (0..1), permissionZones
    3 KB (5 words) - 15:47, 17 May 2024
  • border, bufferStop, crossing, derailerIS, electrificationSection, geometryPoint, gradientCurve, horizontalCurve, keyLockIS, levelCrossingIS, line, loadingGauge
    3 KB (5 words) - 14:21, 24 January 2020
  • *), hasIndication (0..*), isLimitedBy (0..*), keyLockInState (0..*), levelCrossingInState (0..*), releasedForLocalOperation (0..*), signalWithAspect (0
    3 KB (5 words) - 15:48, 17 May 2024
  • simple crossing at the topological level, at least four net elements must be defined (ellipses) to go through straight branches of the crossing ‒ from
    24 KB (2,447 words) - 14:36, 13 March 2024
  • over or next to the railway track, e.g. balises, platform edges, and level crossings. Further located elements encompass elements that are closely linked
    10 KB (1,041 words) - 10:56, 2 May 2024
  • passing speed when LX is in unprotected mode Subschema generic Parents* levelCrossingIS Children None Attributes: ref: reference is required because it's the
    813 bytes (5 words) - 15:46, 17 May 2024
  • is used for logical locking connections between switches, derailers, level crossings, or other signalling components Subschema infrastructure Parents* keyLocksIS
    1 KB (5 words) - 15:46, 17 May 2024
  • *), hasIndication (0..*), isLimitedBy (0..*), keyLockInState (0..*), levelCrossingInState (0..*), releasedForLocalOperation (0..*), signalWithAspect (0
    3 KB (5 words) - 15:48, 17 May 2024
  • Documentation reference to any switchable element (keylock, switch, derailer, level crossing etc.), which is released for local operation, when the work zone is
    924 bytes (5 words) - 16:17, 5 March 2021
  • Operation Topology micro level topology (tracks + track nodes) macro level topology (lines + operational points) support of different levels of detail location
    2 KB (169 words) - 11:34, 12 April 2024
  • includes a switch crossing. Simple crossings do not allow the train to get from one track to another and are represented by the <crossing> element. In railML®
    18 KB (2,052 words) - 18:20, 15 April 2024
  • isLimitedBy (0..*), overlapRelease (0..1), relatedToTrackAsset (0..1), requiresLevelCrossingInState (0..*), requiresSwitchInPosition (0..*) Attributes: releaseSpeed:
    2 KB (5 words) - 14:22, 24 January 2020
  • objectName (0..*), overlapRelease (0..1), relatedToTrackAsset (0..1), requiresLevelCrossingInState (0..*), requiresSwitchInPosition (0..*) Attributes: length: Alternatively
    2 KB (5 words) - 15:48, 17 May 2024
  • Constraints Dev:Railway switch IS Dev:Double and single switch crossing IS Dev:Simple crossing in a context of diamond crossover IS Dev:Requirements for exchanging
    702 bytes (25 words) - 14:53, 7 December 2023
  • the understanding of railway software operations for users with varying levels of understanding. All information added to the Wiki should be backed by
    11 KB (1,424 words) - 18:13, 15 April 2024
  • position Bridges, tunnels: position, length, height, cross section profile Level crossings: position, width
    3 KB (367 words) - 13:49, 13 March 2023
  • documentation VzG Catenary system technical electrical documentation VzG Level Crossings installation documentation VzG plattforms building, installation documentation
    3 KB (117 words) - 13:45, 13 March 2023
  • isDangerSignal (0..1), isEtcsSignal (0..1), isInformationSignal (0..1), isLevelCrossingSignal (0..1), isMilepost (0..1), isSpeedSignal (0..1), isStopPost (0
    4 KB (5 words) - 15:46, 17 May 2024
  • (physical and virtual) are required track circuits horizontal curves level crossings tunnels bridges electrification changes – incl. signals for electric
    3 KB (427 words) - 17:57, 27 June 2022
  • axle counter)…..) Position of elements Block interface to foreign IXL Level crossing Tunnel gates Bascule bridges Slide detector
    1 KB (119 words) - 13:51, 13 March 2023
  • isDangerSignal (0..1), isEtcsSignal (0..1), isInformationSignal (0..1), isLevelCrossingSignal (0..1), isMilepost (0..1), isSpeedSignal (0..1), isStopPost (0
    3 KB (5 words) - 14:21, 24 January 2020
  • case of a switch fault Signaling type of this SCWS (stationary, ETCS Level 1, ETCS Level 2) Supervision of free route in seconds Workplace data Element names
    4 KB (571 words) - 13:51, 13 March 2023
  • (rock (rough)/concrete (smooth)), Km from , Km to Trollunga, 45m², rock Level crossings Name, km Jeløygate, 34,123 Km   Train detection element (Track circuit
    4 KB (198 words) - 16:57, 13 February 2023
  • (all elements which shall be operable: TVD sections, points, signals, level crossings etc.) Permission/operating zones including shunting areas for temporary
    2 KB (209 words) - 13:52, 13 March 2023
  • crossSection, kind, name, *Name der unterquerten Straße bzw. Flusses) <levelCrossings> (id, name, pos, absPos, angle, protection, ocpStationRef, *Bezeichnung
    3 KB (335 words) - 13:48, 13 March 2023
  • speed per leg, kind of point machine(s), energy and information supply Level crossings: name, position, construction details, functional details, energy and
    3 KB (367 words) - 13:47, 13 March 2023
  • it is not really a main signal. Examples are the extra protection of level crossings or the case of the destination (berthing) track in a station, when it
    7 KB (5 words) - 15:48, 17 May 2024
  • the time table. That means that the train is not allowed to activate level crossings before the train routes is set based on the time table. The timetable
    5 KB (558 words) - 13:53, 13 March 2023
  • transmitted back from the TMS to TCS. This enables the TCS to also work on VSTP level. Timetable data has to be exchanged in different situations. There are at
    16 KB (1,744 words) - 18:21, 13 May 2024
  • File:Dbl-levelXing01.jpg
    Level crossing over two tracks
    (794 × 512 (60 KB)) - 14:56, 4 June 2022
  • File:Retford low-level station.jpg
    Bridge crossing at Retford low-level () © CC-BY Rcsprinter123; Source Please, always name the creator when using this image e.g. with: {{licence|File:Retford
    (3,264 × 2,448 (2.52 MB)) - 16:04, 13 March 2024
  • crossedElement description;name;lang;xsi:type levelCrossings IS trackElements levelCrossing levelCrossing IS levelCrossings additionalName;geoCoord;states;crossedElements
    46 KB (4,606 words) - 19:18, 4 January 2023
  • </rail:speed> <rail:etcs level_0="true" level_1="true" level_2="true" level_3="true" srsVersion="" switchable="true"/> <rail:levelCrossing ref="" switchable="true"
    63 KB (5,185 words) - 19:18, 4 January 2023
  • – This combines a lockIL with a possible state. levelCrossingAndState – This combines a levelCrossingIL with a possible state. sectionAndVacancy – This
    5 KB (562 words) - 19:18, 4 January 2023
  • n IL:relatedToTrackAsset IL:requiresLevelCrossingInState IL:relatedLevelCrossingAndState IL:refersToLevelCrossing IL:requiresSwitchInPosition IL:relatedSwitchAndPosition
    77 KB (2,609 words) - 19:18, 4 January 2023
  • comment. --&gt;{{docBase |element=levelCrossings |comment= |subschema=[[IS]] |parent=[[trackElements]] |children=[[levelCrossing]] |attributes=None |obligatory=}}
    339 KB (42,145 words) - 19:18, 4 January 2023
  • either by a <crossing> in case of a simple crossing, or by a <switchIS> of type doubleSwitchCrossing or singleSwitchCrossing. <IS:underCrossing>, <IS:overCrossing>
    9 KB (3 words) - 12:19, 13 May 2024