IS:platformEdge

From railML 3 Wiki
Jump to navigation Jump to search

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 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. Do not hesitate to contact railML.org 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

#209 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.

Additional Information

Notes

Open Issues