From railML 3 Wiki
Jump to navigation Jump to search




Autoexport from the XML-Schema for element RS:formation of railML® version 3.2
Documentation The formation collects all data of vehicles coupled as train for operation.
Subschema rollingstock
Parents* formations
Children designator (1..*), trainBrakes (0..*), trainEngine (0..*), trainOrder (1..*), trainResistance (0..1)
  • haulingWeight: The complete weight of the formation but without locomotive in metric tons. This is not useful for multiple units. (optional; xs:decimal),

  • length: The overall length of the entire formation in metres. (optional; xs:decimal),

  • maximumAxleLoad: The maximum axle load within the formation in metric tons. It is the highest value from any contained vehicle. (optional; xs:decimal),

  • maximumCantDeficiency: The resulting maximum permissible cant deficiency for this formation measured in millimetres. In order to get the cant deficiency class as per UNISIG this would require to combine it with the airBakeApplicationPosition of the trainBrakes. (optional; xs:decimal),

  • numberOfAxles: The number of axles of the entire formation. (optional; xs:positiveInteger),

  • numberOfWagons: The number of non-powered wagons in the formation. This value is only useful in case of a loco hauled train. (optional; xs:positiveInteger),

  • speed: The maximum permissible speed in km/h of the entire formation as limited by the lowest maximum of contained vehicles. (optional; xs:decimal),

  • totalWeight: The complete weight of the formation with payload in metric tons. (optional; xs:decimal),

  • 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
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 RS subschema. It is available only in railML® 3.2. Do not hesitate to contact for further questions.

Changes 3.1→3.2

Introduced with version 3.2.


Best Practice / Examples

Additional Information


Open Issues