RS:drivingResistance

From railML 3 Wiki
Revision as of 17:45, 30 October 2024 by RailML Bot XSD2MediaWiki (talk | contribs) (Created page RS:drivingResistance using XSD2MediaWiki Converter 1.1.1)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Introduction

Documentation

Syntax

Autoexport from the XML-Schema for element RS:drivingResistance of railML® version 3.3
    
Description refers to the sum of the resistance-s that a land vehicle must overcome with the help of a driving force in order to travel at a constant or accelerated speed on a horizontal or inclined path.
Subschema rollingstock
Parents*

vehicle

Children

info (0..1), details (0..1)

Attributes:
  • tunnelFactor: Because of the different aerodynamics in tunnels the train experiences a higher running resistance than on open air. This effect depends on e.g. the tunnel cross section and surface smoothness. This would require an indivdual value for each tunnel. In absence of the exact values the ones of similar tunnels are used. The given value is used as multiplier to increase the ordinary running resistance. (optional: xs:decimal : 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.


 

This element does not appear in railML® 3.2 within the RS subschema. It is available only in railML® 3.3. Do not hesitate to contact railML.org e.V. for further questions.

This element does not appear in railML® 3.1 within the RS subschema. It is available only in railML® 3.3. Do not hesitate to contact railML.org e.V. for further questions.


Changes 3.2→3.3

There exists an overview of all changes between railML® 3.2 and railML® 3.3 on page Dev:Changes/3.3.
Introduced with version 3.3.

Semantics

Best Practice / Examples

Additional Information

Notes

Open Issues