IS:hasContactWire

From railML 3 Wiki
Jump to navigation Jump to search

Introduction

Documentation

Syntax

Autoexport from the XML-Schema for element IS:hasContactWire of railML® version 3.2
Documentation

child element summarizing the construction details of the contact wire

Subschema

infrastructure

Parents*
Children

None

Attributes:

  • maxDisplacement: maximum lateral displacement of the contact wire from centre of track including stagger and wind forces, in [m] (optional; xs:decimal),

  • maxHeight: maximum height of contact wire above top of rail, in [m] (optional; xs:decimal),

  • minHeight: minimum height of contact wire above top of rail, in [m] (optional; xs:decimal)
*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:hasContactWire of railML® version 3.1
Documentation

child element summarizing the construction details of the contact wire

Subschema

infrastructure

Parents*
Children

None

Attributes:

  • minHeight: minimum height of contact wire above top of rail, in [m] (optional; xs:decimal),

  • maxHeight: maximum height of contact wire above top of rail, in [m] (optional; xs:decimal),

  • maxDisplacement: maximum lateral displacement of the contact wire from centre of track including stagger and wind forces, in [m] (optional; xs:decimal)
*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.


 


Changes 3.1→3.2

The attributes have been changed.

Semantics

Best Practice / Examples

Additional Information

Notes

Open Issues