IS:phaseSeparationSection

From railML 3 Wiki
Jump to: navigation, search

Introduction

Documentation

Syntax

Autoexport from the XML-Schema for element IS:phaseSeparationSection of railML® version 3.2
Documentation child element summarizing the phase separation parameters
Subschema infrastructure
Parents* electrificationSection
Children None
Attributes:
  • lengthPhaseSeparation: length of the phase separation section in contact line, in [m] (optional; xs:decimal),

  • switchOffBreaker: flag, whether the main circuit breaker has to be switched off when passing the phase separation (optional; xs:boolean),

  • lowerPantograph: flag, whether the pantographs have to be lowered when passing the phase separation (optional; xs:boolean)
*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:phaseSeparationSection of railML® version 3.1
Documentation child element summarizing the phase separation parameters
Subschema infrastructure
Parents* electrificationSection
Children None
Attributes:
  • lengthPhaseSeparation: length of the phase separation section in contact line, in [m] (optional; xs:decimal),

  • switchOffBreaker: flag, whether the main circuit breaker has to be switched off when passing the phase separation (optional; xs:boolean),

  • lowerPantograph: flag, whether the pantographs have to be lowered when passing the phase separation (optional; xs:boolean)
*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.

Semantics

Best Practice / Examples

Additional Information

Notes

Open Issues