RS:formation

From railML 2 Wiki
Revision as of 18:36, 13 December 2021 by RailML Coord Documentation (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search


formation
 


Scheme description / Schemenbeschreibung

Position of formation in the XML-Tree / Position von formation im XML-Baum

Multiplicity / Anzahl

[1..∞]

Semantics / Bedeutung

The element <formation> contains all data related to a composition of single vehicles forming a complete train or a part of a train. It is not excluded to describe a train consisting of only one single vehicle.

Im Element <formation> werden alle Zug bezogene Daten aufgenommen. Dabei kann es sich wirklich um einen kompletten Zug oder nur um einen Zugteil aus mehreren Einzelfahrzeugen handeln. Es ist aber auch möglich einen nur aus einem Fahrzeug bestehenden Zug zu beschreiben.

Attributes of formation / Attribute von formation

  • id: XML-file-wide unique, machine-interpretable identity, required for later referencing that element internally. For a detailed explanation see Dev:identities.
    XML-Datei-weit eindeutige, maschineninterpretierbare Identität, die für die spätere interne Referenzierung dieses Elements erforderlich ist. Für eine detaillierte Erklärung siehe Dev:identities.
  • code (introduced with version 2.1): Machine-interpretable string (e.g. an abbreviation) used for identification of the object across exchange partners, usecase specific uniqueness constraints may apply. Please see our description of the differences between id, code and human-readable identifiers.
    Maschineninterpretierbare Zeichenkette (z.B. Abkürzung), die zur Identifizierung des Objekts auch bei Austauschpartnern verwendet wird, wobei spezifische Eindeutigkeitsbeschränkungen gelten können. Bitte beachten Sie unsere Erläuterung zu den Unterschieden zwischen id, code and menschenlesbaren Kennzeichnungen.
  • name: Established, human-readable short string, giving the object a name. Not intended for machine interpretation, please see our notice on human interpretable data fields.
    Etablierte, menschenlesbare kurze Zeichenkette, die das Objekt benennt. Nicht zur maschinellen Interpretation bestimmt, siehe Hinweise zu menschenlesbaren Datenfeldern.
  • description: Human-readable, more detailed description as addition to the name. It should give additional explanations or hints to the contents of this element. Not intended for machine interpretation, please see our notice on human interpretable data fields.
    Menschenlesbare, detailliertere Beschreibung als Ergänzung zu name. Sie soll zusätzliche Erläuterungen oder Hinweise auf den Inhalt dieses Elements geben. Nicht zur maschinellen Interpretation bestimmt, siehe Hinweise zu menschenlesbaren Datenfeldern.
  • xml:lang (introduced with version 2.1): This is a unique identifier of language. It uses basically the language standard IETF BCP 47 (external link) which may be different to ISO 639-1 (external link) or ISO 639-2 (external link). For mapping hints see relation to other standards (external link).
    This defines the language used for name and description. Use <additionalName> to provide a name and/or description in other languages.
  • formationCount: This is the number of formations of that type forming the train or train part. This can be used for example when a train is made up of several multiple units of the same type. In all other cases this value shall be 1.
  • length: This is the overall length in metres of that formation. The user has to ensure that it is the resulting sum of the length of each single vehicle the formation consists of.
  • speed: This is the maximum speed in kilometres per hour permitted for that formation. The user has to ensure, that this value is not greater than any permitted speed of the single vehicles the formation consists of.
  • weight (deprecated with version 2.1): This is the total weight in metric tons of that formation. The user has to ensure that it is the resulting sum of the weigths of each single vehicle the formation consists of.
  • bruttoWeight: This is the total brutto weight (vehicles plus payload) in metric tons of that formation, which is physical permissible. The user has to ensure that it is the resulting sum of the weigths of each single vehicle the formation consists of.
  • nettoWeight: This is the total net weight (payload only, all except vehicles) in metric tons of that formation, which is physical permissible. The user has to ensure that it is the resulting sum of the weigths of each single vehicle the formation consists of.
  • tareWeight: This is the total tare weight (empty vehicles) in metric tons of that formation. The user has to ensure that it is the resulting sum of the weigths of each single vehicle the formation consists of.
  • load (introduced with version 2.5): This is the total brutto weight (vehicles plus payload) in metric tons of that formation, which is physical permissible. In contrast to bruttoWeight this value does not contain the locomotive of this formation. The user has to ensure that it is the resulting sum of the weigths of each single vehicle the formation consists of.
  • etcsTrainCategory (introduced with version 2.4): the international train category number as specified on page 38 in ERA_ERTMS_040001 "Assignment of values to ETCS variables" v1.9 from 10/07/12

Syntactic Constraints / Syntaktische Beschränkungen

  • id: xs:ID, required
    a string, starting with a letter (a..zA..Z) or an underscore (_),
    followed by a non-colonized and non-spaced string consisting of letters, digits, points (.), dashes (-) or underscores (_)
  • code: xs:string, optional
  • name: xs:string, optional
  • description: xs:string, optional
  • xml:lang: xs:language, language identification, optional
  • formationCount: tCounter (xs:nonNegativeInteger); optional
  • length: tLengthM (xs:decimal, 6 fraction digits, length value measured in meter); optional
  • speed: tSpeedKmPerHour (xs:decimal, 5 digits and 1 fraction digit with minimum value 0, speed value measured in km/h); optional
  • weight: tWeightTons (xs:decimal, 3 fraction digits, weight value measured in metric tons); optional
  • bruttoWeight: tWeightTons (xs:decimal, 3 fraction digits, weight value measured in metric tons); optional
  • nettoWeight: tWeightTons (xs:decimal, 3 fraction digits, weight value measured in metric tons); optional
  • tareWeight: tWeightTons (xs:decimal, 3 fraction digits, weight value measured in metric tons); optional
  • load: tWeightTons (xs:decimal, 3 fraction digits, weight value measured in metric tons); optional
  • etcsTrainCategory: tEtcsTrainCategory (restriction of xs:integer; minInclusive 0; maxInclusive 15; the international train category number as specified on page 38 in ERA_ERTMS_040001 "Assignment of values to ETCS variables" v1.9 from 10/07/12); optional

The user and application has to ensure the consistancy of the information in the attributes length, speed and weight with any redundant information given for single vehicles.

Best practice & Examples / Empfohlene Anwendung & Beispiele

Not yet described. / Noch nicht beschrieben.

Notes / Anmerkungen

The attributes length, speed and weight are just for easy access. They are defined in this element if no deeper level of details is necessary.

The attributes about weight like bruttoWeight contain the values, which are physical permissible by the vehicles. However, the value for a particular train in timetable might be less than these if the loading grade is below 100%.

Open issues / Offene Punkte/Pendenzen

Not yet described. / Noch nicht beschrieben.