Search results

that it does not make sense to specify a stopOnRequest and at the same time that the train is not allowed to stop. Such rules restricting the contents, or

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

<baseItineraryPoint> elements with commercially relevant stops (<stop> with an <isCommercial> element). For the each stop the following data is shown: published times:

with a sequence of <ocpTT> elements with commercially relevant stops (<stopDescription> with commercial='true'). For the each stop the following data is

Logical Train Positions Subschema: Infrastructure   Related subschemas: IL TT RS  Reported by: Siemens Mobility For general information on use cases see

departure Minimum stop time Stop type, stop description Commercial connections Infrastructure <ocpTT> Ordered stops Rolling stock <formationTT> Loco types Weight

frequency. Typically timetable data is exchanged on a macroscopic level, so that stop patterns of the trains can be described. It should however also be possible

TT:reserves TT:routeRef TT:routeRefs TT:rule TT:startPoint TT:stop:activities TT:stop:announcements TT:stop:passengerTextInfos TT:stoppingPlaceRef TT:tafTapTsiId

railway undertakings (//organizationalUnit/isRailWayUndertaking)) stop types (<stop>/<pass>) train status, information about the planning state of the

Autoexport from the XML-Schema for element TT:transportServiceRef of railML® version 3.2 UML-visualization of TT Documentation Allows referencing a transport

<infrastructure> is referenced from <ocpTT>.ocpRef to <ocp>.id (mandatory), from <sectionTT>.lineRef to <line>.id (optional), from <sectionTT>.<trackRef>.ref to <track>

shall stop. Timetable can optionally reference to a specific route. The Stop Description (Stop, No Stop, Stop on Demand, Stop only for Exit, Stop only for

vary per itinerary section), including coupling and branching of trains Stops, stations, tracks, track sections. They should refer to a validity, possibly

ate;startTime;type ocpsTT TT trainPart ocpTT ocpTT TT ocpsTT times;connections;statistics;sectionTT;stopDescription alignment;ocpRef;ocpType;offset;re

/> </rail:sectionTT> <rail:stopDescription commercial="true" guaranteedPass="true" onOff="both" operatingPeriodRef="" operationalStopOrdered="true" purpose=""

TT:reserves TT:reserve CO:name TT:rule TT:timeBasedRule TT:routeRefs TT:routeRef TT:trackRefs TT:trackRef TT:pass TT:referencePoint TT:times TT:arrival TT:departure

|element=ocpTT |comment= |subschema=[[TT]] |parent=[[ocpsTT]] |children=[[times]], [[connections]], [[statistics]], [[sectionTT]], [[stopDescription]] |att