Search results

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 further

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 reactivate

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 further

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 further

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 further

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 further

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 further

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 further

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 further

to define a (potentially different) formation for a train part on each of its operating days. The assigned formation must match the restrictions of the

use: Infrastructure (IS) and Interlocking (IL). The Timetable and Rostering (TT) and Rollingstock (RS) subschemas are in active development and can be obtained

referenced: from <ocpTT>.ocpRef to <ocp>.id (mandatory) Rolling stock is referenced: from <formationTT>.formationRef to <formation>.id (optional) from <rostering>

<rollingstock> is referenced from <formationTT>.formationRef to <formation>.id (optional) from <rostering>.formationRef to <formation>.id (optional) from <rostering>

stop TT:feeder TT:followupSection TT:followupSections TT:formationInformation TT:identifier TT:identifier:range TT:identifiers TT:isCancelled TT:isCommercial

focused on formations. Such formations are considered to be a sequence of vehicles, at least one vehicle. Typically, vehicles of such formations are not specific

Automatic Schemaexport for Element formationInformation

Infrastructure <ocpTT> Ordered stops Rolling stock <formationTT> Loco types Weight Length Maximum speed Infrastructure restrictions As a minimum the <ocpTT> elements

infrastructure: <operationalPoint>, <platform>, <platformEdge> rolling stock: <formation> (?) interlocking: - This section serves to specify the required data regarding

Autoexport from the XML-Schema for element TT:activityTrainReverse of railML® version 3.2 UML-visualization of TT Documentation Allows to specify that the

Interlocking: -- Infrastructure: <operationalPoint> (macroscopic) Rolling stock: <formation> (optional) Production by the user on demand (ad-hoc), infrequent. Whole

Linie Zuggattung Gültigkeit (Operating Period) und Ausfallinformationen Formation Zugbehandlungen (Flügeln, Kuppeln, Schwächen, Verstärken, Zugtausch – wie

Autoexport from the XML-Schema for element TT:activityOther of railML® version 3.2 UML-visualization of TT Documentation Represents activities that cannot

Autoexport from the XML-Schema for element TT:activityLoad of railML® version 3.2 UML-visualization of TT Documentation Represents (commercial) loading

Autoexport from the XML-Schema for element TT:activityRollingStock of railML® version 3.2 UML-visualization of TT Documentation Allows to describe that at

<trainPartSequence> <trainPartRef> <trainPart> <formationTT> <operatingPeriodRef> <ocpsTT> <time> <sectionTT> <runTimes> <connections> <stopDescription> <stopTimes>

Autoexport from the XML-Schema for element TT:activityTripDependency of railML® version 3.2 UML-visualization of TT Documentation Allows to specify a dependency

Autoexport from the XML-Schema for element TT:activityCrewDependency of railML® version 3.2 UML-visualization of TT Documentation Allows to specify a dependency

commercial train data itineraries with optional platform assignments commercial formation requirements (may vary per itinerary section), commercial coupling and

the vehicle group is represented by vehicle types that are bundled into formations. The blocks in question are primarily operational journeys, but also other

Autoexport from the XML-Schema for element TT:operationalTrainSectionPart of railML® version 3.2 UML-visualization of TT Documentation The operational train section

number of various vehicle types and train formations Technical, Performance Mandatory elements/attributes: formation (ID, name); trainOrder; vehicleRef (orderNumber

REDIRECT UC:TT:ExchangeOfFormationData

changes of RS depending on the number of various vehicle types and train formations Technical, Performance Energy Expected elements/attributes in addition

true. So, the following are equivalent: <formationInformation formationRef="fm-2"/> <formationInformation formationRef="fm-1" orientationReversed="true"/>

location arrival and departure times Vehicle attributes (Rollingstock): Formation or consist (mass, length) profile Maximum speed Braking parameters (braking