TT:activityTrainReverse

From railML 3 Wiki
Jump to navigation Jump to search

Introduction

Documentation

Syntax

Autoexport from the XML-Schema for element TT:activityTrainReverse of railML® version 3.2
Documentation Allows to specify that the train is reversed at the station. Usually that means that previously forward facing parts of the train are subsequently facing backwards, and vice versa. However, if a turntable or similar infrastructure is involved, the reversal may not apply to all parts. The resulting formation reversal is indicated by the attribute @orientationReversed at the formationInfo of the operationalTrainSectionPart.
Subschema timetable
Parents* activities
Children previousActivities (0..1)
Attributes:
  • minDuration: Minimum time scheduled for the activity. (optional; xs:duration),

  • trainActivityClassification: Allows to further classify an activity. Should not be used to describe aspects of another activity. E.g. an activitytrainReverse should not be classified "catering" and an activityTripDependency should not be classified gaugeChange. (optional; xs:string; patterns: other:w{2,})
Possible values:
  • authorityCheck: Stop for purposes of passport or customs check or other authorities
  • catering: Supply or disposal of passengers or payload, e. g. catering
  • collect: Couple vehicles / train parts - intended for non-self-propelling train parts. Please consider relation to formations (as far as used)
  • crewBreak: Stop for engine or train crew to pause
  • crewChange: Stop to change engine or train crew
  • drop: Uncouple vehicles / train parts - intended for non-self-propelling train parts. Please consider relation to formations (as far as used)
  • engineAttach: Receiving of pilot/pushing/double-heading engines - no train coupling
  • engineChange: Change of engine (no train coupling and sharing / splitting)
  • engineDetach: Dropping of pilot/pushing/double-heading engines - no train splitting
  • gaugeChange: Stop caused by a change of gauge (e.g. to change or convert axles)
  • join: Couple vehicles / train parts - intended for self-propelling train parts. Please consider relation to formations (as far as used)
  • misc: miscellaneous stop activity
  • movementAuthority: Stop to receive the permission to proceed into the next route section
  • occupation: Stop caused by occupation of lines, tracks, blocks incl. crossing without further specification
  • occupationBlock: Stop caused by occupation of route by another train running ahead
  • occupationCrossing: Stop caused by occupation of route by an oncoming train
  • occupationStation: Stop caused by occupation of station track(s)
  • photo: stop for passengers to take photos
  • powerSystemChange: Stop caused by a change of power supply (e.g. to change pantograph)
  • releaseLine: Stop to release the permission to proceed from the previous route section
  • runAround: Shunting of the engine to the other end of train (normally during change of driving direction). Normally combined with activityTrainReverse
  • shunting: Shunting movements are planned during stop (may also be used additionally to collect/drop/split/join/staple on demand)
  • shuntingPermission: Receive and/or release the permission to shunt inside ocp during stop time
  • split: Uncouple vehicles / train parts - intended for self-propelling train parts. Please consider relation to formations (as far as used)
  • staple: Notes the necessity of staple track(s) during the stop time
  • supplyOrDisposal: Supply of vehicles with operating supplies or materials or disposal of waste, including taking water for steam traction or steam heating
  • vehicleInspection: Stop for technical / technological vehicle inspections,

  • id: unique identifier (obligatory; xs:string; patterns: (urn:uuid:)?[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}|{[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}}); compare: Dev:Identities
*Notice:
Elements may have different parent elements. As a consequence they may be used in different contexts.
Please, consider this as well as a user of this wiki as when developing this documentation further.
Aspects that are only relevant with respect to one of several parents should be explained exclusively in the documentation of the respective parent element.


 

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 questions.


Changes 3.1→3.2

Introduced with version 3.2.

Semantics

Best Practice / Examples

Additional Information

Notes

Open Issues