IS:isEurobaliseGroup

From railML 3 Wiki
Jump to navigation Jump to search

Introduction

Documentation

Syntax

Autoexport from the XML-Schema for element IS:isEurobaliseGroup of railML® version 3.2
Documentation use this child element to specify that the BaliseGroup is a Eurobalise BaliseGroup
Subschema infrastructure
Parents* baliseGroup
Children None
Attributes:
  • countryID: corresponds to ETCS variable NID_C describing the countryID of the balise group (obligatory; xs:integer),

  • groupID: corresponds to ETCS variable NID_BG describing the balise group ID (obligatory; xs:integer),

  • isLinked: corresponds to ETCS variable Q_LINK (optional; xs:boolean),

  • linkReactionNominal: corresponds to ETCS variable Q_LINKREACTION_nominal (optional; xs:string)
Possible values:
  • applyServiceBrake
  • noReaction
  • trainTrip,

  • linkReactionReverse: corresponds to ETCS variable Q_LINKREACTION_nominal (optional; xs:string)
Possible values:
  • applyServiceBrake
  • noReaction
  • trainTrip,

  • locationAccuracy: corresponds to ETCS variable Q_LOCACC (optional; xs:decimal),

  • mVersion: corresponds to ETCS variable M_VERSION (optional; xs:nonNegativeInteger),

  • usesPackage44: corresponds to ETCS variable NID_XUSER;
    use only if balise group application type includes NTC (optional; xs:integer),

  • virtualCoverageID: corresponds to ETCS variable NID_VBCMK;
    use only if balise group is covered virtually (optional; xs:integer)
*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 IS 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