IS:linePerformance

From railML 3 Wiki
Jump to navigation Jump to search

Introduction

Documentation

Syntax

Autoexport from the XML-Schema for element IS:linePerformance of railML® version 3.2
Documentation child element summarizing the line performance parameters
Subschema infrastructure
Parents* line
Children allowedLoadingGauge (0..*), allowedWeight (0..*)
Attributes:
  • maxSpeed: maximum line speed in km/h (optional; xs:decimal),

  • maxTrainLength: maximum allowed length for trains that run on this line (optional; xs:decimal),

  • signalledBrakingDistance: This is usually the distance between
    the main signal and the matching distant signal. It is usually also
    referred to as the maximum braking distance of a train the lineside
    signaling is based on. (optional; xs:decimal),

  • usablePlatformLength: minimum platform length that is available in stations along that line (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:linePerformance of railML® version 3.1
Documentation child element summarizing the line performance parameters
Subschema infrastructure
Parents* line
Children allowedLoadingGauge (0..*), allowedWeight (0..*)
Attributes:
  • maxSpeed: maximum line speed in km/h (optional; xs:decimal),

  • maxTrainLength: maximum allowed length for trains that run on this line (optional; xs:decimal),

  • usablePlatformLength: minimum platform length that is available in stations along that line (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 children have changed.

The attributes have been changed.

Semantics

Best Practice / Examples

Additional Information

Notes

Open Issues