Search results
Jump to navigation
Jump to search
- <trainPartRef ref='tp_1.1' position='1'/> <trainPartRef ref='tp_3.1' position='2'/> <trainPartRef ref='tp_2.1' position='3'/> <trainPartRef ref='tp_4.1'12 KB (2,023 words) - 20:58, 22 January 2024
- <lineVis> ref <trackVis> ref <trackElementVis> ref <position> x, y <ocpVis> ref <position> x, y <size> height, width <objectVis> ref <position> x, y <size>112 KB (4,754 words) - 18:02, 3 April 2022
- <trainPartRef ref='tp_1.1' position='1'/> <trainPartRef ref='tp_3.1' position='2'/> <trainPartRef ref='tp_2.1' position='3'/> <trainPartRef ref='tp_4.1'24 KB (3,449 words) - 18:37, 22 January 2024
- <connection id="c12" ref="c21"/> </trackBegin> <trackEnd id="tE1"> ... </trackEnd> <connections> <switch id="s1" pos="0"> <connection id="c13" ref="c31" orientation="incoming"45 KB (5,550 words) - 18:04, 19 January 2024
- <propService passenger="true" service="true"/> <propEquipment> <trackRef ref="tr01"/> <trackRef ref="tr02"/> </propEquipment> <propOther status="operational"/>9 KB (1,420 words) - 10:23, 1 February 2024
- </xs:sequence> <xs:attributeGroup ref="rail:aOperatingCode" /> <xs:attributeGroup ref="rail:aTimePeriod" /> + <xs:attributeGroup ref="rail:anyAttribute" /> </xs:complexType>108 KB (9,484 words) - 10:56, 8 October 2021
- <xs:element ref="rail:infrastructure" minOccurs="0" /> - <xs:element ref="rail:infrastructureVisualizations" - minOccurs="0" /> - <xs:element ref="rail:rollingstock"531 KB (37,474 words) - 10:55, 8 October 2021
- sequence="1" ocpRef="A"> <sectionTT> <trackRef ref="tr3"> <trackRef ref="tr6"> <trackRef ref="tr8"> <trackRef ref="tr10"> <trackRef ref="tr9"> </sectionTT>3 KB (441 words) - 16:13, 12 September 2022
- <visualization id="vis0" infrastructureRef="inf0" version="2.4"> <lineVis ref="l1"> <trackVis ref="tr1"> <trackElementVis ref="tr1_b"> <!-- reference to the beginning10 KB (1,182 words) - 19:33, 22 January 2024
- <operationControlPoints> <ocp id="ocp01"> ... <propEquipment> <trackRef ref="tr02"/> <trackRef ref="tr03"/> </propEquipment> ... </ocp> </operationControlPoints>15 KB (1,768 words) - 18:26, 19 January 2024
- <trainPartSequence sequence="1"> <trainPartRef ref="train-part-1"/> </trainPartSequence> <replacements> <replacementOf> <operatingPeriodRef ref="operating-period-KW47-MoFr-18"3 KB (332 words) - 22:40, 25 November 2018
- TT:trainPartRef (section Position of trainPartRef in the XML-Tree / Position von trainPartRef im XML-Baum)Element <trainPartRef> wird genutzt, um einen einzelnen zum Zug gehörenden trainPart (Teilzuglauf, bzw. Zugteil) zu referenzieren. ref: This refers to the2 KB (238 words) - 23:05, 25 November 2018
- name='Dresden Hbf Wiener Strasse' parentOcpRef='ocp02'> <propEquipment> <summary hasSwitches='false' signalBox='none'/> <trackRef ref='track01'/> </propEquipment> <designator18 KB (2,618 words) - 16:53, 19 March 2024
- element, by name the values of minOccurs and maxOccurs. For example, in <ocpRef> (railML® 2) the multiplicity is depicted with [2..2], which means, that1 KB (133 words) - 07:14, 15 November 2022
- 4) (deprecated with version 2.1 and 2.5) ref: reference is required because it's the purpose of the element ref: xs:IDREF; required Not yet described. /813 bytes (125 words) - 14:19, 22 November 2022
- TT:platformEdgeRef (section Position of platformEdgeRef in the XML-Tree / Position von platformEdgeRef im XML-Baum)unterschiedlicher Höhe, kann auch mehr als eine Haltekante befahren werden. ref: This refers to the id attribute of the associated platformEdge element. xs:anyAttribute:1 KB (160 words) - 20:37, 22 January 2024
- org/wiki/IS:baliseGroupRef" /> + </xs:annotation> + </xs:element> + </xs:sequence> <xs:attributeGroup ref="rail:aSignal" /> <xs:attributeGroup ref="rail:aOcpRef" /> </xs:extension>331 KB (27,016 words) - 10:56, 8 October 2021
- name="trainGroup B" parentRef="trg_2"> <trainRef ref="..." sequence="1" /> <trainRef ref="..." sequence="2" /> <trainRef ref="..." sequence="3" /> </trainGroup>9 KB (1,534 words) - 21:00, 22 January 2024
- system WGS84, because it is valid worldwide — see https://spatialreference.org/ref/epsg/wgs-84 (external link). The semantics for the list contents of the coord12 KB (1,472 words) - 19:28, 22 January 2024
- shuntingTime <platformEdgeRef> ref <serviceSectionRef> ref <annotationRef> operatingPeriodRef, ref <organizationalUnitBinding> <vehicleOperator> ref, xsi:type <customer>65 KB (2,931 words) - 12:19, 8 October 2021
- TRACK_COURSE: straight REF_SW: cte2 SW_COURSE: right REF2: csw1 REF3: ctb1 With the "Norwegian definition" we get REF1: cte2 TRACK_COURSE: right REF_SW: cte3 SW_COURSE:5 KB (1,094 words) - 19:21, 22 January 2024
- <vehicleOperator> ref, xsi:type <customer> ref, xsi:type <railwayUndertaking> ref, xsi:type <operationalUndertaking> ref, xsi:type <concessionaire> ref, xsi:type72 KB (3,235 words) - 11:59, 11 October 2021
- G::4326"/> <speed kind="announcement" switchable="false"/> <speedChangeRef ref="sc26301"/> </signal> <signal id="ssig263013" dir="up" pos="15613" absPos="106663"15 KB (2,400 words) - 19:48, 22 January 2024
- TT:operatingPeriodRef trainPart (section Position of operatingPeriodRef in the XML-Tree / Position von operatingPeriodRef im XML-Baum)Element <operatingPeriodRef> referenziert die zum trainPart gehörige Verkehrsperiode. Please, be aware of the semantic constraint(s)! ref: This refers to the2 KB (230 words) - 12:47, 14 May 2024
- replaces <ocpVis>.(introduced with version 2.5) ref: reference is required because it's the purpose of the element ref: xs:IDREF; required please refer to <IS959 bytes (106 words) - 19:40, 22 January 2024
- TT:annotationRef connection (section Position of annotationRef in the XML-Tree / Position von annotationRef im XML-Baum)operatingPeriodRef xs:IDREF, optional ref xs:IDREF, mandatory target: xs:string; either station or train priority: xs:integer operatingPeriodRef: tGenericRef (xs:IDREF);282 bytes (244 words) - 16:01, 28 March 2022
- values). down This goes opposite to up (decreasing relative position values). ref: This refers to the id attribute of the associated <track> element. xs:anyAttribute:995 bytes (166 words) - 12:08, 8 February 2024
- TT:serviceSectionRef (section Position of serviceSectionRef in the XML-Tree / Position von serviceSectionRef im XML-Baum)Haltekanten (platformEdges) auch mehrere solche Abschnitte referenziert werden. ref: This refers to the id attribute of the associated serviceSection element1 KB (154 words) - 20:41, 22 January 2024
- IS:trainProtectionElementGroupRef (section Position of IS:trainProtectionElementGroupRef in the XML-Tree / Position von IS:trainProtectionElementGroupRef im XML-Baum)connected to the signal's aspect None ref: reference is required because it's the purpose of the element ref: tGenericRef The following example (taken from2 KB (168 words) - 14:02, 13 March 2023
- <train> <trainPartSequence> <trainPartRef ref=’TP1.1’ position=’1’> <trainPartRef ref=’TP2.1’ position=’2’> <trainPartRef ref=’TP3.1’ position=’3’> </trainPartSequence>7 KB (948 words) - 18:45, 19 January 2024
- </xs:annotation> </xs:attribute> - <xs:attributeGroup ref="rail:anyAttribute" /> + <xs:attribute ref="xml:lang" /> </xs:complexType> <xs:complexType nam398 KB (34,006 words) - 10:54, 8 October 2021
- kind="execution" trainRelation="headOfTrain" switchable="false"> <speedChangeRef ref="tr03_sc02"/> </speed> </signal> The referenced <speedChange> element is4 KB (487 words) - 17:19, 19 January 2024
- RS:speedProfileRef (section Position of speedProfileRef in the XML-Tree / Position von speedProfileRef im XML-Baum)> in another file. ref xs:IDREF, optional name xs:string, optional Not yet described. / Noch nicht beschrieben. The attributes ref and name shall be used871 bytes (107 words) - 20:25, 25 November 2018
- IS:infraAttrGroupRef (section Position of IS:infraAttrGroupRef in the XML-Tree / Position von IS:infraAttrGroupRef im XML-Baum)IS:infraAttrGroupRef Parent: <infraAttrGroupRefs> Children: None [0..∞] Sub-element for a reference to instances of <infraAttributes>. ref: reference is399 bytes (47 words) - 18:53, 25 November 2018
- once leaving it.(introduced with version 2.5) ref: Reference a <genericArea>, comp. #473 ref: tGenericRef (xs:IDREF); required Not yet described. / Noch686 bytes (109 words) - 12:35, 24 March 2022
- IS:trackRef propEquipment (section Position of trackRef in the XML-Tree / Position von trackRef im XML-Baum)<trackRef>. sequence: This allows for sorting the referenced tracks. ref: This refers to the id attribute of the associated track element. xs:anyAttribute: This316 bytes (162 words) - 19:20, 25 November 2018
- consisting of letters, digits, points (.), dashes (-) or underscores (_) ref: tGenericRef (xs:IDREF); required Must point to the id of another <connection> Please211 bytes (148 words) - 16:28, 20 July 2022
- consisting of letters, digits, points (.), dashes (-) or underscores (_) ref: tGenericRef (xs:IDREF); required Must point to the id of another <connection> Please215 bytes (148 words) - 11:12, 22 January 2013
- IS:ocpRef Parent: <path> Children: None [2..2] This refers to the id attribute of the associated <ocp> element. ref: reference is required because it's428 bytes (52 words) - 14:07, 25 October 2022
- name="singleDate" type="xs:date" /> - <xs:attributeGroup ref="rail:aTimePeriod" /> - <xs:attributeGroup ref="rail:aPeriodTimeSpan" /> + <xs:attribute name="startDate"104 KB (9,170 words) - 10:56, 8 October 2021
- than in the running text. Footnotes can be generated with <ref> tags. A documentation of <ref> tags can be found at mediawiki.org (external link). As to10 bytes (1,478 words) - 18:13, 5 March 2021
- TT:annotationRef trainPart (section Position of annotationRef in the XML-Tree / Position von annotationRef im XML-Baum)operatingPeriodRef xs:IDREF, optional ref xs:IDREF, mandatory target: xs:string; either station or train priority: xs:integer operatingPeriodRef: tGenericRef (xs:IDREF);252 bytes (234 words) - 16:04, 28 March 2022
- TT:annotationRef stopDescription (section Position of annotationRef in the XML-Tree / Position von annotationRef im XML-Baum)operatingPeriodRef xs:IDREF, optional ref xs:IDREF, mandatory target: xs:string; either station or train priority: xs:integer operatingPeriodRef: tGenericRef (xs:IDREF);264 bytes (234 words) - 16:04, 28 March 2022
- version 2.4) (deprecated with version 2.1) ref: reference is required because it's the purpose of the element ref: xs:IDREF; required please refer to <IS795 bytes (109 words) - 13:07, 10 May 2023
- referenced trains. This "counter" defines the chronological order during a day. ref: This refers to the id attribute of the associated train element. xs:anyAttribute:1 KB (146 words) - 18:13, 1 December 2021
- IS:speedChangeRef (section Position of IS:speedChangeRef in the XML-Tree / Position von IS:speedChangeRef im XML-Baum)IS:speedChangeRef Parent: <speed_signal> Children: None [0..∞] Reference to a speed change. ref: reference is required because it's the purpose of the349 bytes (44 words) - 23:28, 25 November 2018
- <xs:element name="metadata" type="dc:elementContainer" minOccurs="0" /> <xs:element ref="rail:infrastructure" minOccurs="0" /> example: <xs:attributeGroup name="aPlaces">5 KB (331 words) - 10:51, 14 November 2023
- RS:categoryRef (section Position of categoryRef in the XML-Tree / Position von categoryRef im XML-Baum)non-railML® attributes in a foreign namespace. How to use it? ref xs:IDREF, mandatory The element <categoryRef> may be used several times. Not yet described. / Noch1 KB (154 words) - 15:58, 15 November 2021
- IS:baliseGroupRef (section Position of IS:baliseGroupRef in the XML-Tree / Position von IS:baliseGroupRef im XML-Baum)IS:baliseGroupRef Parent: IS:signal Children: None [0..∞] Sub-element for a reference to a baliseGroup, which is connected to the signal's aspect ref: reference386 bytes (52 words) - 23:28, 2 July 2021
- the signal to be switchable or fixed (panel) ref: reference to a line switchable: xs:boolean ref: tGenericRef Not yet described. / Noch nicht beschrieben383 bytes (54 words) - 23:23, 25 November 2018
- IS:trainProtectionElementRef (section Position of IS:trainProtectionElementRef in the XML-Tree / Position von IS:trainProtectionElementRef im XML-Baum)<trainProtectionElementRef> addresses the trainProtectionElements belonging to the group. ref: reference is required because it's the purpose of the element ref: xs:IDREF595 bytes (66 words) - 13:29, 25 October 2022
- IS:ocpRef controller (section Position of IS:ocpRef in the XML-Tree / Position von IS:ocpRef im XML-Baum)referenced from more than one controller. ref: reference is required because it's the purpose of the element sequence: ref: xs:IDREF sequence: xs:positiveInteger509 bytes (68 words) - 10:51, 11 December 2018
- with version 2.5) {{{attributes}}} ref: Reference is required because it's the purpose of the element. ref: tGenericRef (xs:IDREF); required Not yet described133 bytes (54 words) - 10:53, 15 April 2024
- version 2.4) (deprecated with version 2.1) ref: reference is required because it's the purpose of the element ref: xs:IDREF; required Not yet described. /473 bytes (81 words) - 19:05, 13 December 2021
- TT:speedProfileRef (section Position of speedProfileRef in the XML-Tree / Position von speedProfileRef im XML-Baum)wird. Im Ausnahmefall, kann auch mehr als ein Geschwindigkeitsprofil gelten. ref: This refers to the id attribute of the associated speedProfile element. xs:anyAttribute:978 bytes (128 words) - 20:44, 22 January 2024
- IS:trackRef locallyControlledArea (section Position of trackRef in the XML-Tree / Position von trackRef im XML-Baum)referenced using <trackRef>. sequence: This allows for sorting the referenced tracks. ref: This refers to the id attribute of the associated track element. xs:anyAttribute:332 bytes (162 words) - 19:04, 25 November 2018
- IS:signalRef stopPost (section Position of signalRef in the XML-Tree / Position von signalRef im XML-Baum)sequence: This allows for sorting the referenced signals. ref: This refers to the id attribute of the associated signal element. xs:anyAttribute: This provides286 bytes (162 words) - 23:32, 25 November 2018
- IS:signalRef signalGroup (section Position of signalRef in the XML-Tree / Position von signalRef im XML-Baum)sequence: This allows for sorting the referenced signals. ref: This refers to the id attribute of the associated signal element. xs:anyAttribute: This289 bytes (162 words) - 19:40, 25 November 2018
- Bahnübergangs. ref: reference to a level crossing switchable: xs:boolean, optional type: enumeration (xs:string), optional ref: tGenericRef, optional Not2 KB (255 words) - 17:39, 1 August 2023
- version 2.4) (deprecated with version 2.1) ref: reference is required because it's the purpose of the element ref: xs:IDREF; required please refer to <IS1 KB (157 words) - 17:44, 19 January 2024
- IS:controllerRef locallyControlledArea (section Position of <controllerRef> in the XML-Tree / Position von <controllerRef> im XML-Baum)with version 2.4) sequence: ref: reference is required because it's the purpose of the element sequence: xs:positiveInteger ref: xs:IDREF Not yet described515 bytes (58 words) - 19:04, 25 November 2018
- with version 2.5) {{{attributes}}} ref: Reference is required because it's the purpose of the element. ref: tGenericRef (xs:IDREF); required Not yet described126 bytes (54 words) - 22:19, 29 November 2021
- with version 2.5) {{{attributes}}} ref: Reference is required because it's the purpose of the element. ref: tGenericRef (xs:IDREF); required Not yet described89 bytes (50 words) - 22:57, 29 November 2021
- with version 2.5) {{{attributes}}} ref: Reference is required because it's the purpose of the element. ref: tGenericRef (xs:IDREF); required Not yet described141 bytes (55 words) - 22:13, 29 November 2021
- TT:blockPartRef (section Position of blockPartRef in the XML-Tree / Position von blockPartRef im XML-Baum)dem Element <blockPartRef> werden blockParts referenziert, um sie als Einzelaufgaben zu einem "Dienst" zu gruppieren. ref: This refers to the id attribute626 bytes (85 words) - 22:05, 25 November 2018
- IS:controllerRef ocp (section Position of <controllerRef> in the XML-Tree / Position von <controllerRef> im XML-Baum)means master controller. ref: reference is required because it's the purpose of the element sequence: xs:positiveInteger ref: xs:IDREF Not yet described516 bytes (68 words) - 12:51, 3 February 2023
- sequence="1"> <trainPartRef ref="tp2_1"/> </trainPartSequence> <!-- From Bf_C to Bf_D --> <trainPartSequence sequence="2"> <trainPartRef ref="tp2_2" position="1"/>8 KB (1,098 words) - 18:21, 19 January 2024
- sequence: This allows for sorting the referenced balises. ref: This refers to the id attribute of the associated balise element. sequence xs:positiveInteger1 KB (144 words) - 23:12, 25 November 2018
- same constraint should be deployed for the tracks in the opposite direction. ref: This refers to the id attribute of the associated track element. xs:anyAttribute:585 bytes (208 words) - 08:14, 31 May 2023
- TT:operatingPeriodRef replacementOf (section Position of <operatingPeriodRef> in the XML-Tree / Position von <operatingPeriodRef> im XML-Baum)(introduced with version 2.4) Spezifiziert die Betriebstage eines Ersatzes ref: This refers to the id attribute of the associated <operatingPeriod> element978 bytes (162 words) - 14:11, 10 August 2020
- from the area to an element bounding this area.(introduced with version 2.5) ref: Reference is required because it's the purpose of the element. xs:anyAttribute:559 bytes (89 words) - 14:05, 25 October 2022
- <trackRef ref="tr01"/> <trackRef ref="tr02"/> <trackRef ref="tr03"/> <trackRef ref="tr04"/> <trackRef ref="tr05"/> <trackRef ref="tr06"/> <trackRef ref="tr07"/>20 KB (1,833 words) - 15:44, 10 October 2023
- consisting of letters, digits, points (.), dashes (-) or underscores (_) ref: tGenericRef (xs:IDREF); required Must point to the id of another <connection> orientation:2 KB (699 words) - 19:20, 22 January 2024
- <trackRef ref="yardTrack01" sequence="1"/> <trackRef ref="segmentTrack01" sequence="2"/> <trackRef ref="yardTrack04" sequence="3"/> <trackRef ref="yardTrack05"7 KB (470 words) - 14:51, 25 September 2023
- <operatingPeriodRef ref='opp_1'/> <ocpsTT> <ocpTT ocpRef='ocp_DNKW_A' ocpType='pass'> <times scope='scheduled' departure='23:55:35'/> </ocpTT> <ocpTT ocpRef='ocp_DNKO'19 KB (2,347 words) - 18:40, 19 January 2024
- <ocpTT ocpRef="_OAR" trackRef="_tr"> <times scope="scheduled" arrival="10:59:00" departure="11:04:00"/> <stopDescription> <platformEdgeRef ref="_pe" />12 KB (1,414 words) - 18:28, 19 January 2024
- sequence="1"> <!-- Berlin to Hannover --> <trainPartRef position="1" ref="CNL_242_1"/> <trainPartRef position="2" ref="CNL_1242_1"/> </trainPartSequence> <trainPartSequence7 KB (964 words) - 21:04, 22 January 2024
- IS:trackRef trackLocation (section Position of IS:trackRef trackLocation in the XML-Tree / Position von IS:trackRef trackLocation im XML-Baum)referenced using <trackRef>.(introduced with version 2.5) sequence: This allows for sorting the referenced tracks. ref: This refers to the id attribute of the113 bytes (168 words) - 11:48, 24 October 2022
- <xs:field xpath="@id" /> </xs:key> Keyrefs have to be defined for all ref and *Ref attributes. They should all refer to a certain element's id attribute9 KB (1,033 words) - 17:59, 19 January 2024
- TT:announcementRef connection (section Position of announcementRef in the XML-Tree / Position von announcementRef im XML-Baum)is determined by the priority (highest priority first). ref xs:IDREF, mandatory operatingPeriodRef xs:IDREF, optional target: xs:string; either station or2 KB (306 words) - 16:41, 24 February 2022
- TT:announcementRef trainPart (section Position of announcementRef in the XML-Tree / Position von announcementRef im XML-Baum)is determined by the priority (highest priority first). ref xs:IDREF, mandatory operatingPeriodRef xs:IDREF, optional target: xs:string; either station or2 KB (286 words) - 16:26, 24 February 2022
- of xs:string, tOtherEnumerationValue); arrival/departure); optional ref: tGenericRef (xs:IDREF); required Not yet described. / Noch nicht beschrieben. Not187 bytes (59 words) - 19:42, 3 April 2022
- revision. (introduced with version 2.5) ref: This refers to the id attribute of the associated element. ref: tGenericRef (xs:IDREF); required Not yet described277 bytes (54 words) - 17:36, 3 April 2022
- ref: Reference is required because it's the purpose of the element. ref: xs:IDREF, required Not yet described. / Noch nicht beschrieben. Not yet described361 bytes (52 words) - 15:48, 8 October 2021
- TT:patternTrainPartRef (section Position of patternTrainPartRef in the XML-Tree / Position von patternTrainPartRef im XML-Baum)(introduced with version 2.5) ref: reference is required because it's the purpose of the element position: ref: tGenericRef (xs:IDREF); required position:693 bytes (82 words) - 17:45, 12 September 2022
- IS:trackSectionRef (section Position of IS:trackSectionRef in the XML-Tree / Position von IS:trackSectionRef im XML-Baum)track sections included in the <releaseGroup>.(introduced with version 2.5) ref The reference to the track section within this group. flankProtection Set600 bytes (86 words) - 10:23, 28 March 2023
- 2022-12-15 2022-12-15 If the trainPartRef attribute is given, then there must also be a trainRef attribute, and the trainPartRef attribute must point to a train10 bytes (579 words) - 15:58, 18 May 2020
- re-used across the sub-schemas, e.g. "geoCoord", "valueTable", "efficiency", "*Ref". This section does not cover these re-used elements. See next section. If15 KB (1,952 words) - 18:11, 15 April 2024
- point for non-railML® attributes in a foreign namespace. How to use it? ref: tGenericRef (xs:IDREF); required hasKeyByDefault: xs:boolean; optional any: xs:any;481 bytes (80 words) - 15:28, 23 May 2022
- this train part. However, it is possible to follow the attribute <trainPartRef>.ref from any train to find out which one (or more) refers to the current train12 KB (1,930 words) - 15:44, 13 May 2024
- id="tr01_te"> <connection ref="tr03_c03" id="tr01_c01"/> </trackEnd> <crossSections> <crossSection id="tr01_cs01" name="Gleis 1" xml:lang="de" ocpRef="ocp01" pos="3002 KB (159 words) - 14:55, 10 October 2023
- id="tr01_te"> <connection ref="tr03_c03" id="tr01_c01"/> </trackEnd> <crossSections> <crossSection id="tr01_cs01" name="Gleis 1" xml:lang="de" ocpRef="ocp01" pos="3002 KB (159 words) - 14:33, 10 October 2023
- TT:announcementRef stopDescription (section Position of announcementRef in the XML-Tree / Position von announcementRef im XML-Baum)is determined by the priority (highest priority first). ref xs:IDREF, mandatory operatingPeriodRef xs:IDREF, optional target: xs:string; either station or2 KB (286 words) - 16:35, 24 February 2022
- id="tr01_te"> <connection ref="tr03_c03" id="tr01_c01"/> </trackEnd> <crossSections> <crossSection id="tr01_cs01" name="Gleis 1" xml:lang="de" ocpRef="ocp01" pos="3002 KB (170 words) - 14:54, 25 September 2023
- id="tr01_te"> <connection ref="tr03_c03" id="tr01_c01"/> </trackEnd> <crossSections> <crossSection id="tr01_cs01" name="Gleis 1" xml:lang="de" ocpRef="ocp01" pos="3002 KB (175 words) - 14:32, 10 October 2023
- sequence="1"> <trainPartRef ref="trainPart1001"/> </trainPartSequence> <replacements> <replacementOf> <operatingPeriodRef ref="operating-period-KW47-MoFr-18"23 KB (104 words) - 11:10, 3 May 2022
- categoryRef="cat_11"> <!-- empty run to stable --> <trainPartRef ref="tp_3" position="1"/> </trainPartSequence> </train> The attribute categoryRef at <train>15 KB (1,905 words) - 11:46, 23 March 2023
- code="5600" infrastructureManagerRef="ima01" name="Bahnstrecke München Ost Pbf – Simbach (Inn) (DB-Grenze)"> <trackRef ref="tr01"/> </line> <line id="lin02"6 KB (516 words) - 11:57, 26 April 2024
- wird genutzt um einen <railwayUndertaking> der <metadata> zu referenzieren. ref: This refers to the id attribute of the associated railwayUndertaking element759 bytes (82 words) - 13:28, 10 August 2020
- element allows for referencing a <railwayUndertaking> within the <metadata>. ref: This refers to the id attribute of the associated customer element. xs:anyAttribute:589 bytes (69 words) - 09:56, 11 May 2023
- 1] This element allows for referencing a <customer> within the <metadata>. ref: This refers to the id attribute of the associated customer element. xs:anyAttribute:569 bytes (69 words) - 09:55, 11 May 2023
- allows for referencing an <operationalUndertaking> within the <metadata>. ref: This refers to the id attribute of the associated customer element. xs:anyAttribute:598 bytes (69 words) - 09:57, 11 May 2023
- element allows for referencing a <concessionaire> within the <metadata>. ref: This refers to the id attribute of the associated customer element. xs:anyAttribute:581 bytes (69 words) - 09:58, 11 May 2023
- element allows for referencing a <vehicleOperator> within the <metadata>. ref: This refers to the id attribute of the associated vehicleOperator element534 bytes (69 words) - 09:53, 11 May 2023
- This element allows for referencing a <contractor> within the <metadata>. ref: This refers to the id attribute of the associated customer element. xs:anyAttribute:573 bytes (69 words) - 09:59, 11 May 2023
- <customer> wird genutzt um einen <customer> der <metadata> zu referenzieren. ref: This refers to the id attribute of the associated customer element. xs:anyAttribute:699 bytes (82 words) - 13:28, 10 August 2020
- genutzt um einen <operationalUndertaking> der <metadata> zu referenzieren. ref: This refers to the id attribute of the associated operationalUndertaking783 bytes (82 words) - 13:29, 10 August 2020
- <concessionaire> wird genutzt um einen <concessionaire> der <metadata> zu referenzieren. ref: This refers to the id attribute of the associated concessionaire element735 bytes (82 words) - 13:29, 10 August 2020
- wird genutzt um einen <vehicleOperator> der <metadata> zu referenzieren. ref: This refers to the id attribute of the associated vehicleOperator element741 bytes (82 words) - 13:28, 10 August 2020
- <contractor> wird genutzt um einen <contractor> der <metadata> zu referenzieren. ref: This refers to the id attribute of the associated contractor element. xs:anyAttribute:711 bytes (82 words) - 13:29, 10 August 2020
- use it? <trainPart id="..." > <operatingPeriodRef ref="op_Daily" /> <ocpsTT> ... <ocpTT sequence="23" ocpRef="ocp_FF" ocpType="stop"> <times scope="scheduled"2 KB (210 words) - 17:16, 3 July 2023
- IS:trackRef line trackGroups (section Position of IS:trackRef line trackGroups in the XML-Tree / Position von IS:trackRef line trackGroups im XML-Baum)<trackRef>. sequence: This allows for sorting the referenced tracks. ref: This refers to the id attribute of the associated track element. xs:anyAttribute: This105 bytes (164 words) - 11:48, 24 October 2022
- mechanism. How to use it? rollingstockRef: This refers to the id attribute of the associated <rollingstock> element. timetableRef: This refers to the id attribute2 KB (574 words) - 17:47, 25 March 2024
- How to use it? infrastructureRef: This refers to the id attribute of the associated infrastructure element. rollingstockRef: This refers to the id attribute2 KB (574 words) - 13:22, 6 October 2022
- railML® enumeration lists, optional ocpRef: xs:IDREF, optional trainPartRef: xs:IDREF, optional operatingPeriodRef: xs:IDREF, optional notGuaranteed: xs:boolean25 KB (3,398 words) - 20:30, 22 January 2024
- categoryPriority: xs:string; optional parentRef: tGenericRef (xs:IDREF); optional organizationalUnitRef: tGenericRef (xs:IDREF); optional Even if the data type12 KB (1,737 words) - 11:19, 18 March 2024
- version 2.2) startOcpRef: tGenericRef (xs:IDREF); optional endOcpRef: tGenericRef (xs:IDREF); optional trainPartRef: tGenericRef (xs:IDREF); optional operatingPeriodRef:12 KB (1,612 words) - 12:52, 14 May 2024
- is referenced: from <ocpTT>.ocpRef to <ocp>.id (mandatory) Rolling stock is referenced: from <formationTT>.formationRef to <formation>.id (optional) from10 bytes (677 words) - 16:12, 3 February 2020
- Element <operatingPeriodRef>, child of <trainPart> Element <operatingPeriodRef>, child of <replacementOf>112 bytes (10 words) - 14:05, 29 January 2018
- node. <trackBegin id="tB35113" pos="0" absPos="-110"> <macroscopicNode ocpRef="ocpFBGK"/> </trackBegin> Consider the railML® 2.2 example of East Saxony3 KB (483 words) - 10:48, 15 April 2024
- timetableRef: This refers to the id attribute of the associated <timetable> element. This is the reference to a timetable data set. infrastructureRef: This1 KB (584 words) - 12:11, 24 January 2022
- <trackEnd id="tE26301" pos="61366" absPos="152415"> <macroscopicNode ocpRef="ocpFBGK"/> </trackEnd> Consider the railML® 2.2 example of East Saxony railway4 KB (545 words) - 18:10, 22 March 2024
- referenced from <ocpTT>.ocpRef to <ocp>.id (mandatory), from <sectionTT>.lineRef to <line>.id (optional), from <sectionTT>.<trackRef>.ref to <track>.id (optional)10 bytes (1,903 words) - 16:12, 3 February 2020
- TT:startTime (redirect from TT:startTime activationTime annotationRef)<startTime> Parent: <periodic>, <activationTime> Children: <eventTrigger>, <ocpTrigger>, <timingTrigger>, <geoTrigger>, <informationAreaTrigger> [1.412 bytes (52 words) - 16:55, 28 March 2022
- TT:endTime (redirect from TT:endTime activationTime annotationRef)<endTime> Parent: <periodic>, <activationTime> Children: <eventTrigger>, <ocpTrigger>, <timingTrigger>, <geoTrigger>, <informationAreaTrigger> [1..1]408 bytes (52 words) - 16:55, 28 March 2022
- "120000-08012017" is referenced. <trainPartSequence sequence="1"> <trainPartRef ref="train-part-1" /> <topologyReference register="UNO" entry="183000-01012017"7 KB (829 words) - 20:52, 22 January 2024
- Children: <additionalName> (introduced with version 2.1), <any>, <states>, <ocpRef> (introduced with version 2.4), <trackVacancyDetectionArea> (introduced with2 KB (607 words) - 20:11, 13 December 2021
- entering entering the area leaving leaving the area informationAreaRef: tGenericRef (xs:IDREF); required event: tInformationAreaEvent (union of (restriction699 bytes (102 words) - 10:05, 11 May 2023
- Element <announcementRef>, child of <stopDescription> Element <announcementRef>, child of <trainPart> Element <announcementRef>, child of <connection>152 bytes (15 words) - 15:06, 24 February 2022
- from abandoned Vienna South Station to Hegyeshalom" xml:lang="en"/> <trackRef ref="tr01"/> </line> </trackGroups> ... Please note, that the line element only12 KB (1,794 words) - 19:36, 22 January 2024
- <additionalName> to provide a name and/or description in other languages. timetablePeriodRef: This refers to the id attribute of the associated <timetablePeriod> element3 KB (711 words) - 12:48, 14 May 2024
- TT:ocpTrigger (redirect from TT:ocpTrigger trigger announcementRef)which when reached triggers the announcement.(introduced with version 2.5) ocpRef: allows to specify an ocp which when reached triggers the announcement. offset:558 bytes (86 words) - 19:16, 13 December 2021
- TT:timingTrigger (redirect from TT:timingTrigger trigger announcementRef)<timingTrigger> Parent: <trigger>, <startTime>, <endTime> Children: None [1..1] allows to specify a specific time for the announcement.(introduced with363 bytes (54 words) - 19:17, 13 December 2021
- TT:eventTrigger (redirect from TT:eventTrigger trigger announcementRef)<eventTrigger> Parent: <trigger>, <startTime>, <endTime> Children: None [1..1] Allows to specify that the referenced announcement is to be played delayed931 bytes (121 words) - 17:25, 8 August 2022
- TT:geoTrigger (redirect from TT:geoTrigger trigger announcementRef)<geoTrigger> Parent: <trigger>, <startTime>, <endTime> Children: <geoCoord> [1..1] allows to specify geocoordinates which when reached trigger the announcement442 bytes (69 words) - 19:17, 13 December 2021
- millimeter side: Restriction of xs:string (enumeration) ocpRef: xs:IDREF parentPlatformEdgeRef: xs:IDREF Consider railML® 2.3 example of Middle Rhine Railway3 KB (916 words) - 18:22, 22 March 2023
- xs:string; optional platformEdgeRef: tGenericRef (xs:IDREF); optional virtual: xs:boolean; optional ocpRef: tGenericRef (xs:IDREF); optional Not yet described5 KB (1,258 words) - 17:26, 19 January 2024
- 6212_1' pos='700' absPos='101400' ocpRef='ocp_DN_G'/> <crossSection id='trn_DN_E_80.6212_1' pos='1110' absPos='100990' ocpRef='ocp_DN_E'/> <crossSection id='trn_DOLB_808 KB (1,542 words) - 10:55, 21 February 2024
- regions". ocpStationRef: This refers to the id attribute of the associated <ocp> element. (introduced with version 2.1) controllerRef: This refers to the2 KB (1,151 words) - 16:06, 6 November 2022
- xs:string; optional etcsTrainCategory: xs:integer; optional profileRef: tGenericRef (xs:IDREF); optional status: xs:string; optional vMax: tSpeedKmPerHour10 KB (1,890 words) - 15:25, 25 March 2024
- xml:lang: xs:language, language identification, optional vehicleRef: xs:IDREF, optional formationRef: xs:IDREF, optional depot: xs:string, optional defaultPreProcessingTime:7 KB (1,167 words) - 20:40, 22 January 2024
- 34" profileRef="sp1" vMax="90"/> <speedChange id="sc2" pos="12.34" profileRef="sp4" vMax="105"/> <speedChange id="sc3" pos="13.45" profileRef="sp3" vMax="40"/>4 KB (819 words) - 10:31, 28 March 2023
- whitespace is not allowed. Please, apply Dev:usingAny accordingly. ocpRef: tGenericRef (xs:IDREF); required flowDirection: tFlowDirection (union of (restriction4 KB (440 words) - 19:38, 22 January 2024
- sectionTT Parent: <ocpTT> Children: <trackRef>, <runTimes>, <xs:any> (introduced with version 2.3) [0..1] The element sectionTT describes data concerning3 KB (289 words) - 11:18, 4 July 2022
- lineTTRef: tGenericRef (xs:IDREF); optional remarks: xs:string; optional timeTablePeriodRef: tGenericRef (xs:IDREF); optional categoryRef: tGenericRef (xs:IDREF);2 KB (516 words) - 11:31, 9 October 2023
- attributes nextBlockRef and nextOperatingperiodRef the blocks are connected to a chain and form a rostering. A circulation without nextBlockRef models a block5 KB (632 words) - 12:51, 14 May 2024
- IS:infraAttrGroupRefs (section Position of IS:infraAttrGroupRefs in the XML-Tree / Position von IS:infraAttrGroupRefs im XML-Baum)IS:infraAttrGroupRefs Parent: <track> Children: <infraAttrGroupRef> [0..1] Container element for infraAttrGroupRef of properties of an infrastructure293 bytes (37 words) - 15:23, 24 October 2022
- RS:vehicleRef (section Position of vehicleRef in the XML-Tree / Position von vehicleRef im XML-Baum)vehicleRef Parent: <trainOrder> Children: Not yet described. / Noch nicht beschrieben. [1..∞] The element <vehicleRef> contains the data about the positions2 KB (287 words) - 21:24, 25 November 2018
- regions". ocpStationRef: This refers to the id attribute of the associated <ocp> element. (introduced with version 2.1) controllerRef: This refers to the2 KB (1,116 words) - 10:12, 28 June 2023
- vehicleManufacturerRef='vm_3' manufacturer-Type='ME26'/> <operator vehicleOperatorRef='vop_1' operatorClass='Di6'/> <operator vehicleOperatorRef='vop_2' operatorClass='251'/>1 KB (146 words) - 18:24, 3 April 2022
- <additionalName> to provide a name and/or description in other languages. vehicleFamilyRef: This refers to the id attribute of the associated <vehicle> element. The10 KB (1,797 words) - 13:09, 24 January 2022
- language identification, optional ocpStationRef xs:IDREF, optional controllerRef xs:IDREF, optional ocpRef: xs:IDREF, optional Not yet described. / Noch2 KB (538 words) - 17:26, 15 February 2021
- specialService Parent: <operatingPeriodRef> Children: None [1..1] (deprecated with version 2.2) — use reference to individual operating period instead2 KB (288 words) - 08:52, 29 November 2022
- vehicleManufacturerRef='vm_3' manufacturer-Type='ME26'/> <operator vehicleOperatorRef='vop_1' operatorClass='Di6'/> <operator vehicleOperatorRef='vop_2' operatorClass='251'/>3 KB (336 words) - 13:37, 14 May 2024
- platform information can and should be identified via the trackRef attribute. trackRef: xs:IDREF trackInfo: xs:string Up to version 2.5 of railML® it was5 KB (677 words) - 19:26, 7 December 2021
- <outputLanguages> Parent: <announcementRef>, <annotationRef> (introduced with version 2.5) Children: <outputLanguage> [0..1] Container for a list output404 bytes (59 words) - 12:34, 14 February 2022
- description="speed profile for trains on a certain path"> <path> <ocpRef ref="ocp01"/> <ocpRef ref="ocp01"/> </path> </speedProfile>36 KB (103 words) - 13:54, 21 February 2022
- Children: <additionalName> (introduced with version 2.1), <trainOrder>, <categoryRef>, <trainEngine>, <trainBrakes>, <technicalStopActivity> (introduced with version4 KB (1,072 words) - 19:36, 13 December 2021
- the whole route (from signal to signal). entryRef reference to the signal where the route starts. exitRef reference to the signal where the route ends.4 KB (1,036 words) - 11:47, 3 November 2023
- xs:duration; optional postProcessingTime: xs:duration; optional basicBlockRef: tGenericRef (xs:IDREF); optional Not yet described. / Noch nicht beschrieben. Not2 KB (231 words) - 22:04, 25 November 2018
- use it? <trainPart id="..." > <operatingPeriodRef ref="op_Daily" /> <ocpsTT> ... <ocpTT sequence="23" ocpRef="ocp_FF" ocpType="stop"> <times scope="scheduled"3 KB (319 words) - 18:20, 24 September 2023
- System (external link)). Please use infrastructureManagerRef instead. infrastructureManagerRef (introduced with version 2.2): reference to the infrastructure2 KB (715 words) - 15:33, 25 March 2024
- is restricted to a certain direction, but this direction is not known. ocpRef: reference to the OCP, where the platform edge / service section belongs to4 KB (1,103 words) - 16:56, 13 March 2022
- Element <annotationRef>, child of <stopDescription> Element <annotationRef>, child of <trainPart> Element <annotationRef>, child of <connection>146 bytes (15 words) - 11:54, 14 June 2017
- <crossSections> <crossSection id="cs3510216" pos="1" type="station" absPos="30523" ocpRef="ocpFMZ"> <geoCoord coord="50.001659 8.258180" epsgCode="urn:ogc:def:crs:EPSG::4326"/>5 KB (1,077 words) - 14:57, 14 March 2024
- version 2.2), use infrastructureManagerRef instead to refer to a listed infrastructureManager uic-no infrastructureManagerRef (introduced with version 2.2) reference809 bytes (83 words) - 18:44, 25 November 2018
- not known. ocpStationRef: This refers to the id attribute of the associated <ocp> element. (introduced with version 2.1) controllerRef: This refers to the4 KB (997 words) - 17:41, 1 August 2023
- beschreibt wie eine formation im Rahmen eines trainPart verwendet wird. formationRef: This refers to the id attribute of the associated formation element. weight:3 KB (356 words) - 17:36, 8 August 2022
- fixed (panel) trackConditionRef: reference to a trackCondition element switchable: xs:boolean trackConditionRef: tGenericRef Not yet described. / Noch nicht430 bytes (54 words) - 23:24, 2 July 2021
- xml:lang: xs:language, language identification, optional initialProjectRef: tGenericRef (xs:IDREF); optional Not yet described. / Noch nicht beschrieben. Not662 bytes (449 words) - 16:58, 3 April 2022
- optional xml:lang: xs:language, language identification, optional areaRef: tGenericRef (xs:IDREF); required Not yet described. / Noch nicht beschrieben. Not514 bytes (401 words) - 21:28, 29 November 2021
- <platformEdgeRef> (introduced with version 2.2), <serviceSectionRef> (introduced with version 2.2), <trackInfo> (introduced with version 2.4),<annotationRef> (introduced11 KB (1,367 words) - 17:56, 24 September 2023
- beginDay end endDay startOcpRef endOcpRef trainPartRef operatingPeriodRef mission fixed runLength vehicleRef formationRef TT:blockPartSequence sequence5 KB (31 words) - 18:14, 22 May 2023
- insulatedRail: ocpStationRef: This refers to the id attribute of the associated <ocp> element. (introduced with version 2.1) controllerRef: This refers to the1,017 bytes (705 words) - 18:51, 16 April 2023
- … > <trainOrder> <vehicleRef orderNumber='1' vehicleRef='veh_ME26' vehicleCount='1'/> <vehicleRef orderNumber='2' vehicleRef='veh_ DABpza785.2' vehicleCount='4'/>4 KB (1,006 words) - 20:23, 25 November 2018
- whitespace is not allowed. Please, apply Dev:usingAny accordingly. operatingPeriodRef: The start date (or start dates if its a periodic state) should be defined5 KB (753 words) - 13:45, 14 May 2024
- vehicleManufacturerRef='vm_3' manufacturer-Type='ME26'/> <operator vehicleOperatorRef='vop_1' operatorClass='Di6'/> <operator vehicleOperatorRef='vop_2' operatorClass='251'/>2 KB (222 words) - 06:54, 26 November 2020
- milepost, e.g. for documenting a mileage gap mileageChangeRef: reference to a mileageChange element lineRef: reference to a line, for which the milepost is valid1 KB (137 words) - 13:34, 8 January 2021
- allowed for extending railML® enumeration lists; mandatory operatingPeriodRef: tGenericRef (xs:IDREF); optional endDayOffset: xs:nonNegativeInteger; optional3 KB (354 words) - 10:27, 21 March 2023
- IS:trackRef line IS:trackRef line trackGroups IS:trackRef locallyControlledArea IS:trackRef propEquipment IS:trackRef trackLocation16 bytes (11 words) - 11:27, 24 October 2022
- aware of the semantic constraint(s)! ocpRef: This refers to the id attribute of the associated ocp element. trackRef: This refers to the id attribute of the5 KB (633 words) - 11:47, 9 October 2023
- optional, commercial="false" should be set operatingPeriodRef: xs:IDREF, optional stopPostRef: xs:IDREF, optional Not yet described. / Noch nicht beschrieben7 KB (917 words) - 18:11, 24 September 2023
- fixed (panel) trackConditionRef: reference to a trackCondition element switchable: xs:boolean trackConditionRef: tGenericRef Not yet described. / Noch nicht442 bytes (56 words) - 23:22, 25 November 2018
- aware of the semantic constraint(s)! ocpRef: This refers to the id attribute of the associated ocp element. trackRef: This refers to the id attribute of the12 KB (1,526 words) - 18:09, 7 March 2024
- <macroscopicNode ocpRef='ocp_BHW'/> </trackBegin> <trackEnd id='trn_BXH_80.6207.1_1' pos='60856' absPos='13424'> <macroscopicNode ocpRef='ocp_BXH'/> </trackEnd>3 KB (806 words) - 15:34, 25 March 2024
- operated area).(introduced with version 2.5) ocpRef: allows to refer to a known ocp as origin or destination ocpRef: xs:IDREF Not yet described. / Noch nicht487 bytes (73 words) - 19:23, 9 February 2022
- the operated area)(introduced with version 2.5) ocpRef: allows to refer to a known ocp as origin ocpRef: xs:IDREF Not yet described. / Noch nicht beschrieben462 bytes (71 words) - 19:22, 9 February 2022
- constraint. endDate: Please, recognize the semantic constraint. vehicleOwnerRef: tGenericRef (xs:IDREF); optional ownerClass: xs:string; required startDate: xs:date;636 bytes (79 words) - 13:38, 14 May 2024
- operatingPeriodRef="opp_0"> <!-- Die Sperrung verläuft nicht über Mitternacht, daher ist endDayOffset=0 --> <from ocpRef="_ocpStart" pos="0" /> <to ocpRef="_ocpEnd"14 KB (1,546 words) - 20:09, 12 April 2024
- language identification, optional remarks: xs:string; optional distributionRef: tGenericRef (xs:IDREF); optional Not yet described. / Noch nicht beschrieben. Not987 bytes (510 words) - 16:38, 12 September 2022
- propEquipment Parent: <ocp> Children: <summary>, <trackRef> [0..1] propEquipment is a container which encapsulates two variantes to define the (technical)637 bytes (81 words) - 19:07, 25 November 2018
- fixed (panel) trackConditionRef: reference to a trackCondition element switchable: xs:boolean trackConditionRef: tGenericRef Not yet described. / Noch nicht433 bytes (55 words) - 23:24, 25 November 2018
- with two tongues, one on each rail. model: specification of the derailer lockRef (introduced with version 2.5): The reference to the lock controlling this2 KB (899 words) - 14:30, 28 November 2022
- use the 'version' attribute in the root element (<railml>) infrastructureRef: This refers to the id attribute of the associated infrastructure element2 KB (279 words) - 17:50, 19 January 2024
- not known. ocpStationRef: This refers to the id attribute of the associated <ocp> element. (introduced with version 2.1) controllerRef: This refers to the7 KB (1,535 words) - 18:44, 11 April 2024
- network. Recommendation: Employ <genericAreas>><genericArea>><limitedBy>@ref to reference any infrastructure-elements that limit the respective <genericArea>29 KB (97 words) - 19:00, 22 January 2024
- Element <signalRef>, child of <signalGroup> Element <signalRef>, child of <stopPost>91 bytes (10 words) - 17:43, 13 January 2017
- sequence: tPositiveCounter (xs:positiveInteger); required categoryRef: tGenericRef (xs:IDREF); optional Not yet described. / Noch nicht beschrieben. Not2 KB (271 words) - 17:28, 12 September 2022
- ERA_ERTMS_040001 "Assignment of values to ETCS variables" v1.9 from 10/07/12 profileRef: (introduced with version 2.2) reference to a speedProfile status: vMax: the1 KB (194 words) - 14:23, 5 April 2023
- whitespace is not allowed. Please, apply Dev:usingAny accordingly. operatingPeriodRef: The start date (or start dates if its a periodic state) should be defined5 KB (637 words) - 13:47, 14 May 2024
- <trainProtectionElements> Children: <additionalName>, <any>, <trainProtectionElementRef> [1..1] The elements allow for grouping <trainProtectionElement> instances:811 bytes (370 words) - 18:58, 16 April 2023
- <trigger> Parent: <announcementRef> Children: <eventTrigger>, <ocpTrigger>, <timingTrigger>, <geoTrigger>, <manualTrigger> (introduced with version 21 KB (170 words) - 18:42, 3 April 2022
- IS:path Parent: <speedProfile> Children: <ocpRef> (mandatory) [0..1] The path element indicates a train run between two neighbouring OCPs. None None279 bytes (39 words) - 16:18, 11 January 2019
- reference, if the same vehicle is "used several times" inside a formation. vehicleRef: This refers to the id attribute of the associated <vehicle> element. xs:1 KB (124 words) - 17:02, 3 February 2022
- Starting point where the 'state' takes place, e.g. kilometric position. ocpRef: location described by the reference to a well-known 'operation or control840 bytes (130 words) - 17:35, 19 January 2024
- whitespace is not allowed. Please, apply Dev:usingAny accordingly. operatingPeriodRef: The start date (or start dates if its a periodic state) should be defined4 KB (588 words) - 13:41, 14 May 2024
- activationTime Parent: <annotationRef> Children: <startTime>, <endTime> [1..1] With the element <activationTime> it is possible to specify the time when947 bytes (150 words) - 14:55, 17 February 2022
- <periodic> Parent: <announcementRef> Children: <startTime>, <endTime> [1..1] specifies the interval, in which the announcement is repeated between <startTime>315 bytes (46 words) - 19:40, 24 February 2022
- Starting point where the 'state' takes place, e.g. kilometric position. ocpRef: location described by the reference to a well-known 'operation or control842 bytes (130 words) - 19:27, 22 January 2024
- referenced from <ocpTT>.ocpRef to <ocp>.id (mandatory), from <sectionTT>.lineRef to <line>.id (optional), from <sectionTT>.<trackRef>.ref to <track>.id (optional)16 KB (2,372 words) - 16:07, 12 November 2021
- (segment). ocp: name the neighbouring <ocp> line: tGenericRef (xs:IDREF); required ocp: tGenericRef (xs:IDREF); required Not yet described. / Noch nicht beschrieben322 bytes (54 words) - 18:30, 13 December 2021
- trainOrder Parent: formation Children: vehicleRef [0..1] The element <trainOrder> is a container for the data about the positions and the number of particular482 bytes (80 words) - 20:20, 25 November 2018
- (segment). ocp: name the neighbouring <ocp> line: tGenericRef (xs:IDREF); required ocp: tGenericRef (xs:IDREF); required Not yet described. / Noch nicht beschrieben322 bytes (54 words) - 13:50, 3 December 2021
- Identifikation, unter der es von der Zentrale angesprochen werden kann. nationalSystemRef: This refers to the id attribute of the associated <nationalSystem> element2 KB (624 words) - 20:19, 25 November 2018
- example one not directly accessible from available input devices. [66] CharRef ::= '&#' [0-9]+ ';' | '&#x' [0-9a-fA-F]+ ';' ... If the character reference2 KB (258 words) - 18:45, 22 January 2024
- <train id='…' type='operational'> <trainPartSequence sequence='1'> <trainPartRef … > <brakeUsage brakeType='compressedAir' airBrakeApplicationPosition='R'6 KB (1,198 words) - 10:17, 31 August 2021
- baliseGroup Parent: <balises> Children: <additionalName>, <any>, <baliseRef> [0..∞] A <baliseGroup> represents a group of balises. id: XML-file-wide unique1 KB (535 words) - 15:26, 22 May 2023
- the main rule.(introduced with version 2.5) ruleRef: Reference to an <operatingRule> element. ruleRef: xs:IDREF, required Not yet described. / Noch nicht376 bytes (51 words) - 15:41, 8 October 2021
- <signalGroups> Children: <additionalName> (introduced with version 2.1), <any>, <signalRef> [0..∞] A <signalGroup> groups various signals together. id: XML-file-wide812 bytes (446 words) - 16:35, 6 November 2022
- id="tr01_tb"> <macroscopicNode ocpRef="ocp01"/> </trackBegin> <trackEnd pos="500" id="tr01_te"> <macroscopicNode ocpRef="ocp02"/> </trackEnd> </trackTopology>3 KB (276 words) - 14:45, 26 September 2023
- have to be included and declared as such.(introduced with version 2.5) switchRef The reference to the switch used by the route within its path or for the flank1 KB (198 words) - 19:07, 18 November 2021
- switches within the path and their position.(introduced with version 2.5) switchRef The reference to the switch used by the overlap within its path. switchPosition861 bytes (141 words) - 19:11, 18 November 2021
- the referencing of <infrastructure> elements via the trackRef attribute or the <platformEdgeRef> element of the parent <ocpTT>. Dieses Element ermöglicht2 KB (234 words) - 18:19, 24 September 2023
- unlimited number of <places> elements. <trainPart id="..."> <formationTT formationRef="frm4711"> <passengerUsage> <places category='class1' count='5'/> <places4 KB (666 words) - 12:16, 13 September 2022
- child of <operatingPeriod> Element <specialService>, child of <operatingPeriodRef>115 bytes (10 words) - 11:49, 14 June 2017
- <macroscopicNode ocpRef='ocp_BHW'/> </trackBegin> <trackEnd id='trn_BXH_80.6207.1_1' pos='60856' absPos='13424'> <macroscopicNode ocpRef='ocp_BXH'/> </trackEnd>716 bytes (62 words) - 14:35, 10 October 2023
- trackLocation Parent: <location> Children: <trackRef> [1..1] Defines a track based area location.(introduced with version 2.5) None None Not yet described221 bytes (38 words) - 16:38, 8 October 2021
- Parent: <operatingRules> Children: <additionalName>, <any>, <childRule>, <objectRef> [1..∞] The element operatingRule describes a single special operating rule497 bytes (409 words) - 10:17, 24 October 2022
- Element <ocpRef>, child of <path> Element <ocpRef>, child of <controller>80 bytes (10 words) - 16:18, 11 January 2019
- weiterzugeben. <trainPart id='tp_1' > <operatingPeriodRef ref='opp_once_a_day'/> <ocpsTT> <ocpTT sequence='1' ocpRef='ocp_A' ocpType='stop'> <times scope='earliest'23 KB (2,742 words) - 17:27, 24 September 2023
- IS:releaseGroup Parent: <route> Children: <trackSectionRef> [0..∞] (introduced with version 2.5) This element refers to an extended feature of a route746 bytes (130 words) - 14:12, 13 November 2021
- import interface must not: contain external connections with a missint @trainRef attribute contain connections with @nonConnection attribute value of true20 KB (238 words) - 18:57, 22 January 2024
- enumeration lists. {{RailMLType|<type-name>}} example: {{RailMLType|tGenericRef}} results in xs:IDREF It shows a link to the basic W3C XML schema type https://www10 bytes (575 words) - 21:29, 23 January 2020
- <platformEdges> (id, pos, absPos, length, dir, height, side, ocpRef, parentPlatformEdgeRef) <radiusChanges> (id, pos, absPos, dir, radius, superelevation10 bytes (335 words) - 16:12, 3 February 2020
- Abschnitten kompensiert. <trainPart> <ocpsTT> <!-- ... --> <ocpTT sequence="24" ocpRef="ocp_X" ocpType="stop"> <!-- scheduled stop time at "X" is 30 seconds, while5 KB (522 words) - 12:52, 12 April 2024
- Abschnitten kompensiert. <trainPart> <ocpsTT> <!-- ... --> <ocpTT sequence="24" ocpRef="ocp_X" ocpType="stop"> <!-- scheduled stop time at "X" is 30 seconds, while4 KB (507 words) - 13:04, 15 May 2024
- purposes train types <category> railway undertaking (<ordererRef>, <operatorRef>, <slotHolderRef> -> references to organizational units that are marked as10 bytes (523 words) - 16:12, 3 February 2020
- elements/attributes: formation (ID, name); trainOrder; vehicleRef (orderNumber, vehicleRef, vehicleCount) vehicle (ID, name, length, speed, bruttoWeight10 bytes (146 words) - 16:12, 3 February 2020
- length, type, trackContinueCourse) <crossSections> (id, pos, absPos, dir, ocpRef) <trackBegin> (id, pos, absPos) <trackEnd> (id, pos, absPos) <mileageChanges>10 bytes (180 words) - 16:12, 3 February 2020
- Element <controllerRef>, child of <ocp> Element <controllerRef>, child of <locallyControlledArea>104 bytes (10 words) - 13:43, 5 October 2018
- existing operational point within the target system <formation> x <vehicleRef> x <vehicle> x used for referencing an existing vehicle within the target10 bytes (688 words) - 16:12, 3 February 2020
- Usage in use case 'operational connection management' @trainRef No usage Optional @trainPartRef No usage Optional @minConnTime Optional Optional @maxConnTime858 bytes (0 words) - 16:19, 8 November 2022
- Currently the track and platform information shall be provided via the trackRef attribute linking the corrosponding element in the infrastructure. However10 bytes (751 words) - 16:12, 3 February 2020