IS:levelCrossingIS

From railML 3 Wiki
Jump to navigation Jump to search
Rockport_Line () train passing level crossing in Canada

Introduction

A <levelCrossingIS> is an at grade intersection of a railway <line> with a road, a motorway, a footway etc [1].

The crossing of a railway <line> with a a river, a lake, a city etc. at different levels (bridge / tunnel) is called an <overCrossing> or <underCrossing>.

<levelCrossingIS> has its Interlocking counterpart <levelCrossingIL>. Interlocking properties of <levelCrossingIS> shall be described using <levelCrossingIL>.


🗒️ 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:levelCrossingIS of railML® version 3.3
    
Description intersections where a railway line crosses a road or a path at the same level
Subschema infrastructure
Parents*

levelCrossingsIS

Children**

name (0..*), isValid (0..*), areaLocation (0..*), linearLocation (0..*), spotLocation (0..*), gmlLocation (0..*), networkLocation (0..*), designator (0..*), typeDesignator (0..*), elementState (0..*), crossesElement (0..*), etcsLevelCrossing (0..1), linkedSpeedSection (0..*), protection (0..1)

Attributes:
  • activation: describes how the level crossing is being activated;
    missing attribute means that the information is not known (optional: tLevelCrossingActivation : xs:string)
Possible values:
  • infrastructureAutomatic: level crossing is activated automatically from infrastructure side (e.g. via activating rail detector)
  • infrastructureManual: level crossing is activated manually from infrastructure side (e.g. by a dispatcher)
  • none: there is no activation of the level crossing protection
  • trainAutomatic: level crossing is activated automatically from train side
  • trainManual: level crossing is activated manually from train side (action of train driver required),

  • belongsToParent: reference to the (one and only) parent level crossing

    - 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: tRef : xs:IDREF): compare: Dev:On the differences between belongsToParent and basedOnTemplate,

  • lengthOfStoppingAreaBeforeLevelCrossing: distance between the stopping point in front of a level crossing and the level crossing itself, in meters (optional: tLengthM : xs:decimal),

  • obstacleDetection: obstacle detection: automatic (technical system, e.g. radar) or manual (e.g. by operator);
    missing attribute means that the information is not known (optional: tLevelCrossingObstacleDetection : xs:string)
Possible values:
  • automatic: obstacle detection in level crossing danger area is done automatically (e.g. via radar)
  • manual: obstacle detection in level crossing danger area is done manually (e.g. via dispatcher looking)
  • none: there is no obstacle detection taking place in the level crossing danger area,

  • opensOnDemand: set TRUE if the level crossing is closed for road users by default and gates are only opened on demand;
    missing attribute means that the information is not known (optional: xs:boolean : xs:boolean),

  • supervision: describes how the state of the level crossing is being supervised;
    missing attribute means that the information is not known (optional: tLevelCrossingSupervision : xs:string)
Possible values:
  • infrastructureAutomatic: level crossing is supervised automatically from infrastructure side (e.g. via camera)
  • infrastructureManual: level crossing is supervised manually from infrastructure side (e.g. by dispatcher looking)
  • none: the level crossing is not supervised
  • trainManual: level crossing is supervised manually from train side (by train driver),

  • id: the file-internal ID of the object (obligatory: tID : 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.
**Notice:
To learn, how to interpret multiplicity information like (0..*) go to The W3C Recommendation on XML Schema

 

Autoexport from the XML-Schema for element IS:levelCrossingIS of railML® version 3.2
    
Description Allows specifying intersections where a railway line crosses a road or a path at the same level
Subschema infrastructure
Parents*

levelCrossingsIS

Children**

name (0..*), isValid (0..*), areaLocation (0..*), linearLocation (0..*), spotLocation (0..*), gmlLocations (0..*), networkLocation (0..*), designator (0..*), external (0..*), typeDesignator (0..*), crossesElement (0..*), etcsLevelCrossing (0..1), linkedSpeedSection (0..*), protection (0..1)

Attributes:
  • activation: describes how the level crossing is being activated;
    missing attribute means that the information is not known (optional: tLevelCrossingActivation : xs:string)
Possible values:
  • infrastructureAutomatic: level crossing is activated automatically from infrastructure side (e.g. via activating rail detector)
  • infrastructureManual: level crossing is activated manually from infrastructure side (e.g. by a dispatcher)
  • none: there is no activation of the level crossing protection
  • trainAutomatic: level crossing is activated automatically from train side
  • trainManual: level crossing is activated manually from train side (action of train driver required),

  • belongsToParent: reference to the (one and only) parent level crossing

    - 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: tRef : 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:On the differences between belongsToParent and basedOnTemplate,

  • lengthOfStoppingAreaBeforeLevelCrossing: distance between the stopping point in front of a level crossing and the level crossing itself, in meters (optional: tLengthM : xs:decimal),

  • obstacleDetection: obstacle detection: automatic (technical system, e.g. radar) or manual (e.g. by operator);
    missing attribute means that the information is not known (optional: tLevelCrossingObstacleDetection : xs:string)
Possible values:
  • automatic: obstacle detection in level crossing danger area is done automatically (e.g. via radar)
  • manual: obstacle detection in level crossing danger area is done manually (e.g. via dispatcher looking)
  • none: there is no obstacle detection taking place in the level crossing danger area,

  • opensOnDemand: set TRUE if the level crossing is closed for road users by default and gates are only opened on demand;
    missing attribute means that the information is not known (optional: xs:boolean : xs:boolean),

  • supervision: describes how the state of the level crossing is being supervised;
    missing attribute means that the information is not known (optional: tLevelCrossingSupervision : xs:string)
Possible values:
  • infrastructureAutomatic: level crossing is supervised automatically from infrastructure side (e.g. via camera)
  • infrastructureManual: level crossing is supervised manually from infrastructure side (e.g. by dispatcher looking)
  • none: the level crossing is not supervised
  • trainManual: level crossing is supervised manually from train side (by train driver),

  • id: the identifier of the object; this can be either of type xs:ID or UUID (obligatory: tID : 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.
**Notice:
To learn, how to interpret multiplicity information like (0..*) go to The W3C Recommendation on XML Schema

 

Autoexport from the XML-Schema for element IS:levelCrossingIS of railML® version 3.1
    
Description This element is not documented in the schema!
Subschema infrastructure
Parents*

levelCrossingsIS

Children**

name (0..*), isValid (0..*), areaLocation (0..*), linearLocation (0..*), spotLocation (0..*), gmlLocations (0..*), networkLocation (0..*), designator (0..*), external (0..*), crossesElement (0..*), protection (0..1), any (0..*)

Attributes:
  • obstacleDetection: obstacle detection: automatic (technical system, e.g. radar) or manual (e.g. by operator);
    missing attribute means that the information is not known (optional: tLevelCrossingObstacleDetection : xs:string)
Possible values:
  • none: there is no obstacle detection taking place in the level crossing danger area
  • manual: obstacle detection in level crossing danger area is done manually (e.g. via dispatcher looking)
  • automatic: obstacle detection in level crossing danger area is done automatically (e.g. via radar),

  • opensOnDemand: set TRUE if the level crossing is closed for road users by default and gates are only opened on demand;
    missing attribute means that the information is not known (optional: xs:boolean : xs:boolean),

  • activation: describes how the level crossing is being activated;
    missing attribute means that the information is not known (optional: tLevelCrossingActivation : xs:string)
Possible values:
  • trainAutomatic: level crossing is activated automatically from train side
  • trainManual: level crossing is activated manually from train side (action of train driver required)
  • infrastructureAutomatic: level crossing is activated automatically from infrastructure side (e.g. via activating rail detector)
  • infrastructureManual: level crossing is activated manually from infrastructure side (e.g. by a dispatcher)
  • none: there is no activation of the level crossing protection,

  • supervision: describes how the state of the level crossing is being supervised;
    missing attribute means that the information is not known (optional: tLevelCrossingSupervision : xs:string)
Possible values:
  • trainManual: level crossing is supervised manually from train side (by train driver)
  • infrastructureManual: level crossing is supervised manually from infrastructure side (e.g. by dispatcher looking)
  • infrastructureAutomatic: level crossing is supervised automatically from infrastructure side (e.g. via camera)
  • none: the level crossing is not supervised,

  • id: the identifier of the object; this can be either of type xs:ID or UUID (obligatory: tID : xs:ID: 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.
**Notice:
To learn, how to interpret multiplicity information like (0..*) go to The W3C Recommendation on XML Schema

 


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.

The element documentation has been changed.

The children have been changed.

The attributes have been changed.

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 element documentation has been changed.

The children have been changed.

The attributes have been changed.

Semantics

Best Practice / Examples

Please see IS:roadSideBarriers for an example.

Additional Information

Notes

Open Issues

References

  1. ↑ https://de.wikipedia.org/wiki/Bahn%C3%BCbergang
Retrieved from "https://wiki3.railml.org/index.php?title=IS:levelCrossingIS&oldid=17302"