IS:maxTrainCurrent

From railML 3 Wiki
Jump to navigation Jump to search

Introduction

Documentation

Syntax

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

maximum current that can be accessed in the described electrification section

Subschema

infrastructure

Parents*
Children

None

Attributes:

  • maxCurrent: maximum allowed current in Ampere (optional; xs:decimal),

  • operationType: type of operation for maximum train current: standstill or driving (optional; xs:int),

  • trainType: train category for which the maximum train current constraint is valid (optional; xs:string)
Possible values:
  • all
  • freight
  • highspeed
  • passenger,

  • validFor: application of maximum train current: train or pantograph (optional; xs:int)
*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:maxTrainCurrent of railML® version 3.1
Documentation

maximum current that can be accessed in the described electrification section

Subschema

infrastructure

Parents*
Children

None

Attributes:

  • maxCurrent: maximum allowed current in Ampere (optional; xs:decimal),

  • trainType: train category for which the maximum train current constraint is valid (optional; xs:string)
Possible values:
  • all
  • highspeed
  • freight
  • passenger,

  • operationType: type of operation for maximum train current: standstill or driving (optional; xs:int),

  • validFor: application of maximum train current: train or pantograph (optional; xs:int)
*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