Introduction
Documentation
Syntax
Autoexport from the XML-Schema for element IS:length of railML ® version 3.2 |
| Documentation
|
length of the line (section)
|
| Subschema
|
infrastructure
|
| Parents*
|
line,
overCrossing,
platform,
platformEdge,
track,
underCrossing
|
| Children
|
None
|
Attributes:
- type: type of length (operational, physical, administrative...) (obligatory;
xs:string; patterns: other:w{2,})
- Possible values:
- operational: operational or administrative length value
- physical: physical length value,
- validForDirection: indicate the direction for which the length information applies (optional;
xs:string)
- Possible values:
- value: the distance value given in meters (obligatory;
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:length of railML ® version 3.1 |
| Documentation
|
length of the line (section)
|
| Subschema
|
infrastructure
|
| Parents*
|
line,
overCrossing,
platform,
track,
underCrossing
|
| Children
|
None
|
Attributes:
- value: the distance value given in meters (obligatory;
xs:decimal),
- type: type of length (operational, physical, administrative...) (obligatory;
xs:string; patterns: other:w{2,})
- Possible values:
- physical: physical length value
- operational: operational or administrative length value,
- validForDirection: indicate the direction for which the length information applies (optional;
xs:string)
- Possible values:
|
*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 parents have changed.
The attributes have been changed.
Semantics
Best Practice / Examples
Additional Information
Notes
Open Issues