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
- deadrun="true" /> </categories> <trainParts> <trainPart id="tp_1" categoryRef="cat_1"> <ocpsTT> </ocpsTT> </trainPart> </trainParts> </timetable> </railml>12 KB (1,930 words) - 15:44, 13 May 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
- <runTimes> additionalReserve, minimalTime, operationalReserve <alternativeSectionsTT> <alternativeSectionTT> description, distance, lineRef, percentageSupplement112 KB (4,754 words) - 18:02, 3 April 2022
- id='ocp01' name='Pulsnitz' type='operationalName'> <propOperational operationalType='station' orderChangeable='true' ensuresTrainSequence='true'/> <propService18 KB (2,618 words) - 16:53, 19 March 2024
- 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
- 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
- crossSections --> - <!-- +- crossSection --> - <!----> - - <xs:complexType name="eCrossSections"> - <xs:sequence> - <xs:element name="crossSection" typ531 KB (37,474 words) - 10:55, 8 October 2021
- TT:trainPartSequence train (section Position of trainPartSequence in the XML-Tree / Position von trainPartSequence im XML-Baum)Paris-Nord --> <trainPartRef ref="CNL_242_2"/> </trainPartSequence> </train> Each train names all its train parts in its element <trainPartRef> with the attributes7 KB (964 words) - 21:04, 22 January 2024
- Dev:changes/2.2 (section trainPart)The key trainPartKey has been expanded by keyref trainPart-connectionKeyref. The key train-connectionKeyref has been expanded by keyref train-connectionKeyref36 KB (103 words) - 13:54, 21 February 2022
- connections with a missint @trainRef attribute contain connections with @nonConnection attribute value of true contain trains or trainParts with a @cancellation20 KB (238 words) - 18:57, 22 January 2024
- </xs:complexType> - <xs:complexType name="eTrainParts"> <xs:sequence> <xs:element name="trainPart" type="rail:eTrainPart" maxOccurs="unbounded"> @@ -484,6 +487108 KB (9,484 words) - 10:56, 8 October 2021
- TT:times ocpTT ocpsTT trainPart (section Special case of a non-zero operating day offset at the first <ocpTT> of a train run / Spezialfall eines Verkehrstage-Offset ungleich Null an der ersten <ocpTT> eines Zuglaufs)the last trainPart (section) of a train: If this attribute is set at the last <ocpTT> of a <trainPart> that is also the last of the <trainPartSequence>23 KB (2,742 words) - 17:27, 24 September 2023
- samePlatform, trainPartRef, trainRef <externalReference> <tafTapTsiTrainID> companyCode, core, objectType, startDate, timetableYear, variant <trainNumber> trainNumber65 KB (2,931 words) - 12:19, 8 October 2021
- Haltzeitzuschläge auf den angrenzenden Abschnitten kompensiert. <trainPart> <ocpsTT> <!-- ... --> <ocpTT sequence="24" ocpRef="ocp_X" ocpType="stop"> <!-- scheduled5 KB (522 words) - 12:52, 12 April 2024
- Haltzeitzuschläge auf den angrenzenden Abschnitten kompensiert. <trainPart> <ocpsTT> <!-- ... --> <ocpTT sequence="24" ocpRef="ocp_X" ocpType="stop"> <!-- scheduled4 KB (507 words) - 13:04, 15 May 2024
- org/wiki/TT:trainPartSequence" /> </xs:annotation> </xs:element> - <xs:element name="tafTapTsiTrainID" type="rail:eTapTsiTransportOperationalIdentifier"104 KB (9,170 words) - 10:56, 8 October 2021
- samePlatform, trainPartRef, trainRef <externalReference> <tafTapTsiTrainID> companyCode, core, objectType, startDate, timetableYear, variant <trainNumber> trainNumber72 KB (3,235 words) - 11:59, 11 October 2021
- UC:TT:ATimetableForACompetition (category Use case (TT))<line>s are included Each <trainPart> must be covered by exactly one operational train. If commercial trains are given, each <trainPart> must be covered by exactly10 bytes (1,903 words) - 16:12, 3 February 2020
- velocities. Vectors, lists (enumerations) or structures are not covered in this section! The following table lists the variables which can currently be assigned4 KB (85 words) - 12:16, 3 June 2019
- the last trainPart (section) of a train: If this attribute is set at the last <ocpTT> of a <trainPart> that is also the last of the <trainPartSequence>6 KB (594 words) - 20:48, 22 January 2024
- UC:TT:FGIInTrain (category Use case (TT)) (section Which specific TT data do you expect to receive/send (elements)?)least this use case needs the following elements: the elements <train> and <trainPart> to supply information about line, direction and relevant information10 bytes (677 words) - 16:12, 3 February 2020
- UC:TT:ExchangeOfFormationData (category Use case (TT)) (section Which specific TT data do you expect to receive/send (elements)?)railML object types: <operationalTrain> <operationalTrainVariant> <operationalTrainSection> <operationalTrainSectionPart> <operationalPoint> <vehicle> All10 bytes (688 words) - 16:12, 3 February 2020
- UC:TT:TAF/TAP TSI (category Use case (TT)) (section Which specific TT data do you expect to receive/send (elements)?)elements (e.g. trains) To be specified As a bare minimum the commercial view of a <train> can be reduced to one <trainPart> with a sequence of <ocpTT> elements10 bytes (592 words) - 16:12, 3 February 2020
- UC:TT:TimetableInformation (category Use case (TT)) (section Which specific TT data do you expect to receive/send (elements)?)following changes: full cancellation of a train partial cancellation - i.e. of a trainPart extra train or trainPart cancelled stop extra stop etc. Terms and10 bytes (751 words) - 16:12, 3 February 2020
- <timetable>.<trainParts>.<trainPart>.<ocpsTT>.<ocpTT>.<sectionTT>.lineRef must be used if <line>s are included <timetable>.<trainParts>.<trainPart>.<ocpsTT>.<ocpTT>16 KB (2,372 words) - 16:07, 12 November 2021