Search results
Jump to navigation
Jump to search
- TT:train (section Usage of operational and commercial trains in railML® for coupled and shared trains)2' position='2'/> </trainPartSequence> </train> operational trains: <train id='tro_1' type='operational' trainNumber='456'> <trainPartSequence sequence='1'>12 KB (2,023 words) - 20:58, 22 January 2024
- railML® 2, it is possible to describe and validate that a <train> must reference one or more <trainPart>s, that all <trackElements> must have a position on the10 bytes (579 words) - 15:58, 18 May 2020
- attribute <trainPartRef>.ref from any train to find out which one (or more) refers to the current train part. For more information on trains an train parts9 KB (1,629 words) - 21:03, 22 January 2024
- position='1'/> </trainPartSequence> </train> <train id='tro_421' type='operational' trainNumber='421'> <trainPartSequence sequence='1'> <trainPartRef ref='tp24 KB (3,449 words) - 18:37, 22 January 2024
- elements <tafTapTsiTrainID> and <trainNumber> of <externalReference> an external train may be referenced. In this case @trainRef and @trainPartRef shall not25 KB (3,398 words) - 20:30, 22 January 2024
- id='ocp01' name='Pulsnitz' type='operationalName'> <propOperational operationalType='station' orderChangeable='true' ensuresTrainSequence='true'/> <propService18 KB (2,618 words) - 16:53, 19 March 2024
- <runTimes> additionalReserve, minimalTime, operationalReserve <alternativeSectionsTT> <alternativeSectionTT> description, distance, lineRef, percentageSupplement112 KB (4,754 words) - 18:02, 3 April 2022
- schedule (rostering). This schedule is focussed on the trains rather than on the personell operating the trains. In dem Element <rostering> werden alle Informationen7 KB (1,167 words) - 20:40, 22 January 2024
- IS:state (redirect from IS:state crossSection)Leistungsphasen (Lph) 3 bis Lph 8 nach deutscher HOAI (external link). operational The element is operational and can be used regularly. Das Element ist betriebsfähig5 KB (753 words) - 17:21, 19 January 2024
- Dev:categoryUsage (redirect from TT:categoryUsage) (section How to find out whether a train or train part is for passengers or freight?)stable --> <trainPartRef ref="tp_3" position="1"/> </trainPartSequence> </train> The attribute categoryRef at <train> for the operational category is normally15 KB (1,905 words) - 11:46, 23 March 2023
- TT:stopDescription ocpTT ocpsTT trainPart (section Operational stop infrastructure, by IM | Betriebshalt EIU)version 2.2) The train shall pass through this operating point and must not come to a stop for operational reasons (occupied block section, train crossing,11 KB (1,367 words) - 17:56, 24 September 2023
- version 2.2) The train shall pass through this operating point and must not come to a stop for operational reasons (occupied block section, train crossing,7 KB (917 words) - 18:11, 24 September 2023
- Dev:Midnight overrun (redirect from TT:Midnight overrun) (section Example 3: Midnight overrun between linked <trainPart>s / Beispiel 3: Mitternachtsübergang zwischen verknüpften <trainPart>s)departureDay='1'/> </ocpTT> <ocpsTT> </trainPart> Please note that both <trainPart>s reference the same <operatingPeriod>. The fact that one <trainPart> will arrive19 KB (2,347 words) - 18:40, 19 January 2024
- 2.railml.org/wiki/TT:additionalName_trainPart" /> + <xs:documentation source="https://wiki2.railml.org/wiki/TT:additionalName_train" /> + <xs:documentation331 KB (27,016 words) - 10:56, 8 October 2021
- Dev:Examples for a non-zero operating day offset at the first ocpTT of a train run (section Examples for a non-zero operating day offset at the first <ocpTT> of a train run / Beispiele für einen Verkehrstage-Offset ungleich Null an der ersten <ocpTT> eines Zuglaufs)weiterlaufen. <train trainNumber="1" type="operational"> <!-- From Bf_B to Bf_C --> <trainPartSequence sequence="1"> <trainPartRef ref="tp1_1"/> </trainPartSequence>8 KB (1,098 words) - 18:21, 19 January 2024
- false false IS:trainProtection none IS:trainProtectionChange none TT:blockPart 0 0 TT:blockPartSequence 0 TT:mean 0 0 TT:median 0 0 TT:times 0 05 KB (31 words) - 18:14, 22 May 2023
- org/index.php?title=TT:additionalName_trainPart" /> - <xs:documentation source="http://wiki.railml.org/index.php?title=TT:additionalName_train" /> - <xs:documentation398 KB (34,006 words) - 10:54, 8 October 2021
- Dev:changes/2.5 (section @processStatus set to deprecated for <trainPart>, <train> and <trainGroup>)element was added to the <ocpTT> called <alternativeSectionsTT>. It serves as a container for a number of <alternativeSectionTT> elements that can each be29 KB (97 words) - 19:00, 22 January 2024
- Dev:changes/2.4 (section Element <trainPartSequence> has been expanded by the children <topologyReference>)the train. train element sample: <train type="operational" id="train-1455532037" processStatus="actual"> <trainPartSequence sequence="1"> <trainPartRef23 KB (104 words) - 11:10, 3 May 2022
- Main Page (section Timetable and Rostering (TT))rostering. Train Parts: The basic parts of a train with the same characteristics such as formation and operating period. The train part includes the actual9 KB (916 words) - 12:29, 22 February 2024