CO:trainType

From railML 3 Wiki
Jump to navigation Jump to search

Introduction

Documentation

Syntax

Autoexport from the XML-Schema for element CO:trainType of railML® version 3.2
Documentation a speedProfile can be linked with several train types
Subschema common
Parents* speedProfile
Children None
Attributes:
  • etcsTrainCategoryNumber: this information shall be derived from trainType, airBrakeApplicationPosition and maxCantDeficiency (optional; xs:integer; minInclusive: 0; maxInclusive: 15),

  • type: the operational type of train, e.g. passenger or freight (optional; xs:string; patterns: other:\w{2,})
Possible values:
  • all: use value 'all' to specify that the speed profile is valid for all types of train
  • freight
  • mixed: a mixed train includes passenger and freight waggons
  • passenger
  • tiltingPassenger: DEPRECATED; use tilting element instead,

  • cantDeficiency: DEPRECATED; use new speedProfile attribute maxCantDeficiency instead (optional; xs:integer; minInclusive: 80; maxInclusive: 300)
*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 CO:trainType of railML® version 3.1
Documentation Schema documentation missing!
Subschema common
Parents* speedProfile
Children None
Attributes:
  • etcsTrainCategoryNumber: Schema documentation missing! (optional; xs:integer; minInclusive: 0; maxInclusive: 15),

  • type: Schema documentation missing! (optional; xs:string)
Possible values:
  • freight
  • tiltingPassenger
  • passenger,

  • cantDeficiency: Schema documentation missing! (optional; xs:integer; minInclusive: 80; maxInclusive: 300)
*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