Search results
Jump to navigation
Jump to search
- aspect it is showing. This includes also any repeaters. Subschema interlocking Parents* aspectRelation Children any (0..*), designator (0..1), refersToSignal516 bytes (15 words) - 18:52, 19 December 2019
- reference to any switch in the overlap required to be in a particular position and its position. Subschema interlocking Parents* overlap Children any (0..*)542 bytes (9 words) - 12:02, 30 May 2020
- needs just the <designator> and @id to describe a key that can be referred by any lock as suitable to operate it. In a conventional system this means a hardware964 bytes (88 words) - 19:16, 29 January 2020
- reference to any level crossing in the overlap required to be in a particular state and its state. Subschema interlocking Parents* overlap Children any (0..*)546 bytes (9 words) - 12:01, 30 May 2020
- in its purest form consists only of an entry and exit signal. If there are any switches on the route, their position is associated with the route. The interlocking9 KB (1,096 words) - 11:30, 30 May 2024
- 3.2 UML-visualization of RAILML Documentation This is the root element of any railML file. Subschema railml Parents* Children common (0..1), infrastructure513 bytes (4 words) - 18:40, 19 December 2019
- infrastructure Parents* signalIS Children any (0..*), refersToLine (0..1) Attributes: shownValue: kilometer value plus any further remark that is printed on the513 bytes (4 words) - 18:44, 19 December 2019
- }) Possible values: conflictingHeadProtection: This value is used in case any signal that shall provide flank/head protection to either route is used as520 bytes (9 words) - 18:50, 19 December 2019
- of railML® version 3.2 UML-visualization of IL Documentation reference to any derailer and its position inside or outside the work zone required for use521 bytes (9 words) - 18:49, 19 December 2019
- of railML® version 3.2 UML-visualization of IL Documentation reference to any movable crossing and its position inside or outside the work zone required521 bytes (9 words) - 18:49, 19 December 2019
- of railML® version 3.2 UML-visualization of IL Documentation reference to any key log and its state inside or outside the work zone required for use and/or517 bytes (9 words) - 18:49, 19 December 2019
- of railML® version 3.2 UML-visualization of IL Documentation reference to any signal and its aspect inside or outside the work zone required for use and/or519 bytes (9 words) - 18:49, 19 December 2019
- of railML® version 3.2 UML-visualization of IL Documentation reference to any switch and its position inside or outside the work zone required for use and/or519 bytes (9 words) - 18:48, 19 December 2019
- belongs to from operational point of view. <hasCommand> - The reference to any predefined operator command, which can be used with this element. For details3 KB (348 words) - 12:05, 28 May 2022
- outside the interlocking system., verbalConstraint: verbal formulation for any kind of further constraint that applies for using the overCrossing or underCrossing3 KB (242 words) - 11:48, 13 May 2024
- command. @requiresStopBeforeUnprotectedLevelCrossing – Flag to define whether any train needs to stop in front of the level crossing in case it is unprotected18 KB (1,997 words) - 15:11, 4 June 2022
- crossing is activated only after a given delay. This delay doesn't depend on any aspect. If there's a delay that depends on signalled speed, please use the514 bytes (9 words) - 18:48, 19 December 2019
- of railML® version 3.2 UML-visualization of IL Documentation The tuple for any switch in the track in rear of the start signal required for this route containing533 bytes (9 words) - 18:50, 19 December 2019
- endOfTrack is a functional element for use in an interlocking logic as end of any route, which represents the limit of control. It might be a physicalEnd or2 KB (276 words) - 14:50, 27 May 2022
- entityIL allows the possibility of user-defined extensions with @anyAttribute and anchors for <any>-Elements. The latter one requires a user-defined namespace4 KB (493 words) - 10:38, 31 May 2021