Search results
Jump to navigation
Jump to search
- 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