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.3
    
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: if this balise group could not be detected by an ETCS-equipped train in the expectation window (e.g. because the balise group is defected or stolen), then the train reacts by applying the service break. If the service break is not available the emergency break is triggered.
  • noReaction: if this balise group could not be detected by an ETCS-equipped train in the expectation window (e.g. because the balise group is defected or stolen), then the train ignores this information.
  • trainTrip: if this balise group could not be detected by an ETCS-equipped train in the expectation window (e.g. because the balise group is defected or stolen), then the train reacts by triggering the emergency break.,

  • linkReactionReverse: corresponds to ETCS variable Q_LINKREACTION_reverse (optional; xs:string)
Possible values:
  • applyServiceBrake: if this balise group could not be detected by an ETCS-equipped train in the expectation window (e.g. because the balise group is defected or stolen), then the train reacts by applying the service break. If the service break is not available the emergency break is triggered.
  • noReaction: if this balise group could not be detected by an ETCS-equipped train in the expectation window (e.g. because the balise group is defected or stolen), then the train ignores this information.
  • trainTrip: if this balise group could not be detected by an ETCS-equipped train in the expectation window (e.g. because the balise group is defected or stolen), then the train reacts by triggering the emergency break.,

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


 

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: if this balise group could not be detected by an ETCS-equipped train in the expectation window (e.g. because the balise group is defected or stolen), then the train reacts by applying the service break. If the service break is not available the emergency break is triggered.
  • noReaction: if this balise group could not be detected by an ETCS-equipped train in the expectation window (e.g. because the balise group is defected or stolen), then the train ignores this information.
  • trainTrip: if this balise group could not be detected by an ETCS-equipped train in the expectation window (e.g. because the balise group is defected or stolen), then the train reacts by triggering the emergency break.,

  • linkReactionReverse: corresponds to ETCS variable Q_LINKREACTION_reverse (optional; xs:string)
Possible values:
  • applyServiceBrake: if this balise group could not be detected by an ETCS-equipped train in the expectation window (e.g. because the balise group is defected or stolen), then the train reacts by applying the service break. If the service break is not available the emergency break is triggered.
  • noReaction: if this balise group could not be detected by an ETCS-equipped train in the expectation window (e.g. because the balise group is defected or stolen), then the train ignores this information.
  • trainTrip: if this balise group could not be detected by an ETCS-equipped train in the expectation window (e.g. because the balise group is defected or stolen), then the train reacts by triggering the emergency break.,

  • 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

There exists an overview of all changes between railML® 3.1 and railML® 3.2 on page Dev:Changes/3.2.

Introduced with version 3.2.

Changes 3.2→3.3

There exists an overview of all changes between railML® 3.2 and railML® 3.3 on page Dev:Changes/3.3.

The parents have been changed.

Semantics

Best Practice / Examples

Additional Information

Notes

Open Issues