|
|
| (2 intermediate revisions by the same user not shown) |
| Line 13: |
Line 13: |
| Some basic modelling rules: | | Some basic modelling rules: |
|
| |
|
| - It is possible to refer to an arbitrary number of "crossed elements" from one xCrossing | | - It is possible to refer to an arbitrary number of {{IS:Tag|crossesElement}} 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 | | - the constructional realization (bridge or tunnel) of the xCrossing is implemented as attribute and shall not be included in the name of the {{IS:Tag|functionalInfrastructure}} |
|
| |
|
| - if "something" crosses under the railway track/line, it shall be named an underCrossing | | - if "something" crosses under the railway track/line, it shall be named an {{IS:Tag|underCrossing}} |
|
| |
|
| - if "something" crosses over the railway track/line, it shall be named an overCrossing | | - if "something" crosses over the railway track/line, it shall be named an {{IS:Tag|overCrossing}} |
|
| |
|
| - if "something" crosses the railway track/line at same level (usually only roads, streets and ways), it shall be named levelCrossing | | - if "something" crosses the railway track/line at same level (usually only roads, streets and ways), it shall be named {{IS:Tag|levelCrossingIS}} |
| {{importComment}} | | {{importComment}} |
|
| |
| {{semcon|should only have a {{tag|is|crossesElement}} child of type {{enum|railway}} child of type railway when railway crosses railway (not on the same level!).
| |
|
| |
| |status=proposed|proposed=2023-10-23
| |
| |id=IS:004}}
| |
|
| |
|
| {{importComment}} | | {{importComment}} |
| =={{examples}}== | | =={{examples}}== |
| [[File:Retford low-level station.jpg|thumb|500px|CC BY https://creativecommons.org/licenses/by/3.0/deed.de Rcsprinter123 https://commons.wikimedia.org/wiki/User:Rcsprinter123 https://commons.wikimedia.org/wiki/File:Overbridge_at_Retford_low-level_station.jpg ]] | | [[File:Retford low-level station.jpg|thumb|1000px|OverCrossing {{commons|Overbridge_at_Retford_low-level_station.jpg|Rcsprinter123 |CC|BY|3.0}}]] |
| | |
|
| |
|
|
| |
|
| in railML 3 a railway track crossing another railway track via a bridge can be modelled using the elements <overcrossing> and <underCrossing> <ref name=2bridge />. | | in railML3 a railway track crossing another railway track via a bridge can be modelled using the elements {{IS:Tag|overCrossing}} and {{IS:Tag|underCrossing}} <ref name=2bridge />. |
|
| |
|
| Assume that in the following example, as in the image on the right, Track A passes over Track B (whereas A and B shall be the IDs of NetElements). | | Assume that in the following example, as in the image on the right, Track A passes over Track B (whereas A and B shall be the IDs of {{IS:Tag|netElement}}). |
| <syntaxhighlight lang="xml"> | | <syntaxhighlight lang="xml"> |
| <overcrossing id="ocr1" constructionType="bridge"> | | <overcrossing id="ocr1" constructionType="bridge"> |
| Line 56: |
Line 50: |
| ==={{Notes}}=== | | ==={{Notes}}=== |
|
| |
|
| See photos in <crossesElement> for sharpening the conceptualization (understanding) of the definition of this element. | | See photos in {{IS:Tag|crossesElement}} for sharpening the conceptualization (understanding) of the definition of this element. |
|
| |
|
|
| |
|
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:
- 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,})
- 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,})
- 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
This section was requested by [tickets 1].
Some basic modelling rules:
- It is possible to refer to an arbitrary number of <crossesElement> 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 <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
in railML3 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 on the right, 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>
Additional Information
Notes
See photos in <crossesElement> for sharpening the conceptualization (understanding) of the definition of this element.
Open Issues
References
Affected Tickets
