Search results
Jump to navigation
Jump to search
- This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further523 bytes (38 words) - 21:56, 25 April 2022
- to use cases. CO Use Cases – IL Use Cases – IS Use Cases – RS Use Cases – TT Use Cases View/edit list on the separate source page If you want to reactivate7 KB (287 words) - 16:17, 13 May 2024
- This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further523 bytes (38 words) - 21:55, 25 April 2022
- This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further523 bytes (38 words) - 21:55, 25 April 2022
- This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further515 bytes (38 words) - 21:55, 25 April 2022
- This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further516 bytes (38 words) - 21:55, 25 April 2022
- This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further1 KB (91 words) - 10:22, 13 October 2022
- This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further525 bytes (38 words) - 21:55, 25 April 2022
- This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further525 bytes (38 words) - 21:55, 25 April 2022
- UC:TT:ExchangeOfFormationData (category Use case (TT)) (section Which specific TT data do you expect to receive/send (elements)?)to define a (potentially different) formation for a train part on each of its operating days. The assigned formation must match the restrictions of the6 KB (688 words) - 13:26, 13 March 2023
- Main Page (section Timetable and Rostering (TT))use: Infrastructure (IS) and Interlocking (IL). The Timetable and Rostering (TT) and Rollingstock (RS) subschemas are in active development and can be obtained10 KB (1,041 words) - 10:56, 2 May 2024
- UC:TT:FGIInTrain (category Use case (TT)) (section Which specific TT data do you expect to receive/send (elements)?)referenced: from <ocpTT>.ocpRef to <ocp>.id (mandatory) Rolling stock is referenced: from <formationTT>.formationRef to <formation>.id (optional) from <rostering>9 KB (677 words) - 18:10, 27 June 2022
- UC:TT:ATimetableForACompetition (category Use case (TT))<rollingstock> is referenced from <formationTT>.formationRef to <formation>.id (optional) from <rostering>.formationRef to <formation>.id (optional) from <rostering>16 KB (1,903 words) - 13:27, 13 March 2023
- stop TT:feeder TT:followupSection TT:followupSections TT:formationInformation TT:identifier TT:identifier:range TT:identifiers TT:isCancelled TT:isCommercial3 KB (758 words) - 14:47, 27 June 2022
- UC:TT:RunTimeCalculationInput (category Use case (TT))focused on formations. Such formations are considered to be a sequence of vehicles, at least one vehicle. Typically, vehicles of such formations are not specific6 KB (858 words) - 12:09, 25 March 2024
- Automatic Schemaexport for Element formationInformation2 KB (5 words) - 15:48, 17 May 2024
- UC:TT:SlotOrdering (category Use case (TT)) (section Which specific TT data do you expect to receive/send (elements)?)Infrastructure <ocpTT> Ordered stops Rolling stock <formationTT> Loco types Weight Length Maximum speed Infrastructure restrictions As a minimum the <ocpTT> elements2 KB (273 words) - 13:26, 13 March 2023
- UC:TT:TimetableInformation (category Use case (TT)) (section Which specific TT data do you expect to receive/send (elements)?)infrastructure: <operationalPoint>, <platform>, <platformEdge> rolling stock: <formation> (?) interlocking: - This section serves to specify the required data regarding5 KB (751 words) - 13:28, 13 March 2023
- Autoexport from the XML-Schema for element TT:activityTrainReverse of railML® version 3.2 UML-visualization of TT Documentation Allows to specify that the5 KB (5 words) - 21:55, 25 April 2022
- UC:TT:LongTermStrategicTimetabling (category Use case (TT))Interlocking: -- Infrastructure: <operationalPoint> (macroscopic) Rolling stock: <formation> (optional) Production by the user on demand (ad-hoc), infrequent. Whole4 KB (523 words) - 11:14, 18 July 2022
- UC:TT:PassengerInformationAtStations (category Use case (TT))Linie Zuggattung Gültigkeit (Operating Period) und Ausfallinformationen Formation Zugbehandlungen (Flügeln, Kuppeln, Schwächen, Verstärken, Zugtausch – wie6 KB (691 words) - 13:28, 13 March 2023
- Autoexport from the XML-Schema for element TT:activityOther of railML® version 3.2 UML-visualization of TT Documentation Represents activities that cannot5 KB (5 words) - 12:43, 8 February 2024
- Autoexport from the XML-Schema for element TT:activityLoad of railML® version 3.2 UML-visualization of TT Documentation Represents (commercial) loading5 KB (5 words) - 12:43, 8 February 2024
- Autoexport from the XML-Schema for element TT:activityRollingStock of railML® version 3.2 UML-visualization of TT Documentation Allows to describe that at5 KB (5 words) - 21:55, 25 April 2022
- UC:TT:IntegratedTMS (category Use case (TT))<trainPartSequence> <trainPartRef> <trainPart> <formationTT> <operatingPeriodRef> <ocpsTT> <time> <sectionTT> <runTimes> <connections> <stopDescription> <stopTimes>16 KB (1,744 words) - 18:21, 13 May 2024
- Autoexport from the XML-Schema for element TT:activityTripDependency of railML® version 3.2 UML-visualization of TT Documentation Allows to specify a dependency6 KB (5 words) - 12:43, 8 February 2024
- Autoexport from the XML-Schema for element TT:activityCrewDependency of railML® version 3.2 UML-visualization of TT Documentation Allows to specify a dependency7 KB (5 words) - 12:43, 8 February 2024
- UC:TT:ImportCompleteTimetableForVehicleWorkingSchedulingAndVehicleWorkings (category Use case (TT))commercial train data itineraries with optional platform assignments commercial formation requirements (may vary per itinerary section), commercial coupling and3 KB (355 words) - 18:11, 27 June 2022
- UC:TT:LongTermCirculationPlanning (category Use case (TT))the vehicle group is represented by vehicle types that are bundled into formations. The blocks in question are primarily operational journeys, but also other6 KB (926 words) - 17:00, 4 December 2023
- Autoexport from the XML-Schema for element TT:operationalTrainSectionPart of railML® version 3.2 UML-visualization of TT Documentation The operational train section3 KB (5 words) - 12:43, 8 February 2024
- number of various vehicle types and train formations Technical, Performance Mandatory elements/attributes: formation (ID, name); trainOrder; vehicleRef (orderNumber1 KB (146 words) - 13:29, 13 March 2023
- REDIRECT UC:TT:ExchangeOfFormationData10 bytes (2 words) - 17:37, 24 November 2019
- changes of RS depending on the number of various vehicle types and train formations Technical, Performance Energy Expected elements/attributes in addition2 KB (236 words) - 13:43, 13 March 2023
- true. So, the following are equivalent: <formationInformation formationRef="fm-2"/> <formationInformation formationRef="fm-1" orientationReversed="true"/>7 KB (771 words) - 13:39, 13 March 2023
- location arrival and departure times Vehicle attributes (Rollingstock): Formation or consist (mass, length) profile Maximum speed Braking parameters (braking3 KB (306 words) - 13:48, 13 March 2023