Introduction
🗒️
|
This article uses the unit label meter.
As the reference for this wiki is British English, the correct label is metre.
Wherever the label meter occurs, it is meant equivalently to metre.
|
|
|
Documentation
Syntax
Autoexport from the XML-Schema for element Generic:load of railML ® version 3.3
|
Documentation
|
Collects requirements regarding the load of a vehicle belonging to the enclosing speed profile
|
Subschema
|
generic
|
Parents*
|
speedProfile
|
Children
|
exceedsOrEqualsAxleLoad (0..1)
|
Attributes:
- exceedsAxleLoadCategory: The enclosing element applies for trains exceeding the axle load category specified here. (optional;
xs:string ; patterns: other:w{2,})
- Possible values:
- A: axle load: 16.0 t, meter load: 5.0 t/m
- B1: axle load: 18.0 t, meter load: 5.0 t/m
- B2: axle load: 18.0 t, meter load: 6.4 t/m
- C2: axle load: 20.0 t, meter load: 6.4 t/m
- C3: axle load: 20.0 t, meter load: 7.2 t/m
- C4: axle load: 20.0 t, meter load: 8.0 t/m
- D2: axle load: 22.5 t, meter load: 6.4 t/m
- D3: axle load: 22.5 t, meter load: 7.2 t/m
- D4: axle load: 22.5 t, meter load: 8.0 t/m
- D4xL: only valid for locomotives
- E4: axle load: 25.0 t, meter load: 8.0 t/m
only valid for freight cars
- E5: axle load: 25.0 t, meter load: 8.8 t/m
only valid for freight cars,
- exceedsMeterLoad: The enclosing element applies for trains exceeding the meter load specified here. (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.
|
This element does not appear in railML® 3.2 within the Generic subschema. It is available only in railML® . Do not hesitate to contact railML.org for further questions.
This element does not appear in railML® 3.1 within the Generic subschema. It is available only in railML® . Do not hesitate to contact railML.org 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