From railML 3 Wiki
Jump to navigation Jump to search

Automatic Schemaexport for Element baliseGroup

Autoexport from the XML-Schema for element IS:baliseGroup of railML® version 3.2
Documentation One or more balises which are treated as having the same reference location on the track. The telegrams transmitted by all the balises of a group form a track-to-train message [ERTMS/ETCS Glossary of Terms and Abbreviations].
Subschema infrastructure
Parents* baliseGroups
Children applicationType (1..*), areaLocation (0..*), connectedWithInfrastructureElement (0..*), designator (0..*), external (0..*), functionalType (0..*), gmlLocations (0..*), isEurobaliseGroup (0..1), isValid (0..*), linearLocation (0..*), name (0..*), networkLocation (0..*), spotLocation (0..*), typeDesignator (0..*)
  • coverage: specifies the balise group coverage as being 'physical', 'virtual', 'both' or 'none'. (optional; xs:string)
Possible values:
  • both
  • none
  • physical
  • virtual,

  • mileageDirection: specifies the orientation of the balise group in reference to the mileage / kilometer chainage (optional; xs:string)
Possible values:
  • nominal: rising
  • reverse: falling,

  • numberOfBalisesInGroup: for Eurobalises this attribute corresponds to the ETCS variable N_TOTAL incremented by 1 (optional; xs:integer),

  • id: the identifier of the object; this can be either of type xs:ID or UUID (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.