Introduction
|
|
The platform edge, also known as the perron edge in Switzerland, is the edge of the platform from which passengers board and disembark a train. The platform edge is defined primarily as a structural boundary line. Platform edges have internationally defined heights to allow for the most efficient use of different train types, depending on their design.
Platform edges must maintain a sufficient distance from the track centerline to keep the clearance gauge clear. This so-called installation dimension depends on the platform height, the track superelevation, and the clearance gauge. In Germany, the installation dimension is approximately 1.65 m [1].
|
| Platform edge
|
|
| 🗒️
|
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 IS:platformEdge of railML ® version 3.3 |
| Documentation
|
A platform edge is the interface between passenger train and station. Platform edges are also modeled with the platform element.
|
| Subschema
|
infrastructure
|
| Parents*
|
platformEdges
|
| Children
|
areaLocation (0..*), designator (0..*), elementState (0..*), gmlLocation (0..*), isValid (0..*), length (0..*), linearLocation (0..*), name (0..*), networkLocation (0..*), spotLocation (0..*), typeDesignator (0..*)
|
Attributes:
- belongsToParent: reference to a parent platform edge,
use this attribute for grouping of platform edges with different parameters (e.g. different heights)
- if some information exists in parent and child, then information in child overwrites it in child
- if some information exists only in parent, then child inherits this information from parent (optional; xs:IDREF),
- belongsToPlatform: reference to a platform the edge belongs to (optional;
xs:IDREF),
- height: height of the platform edge in meters (optional;
xs:decimal),
- id: the identifier of the object; this can be either of type xs:ID or UUID (obligatory;
xs:ID); compare: Dev:Identities
|
*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:platformEdge of railML ® version 3.2 |
| Documentation
|
A platform edge is the interface between passenger train and station. Platform edges are also modeled with the platform element.
|
| Subschema
|
infrastructure
|
| Parents*
|
platformEdges
|
| Children
|
areaLocation (0..*), designator (0..*), external (0..*), gmlLocations (0..*), isValid (0..*), length (0..*), linearLocation (0..*), name (0..*), networkLocation (0..*), spotLocation (0..*), typeDesignator (0..*)
|
Attributes:
- belongsToParent: reference to a parent platform edge,
use this attribute for grouping of platform edges with different parameters (e.g. different heights)
- if some information exists in parent and child, then information in child overwrites it in child
- if some information exists only in parent, then child inherits this information from parent (optional; xs:string; patterns: (urn:uuid:)?[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}|{[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}}),
- belongsToPlatform: reference to a platform the edge belongs to (optional;
xs:string; patterns: (urn:uuid:)?[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}|{[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}}),
- height: height of the platform edge in meters (optional;
xs:decimal),
- id: the identifier of the object; this can be either of type xs:ID or UUID (obligatory;
xs:string; patterns: (urn:uuid:)?[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}|{[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}}); compare: Dev:Identities
|
*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.1 within the IS subschema. It is available only in railML® 3.2, 3.3. Do not hesitate to contact railML.org e.V. for further questions.
Changes 3.1→3.2
There exists an overview of all changes between railML® 3.1 and railML® 3.2 on page Dev:Changes/3.2.
Introduced with version 3.2.
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.
The children have been changed.
The attributes have been changed.
Semantics
Best Practice / Examples
The @belongsToParent is only used for grouping <platformEdge>s "in sequence" e.g. <platformEdge>s with different heights that still form one physical <platformEdge>. The grouping of <platformEdge>s at one <platform> is possible with @belongsToPlatform. For example, the Lansdowne station (MBTA) (
) in 2011 had two platform heights (external link): low-level for most cars and a full-height platform to accommodate passengers in wheelchairs[2].
|
|
| Grouping of platform edges
|
<platformEdge id="platformEdge1">
<linearLocation id=“pep01_lloc01" applicationDirection="both">
<associatedNetElement netElementRef="x0.4">
<linearCoordinateBegin positioningSystemRef="lps01" measure="100"/>
<linearCoordinateEnd positioningSystemRef="lps01" measure ="200"/>
</associatedNetElement>
</linearLocation>
</platformEdge>
<platformEdge id="platformEdgeChild2" belongsToParent="platformEdge1" >
<linearLocation id=“pep01_lloc01" applicationDirection="both">
<associatedNetElement netElementRef="x0.4">
<linearCoordinateBegin positioningSystemRef="lps01" measure="100"/>
<linearCoordinateEnd positioningSystemRef="lps01" measure ="150"/>
</associatedNetElement>
</linearLocation>
</platformEdge>
<platformEdge id="platformEdgeChild3" belongsToParent="platformEdge1" >
<linearLocation id=“pep01_lloc01" applicationDirection="both">
<associatedNetElement netElementRef="x0.4">
<linearCoordinateBegin positioningSystemRef="lps01" measure="150"/>
<linearCoordinateEnd positioningSystemRef="lps01" measure ="200"/>
</associatedNetElement>
</linearLocation>
</platformEdge>
Additional Information
Notes
Additional Information
| 🗒️
|
This segment provides background information that is not relevant for the certification process.
|
|
|
Source of best practice is issue #209.
Open Issues
References
