Search results

Reference to the part of the train from where the speed change is valid. Normally, a speed change with a speed that is higher than the permitted speed in

in railML® definiert. For change of the mileage direction by <mileageChange> see Remarks and open issues on mileage changes.

belegten Bahnhofsgleises powerSystemChange: Systemwechsel Stop caused by a change of power supply (e.g. to change pantograph) für Halte wegen Wechsels

of frame contracts yearly for LTP planning the regular timetable regular changes for STP planning, e.g. for engineering infrastructure works, special event

the train(part) changes the direction - no matter whether the formation changes, reverses or neither of both. trainReverse with change of formation = e

whereas local definitions are generally set in change-elements like <electrificationChange> and <speedChange> Not yet described. / Noch nicht beschrieben

bureaucracy, the beginning and ending of trains is regarded as “train order change”. <ocp id=… name=…> <propOperational operationalType='station' orderChangeable='true'

After publication, take care, that changes are incorporated into the wiki asap. New or changed attribute: Add or change the attribute in "attributes" providing

code example defines gauge change of the track that connects Arnsdorf West and Nord junctions. <gaugeChanges> <gaugeChange id='gac_80.6228_0' pos='0' absPos='942'

dayIndex). Whether a change of operating days during a train run actually happens can only be obtained by comparing the shifted bit masks. A change of <operatingPeriodRef>

<gaugeChange>, <geoMapping>, <gradientChange>, <levelCrossing>, <lock>, <mileageChange>, <ocp>, <operationModeChange>, <ownerChange>, <platformEdge>, <p

exist? How often is data exchanged? What is the granularity? How does it change over time, if it does at all? Diagrams/images would be helpful to visualize

station name to a typical usage or give it a “right to exist”. But it does not change the behaviour of a railML® parser when decoding the file. So, if the file

IS:states   Parent: (miscellaneous) – see Category:states Children: <state> [0..1] Container to define disabled/enabled pieces of infrastructure. None

physically signalised speed restriction or speed change, always both elements need to be modelled: the <speedChange> and the <speed> element of <signal>. In the

exist? How often is data exchanged? What is the granularity? How does it change over time, if it does at all? Diagrams/images would be helpful to visualize

train part in subsequent sections applies for instance if the operating days change at an intermediate station. For more information, please read Train coupling

Thus, it is mandatory to place a <gradientChange> at the beginning of a model or at a mileage direction change once for each direction. The gradient itself

additional information. While e. g. operating days or no. of vehicles may change during a train’s run, all such properties of a <trainPart> stay constant

IS:speedChangeRef   Parent: <speed_signal> Children: None [0..∞] Reference to a speed change. ref: reference is required because it's the purpose of the