Introduction
Documentation
Syntax
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:
- constructionType: construction type of over crossing: bridge or tunnel (obligatory;
xs:string; patterns: other:w{2,})
- Possible values:
- bridge
- tunnel
- movableBridge,
- belongsToParent: reference to a parent over crossing (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}}),
- 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,})
- 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
The children have changed.
The attributes have been changed.
Semantics
#255
Some basic modelling rules:
- It is possible to refer to an arbitrary number of "crossed elements" from one xCrossing
- the constructional realization (bridge or tunnel) of the xCrossing is implemented as attribute and shall not be included in the name of the functional infrastructure element
- 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 levelCrossing
Best Practice / Examples
https://www.railml.org/forum/index.php?t=msg&goto=3014&&srch=overcrossing#msg_3014
in railML 3 a railway track crossing another railway track via a bridge can be modelled using the elements <overcrossing> and <underCrossing>.
Assume that in the following example Track A passes over Track B (whereas A and B shall be the IDs of NetElements).
<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>
Best Practice / Examples
Additional Information
Notes
Open Issues
