Introduce <platformEdge>
Description
Discussions in the railML use case developer groups have shown that there is a need to clearly distinguish between platforms and platform edges. The railML 3.1 solution (using for both types of objects) is not sufficient for all use cases / scenarios.
Background
In railML 2.x, the element <platformEdge>
exists. There is no element for platforms (owning platform edges). In railML 3.x both functional elements shall be modelled.
Links
- Forum discussion:
- Thomas Nygreen, 08.02.2019: [https://www.railml.org/forum/index.php?t=msg&th=650&goto=2133&#msg_2133]
- Trac ticket:
- Wiki documentation:
- IS:platform: [https://wiki3.railml.org/wiki/IS:platform]
- IS:platformEdge: [https://wiki3.railml.org/wiki/IS:platformEdge]
Proposed solution railML 3.2
Introduce new functional infrastructure element <platformEdge>
(derived from FunctionalInfrastructureEntity) with attributes / child elements:
-
@belongsToParent
to reference a parent platform edge (useful for grouping platform edges with different features) -
@belongsToPlatform
to reference the platform where the platform edge belongs to. -
@height
to define the height of the platform edge in meters. -
<length>
to define the length of the platform edge in meters.
In parallel, the element <platform>
needs to be adapted:
- deprecate
@height
(as this is only relevant for platform edges) - deprecate
<length>
(as this is only relevant for platform edges)