IS:linesideElectronicUnitIS

Introduction

Lineside Electronic Unit (LEU) ‒ a trackside electronic unit that interfaces the national trackside signalling / interlocking equipment with Eurobalise and Euroloop .

• 

  Figure 5-1: ERTMS/ETCS Level 1 with In-fill

<linesideElectronicUnitIS> has its Interlocking counterpart <linesideElectronicUnitsIL>. Interlocking properties of <linesideElectronicUnitIS> shall be described using <linesideElectronicUnitsIL>.

Documentation

Syntax

Autoexport from the XML-Schema for element IS:linesideElectronicUnitIS of railML® version 3.3      UML-visualization of IS
Documentation	Allows specifying a line side electronic unit that may be connected to signals, balise groups or singlular balised as well as euro loops.
Subschema	infrastructure
Parents*	linesideElectronicUnitsIS
Children	areaLocation (0..*), connectedToBalise (0..*), connectedToBaliseGroup (0..*), connectedToEuroloop (0..*), designator (0..*), elementState (0..*), gmlLocation (0..*), isValid (0..*), linearLocation (0..*), name (0..*), networkLocation (0..*), spotLocation (0..*), typeDesignator (0..*)
Attributes: id: the identifier of the object; this can be either of type xs:ID or UUID (obligatory; xs:ID); compare: Dev:Identities
*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.2 within the IS subschema. It is available only in railML^® 3.3. Do not hesitate to contact railML.org e.V. for further questions.

This element does not appear in railML^® 3.1 within the IS subschema. It is available only in railML^® 3.3. Do not hesitate to contact railML.org e.V. for further questions.

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.
Introduced with version 3.3.

Best Practice / Examples

Please see guide at Dev:Euroloop.