IS:energyPantograph

From railML 3 Wiki
Jump to navigation Jump to search

Introduction

Documentation

Syntax

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

child element summarizing the pantograph energy parameters

Subschema

infrastructure

Parents*
Children

None

Attributes:

  • compliantTSITypes: space separated list of accepted TSI compliant pantograph heads (optional; tTSIPantoHeadTypeList),

  • contactStripMaterials: space separated list of permitted contact strip materials (optional; tContactStripMaterialList),

  • nationalPanHeadTypes: space separated list of accepted other pantograph heads (optional; tPantoHeadTypeList),

  • requiresTSIcompliance: flag, whether a TSI complaint pantograph head is required (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:energyPantograph of railML® version 3.1
Documentation

child element summarizing the pantograph energy parameters

Subschema

infrastructure

Parents*
Children

None

Attributes:

  • requiresTSIcompliance: flag, whether a TSI complaint pantograph head is required (optional; xs:boolean),

  • compliantTSITypes: space separated list of accepted TSI compliant pantograph heads (optional; tTSIPantoHeadTypeList),

  • nationalPanHeadTypes: space separated list of accepted other pantograph heads (optional; tPantoHeadTypeList),

  • contactStripMaterials: space separated list of permitted contact strip materials (optional; tContactStripMaterialList)
*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