Introduction
Overcrossing where road bridge crosses over the railway line at Station Dudzele (
🇳🇱)
Documentation
Syntax
Autoexport from the XML-Schema for element IS:overCrossing of railML ® version 3.3 |
| Documentation
|
An over crossing describes a crossing, where something crosses over the railway line. From constructional point of view an over crossing can be a bridge or a tunnel.
|
| Subschema
|
infrastructure
|
| Parents*
|
overCrossings
|
| Children
|
allowedLoadingGauge (0..*), areaLocation (0..*), crossesElement (0..*), designator (0..*), elementState (0..*), gmlLocation (0..*), isValid (0..*), length (0..*), linearLocation (0..*), name (0..*), networkLocation (0..*), spotLocation (0..*), tunnelResistance (0..1), typeDesignator (0..*)
|
Attributes:
- belongsToParent: reference to a parent over 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; xs:IDREF),
- constructionType: construction type of over crossing: bridge or tunnel (obligatory;
xs:string; patterns: other:w{2,}; consider Use of tOtherEnumerationValue too.)
- Possible values:
- bridge: a structure built to span a physical obstacle (such as a body of water, valley, road, or railway) without blocking the way underneath [wikipedia].
- tunnel: underground passageway, dug through surrounding soil, earth or rock, and enclosed except for the entrance and exit, commonly at each end [wikipedia].
- movableBridge: A special movable bridge (undercrossing) which is used for railway traffic passing a waterway underneath the railway line in normal position but allows for temporarily being moved out of the way of the vessels. It is then not passable by trains.
The normal position is locked and supervised by interlocking system. The other control of the bridge is outside the interlocking system.,
- verbalConstraint: verbal formulation for any kind of further constraint that applies for using the overCrossing or underCrossing (optional;
xs:string),
- 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:overCrossing of railML ® version 3.2 |
| Documentation
|
An over crossing describes a crossing, where something crosses over the railway line. From constructional point of view an over crossing can be a bridge or a tunnel.
|
| Subschema
|
infrastructure
|
| Parents*
|
overCrossings
|
| Children
|
allowedLoadingGauge (0..*), areaLocation (0..*), crossesElement (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 over 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; 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}}),
- constructionType: construction type of over crossing: bridge or tunnel (obligatory;
xs:string; patterns: other:w{2,}; consider Use of tOtherEnumerationValue too.)
- Possible values:
- bridge: a structure built to span a physical obstacle (such as a body of water, valley, road, or railway) without blocking the way underneath [wikipedia].
- tunnel: underground passageway, dug through surrounding soil, earth or rock, and enclosed except for the entrance and exit, commonly at each end [wikipedia].
- movableBridge: A special movable bridge (undercrossing) which is used for railway traffic passing a waterway underneath the railway line in normal position but allows for temporarily being moved out of the way of the vessels. It is then not passable by trains.
The normal position is locked and supervised by interlocking system. The other control of the bridge is outside the interlocking system.,
- verbalConstraint: verbal formulation for any kind of further constraint that applies for using the overCrossing or underCrossing (optional;
xs:string),
- 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.
|
Autoexport from the XML-Schema for element IS:overCrossing of railML ® version 3.1 |
| Documentation
|
An over crossing describes a crossing, where something crosses over the railway line. From constructional point of view an over crossing can be a bridge or a tunnel.
|
| Subschema
|
infrastructure
|
| Parents*
|
overCrossings
|
| Children
|
allowedLoadingGauge (0..*), any (0..*), areaLocation (0..*), crossesElement (0..*), designator (0..*), external (0..*), gmlLocations (0..*), isValid (0..*), length (0..*), linearLocation (0..*), name (0..*), networkLocation (0..*), spotLocation (0..*)
|
Attributes:
- constructionType: construction type of over crossing: bridge or tunnel (obligatory;
xs:string; patterns: other:w{2,}; consider Use of tOtherEnumerationValue too.)
- Possible values:
- belongsToParent: reference to a parent over crossing (optional;
xs:IDREF; 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}}),
- verbalConstraint: verbal formulation for any kind of further constraint that applies for using the overCrossing or underCrossing (optional;
xs:string),
- id: the identifier of the object; this can be either of type xs:ID or UUID (obligatory;
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.
|
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 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 children have been changed.
The attributes have been changed.
Semantics
Some basic modelling rules:
- It is possible to refer to an arbitrary number of <crossesElement> from one xCrossing (link to the railML® website)
- the constructional realization (bridge or tunnel) of the xCrossing is implemented as attribute and shall not be included in the name of the <functionalInfrastructure>
- if "something" crosses under the railway track/line, it shall be named an <underCrossing>
- if "something" crosses over the railway track/line, it shall be named an <overCrossing>
- if "something" crosses the railway track/line at same level (usually only roads, streets and ways), it shall be named <levelCrossingIS>
Best Practice / Examples
General approach
in railML® 3 a railway <track> crossing another railway <track> via a bridge can be modelled using the elements <overCrossing> and <underCrossing> [1].
Assume that in the following example, as in the image above, <track> A passes over <track> B (whereas A and B shall be the IDs of <netElement>).
<overcrossing id="ocr1" constructionType="bridge">
<spotLocation netElementRef="B" ... />
<crossesElement type="railway" ref="A" ... />
</overcrossing>
...
<underCrossing id="ucr1" constructionType="bridge">
<spotLocation netElementRef="A" ... />
<crossesElement type="railway" ref="B" ... />
</underCrossing>
Tunnel on a double-track line
- Preferred, alternalive and invalid ways of modeling overCrossing
Alternative option: areaLocation per collection of unconnected netElements
Invalid code: linearLocation per collection of unconnected netElements
double <track> <line> consists of two <tracks>. On Micro level of <topology> they are represented using two <netElements>. In the example they are x0.4 and x0.5. On the Meso <level> these two <tracks> are represented using still two another <netElements>. They are x1.4 and x1.05. x1.4 aggregates x0.4. x1.5 aggregates x0.5. On the Macro <level> of aggregation two <netElements> x1.4 and x1.5 representing double <track> <line> are aggregated into one <netElement> x2.2.
tunnel can be located on all the <level>s of aggregation. <linearLocation> element shall be given per <level> of aggregation and per unconnected <netElement>, i.e. lc01_lloc01 , lc01_lloc02 and lc01_lloc03. <linearCoordinateBegin> and <linearCoordinateEnd> are the same for all <level>s of aggregation.
Additional Information
Notes
See photos in <crossesElement> for sharpening the conceptualization (understanding) of the definition of this element.
Additional Information
| 🗒️
|
This segment provides background information that is not relevant for the certification process.
|
|
|
Semantics section was requested by [tickets 1].
Examples were reviewed by the coordinator (link to the railML® website) of the Infrastructure subschema on 2025-11-11.
Open Issues
References
Affected Tickets
