Dev:Border between infrastructure managers and countries: Difference between revisions
[checked revision] | [checked revision] |
No edit summary |
(improved example) |
||
Line 14: | Line 14: | ||
</metadata> | </metadata> | ||
.. | .. | ||
<trackBegin id="tb01" pos="0" absPos="0"> | <track id="tr01"> | ||
<ownerChange id="och01" pos="0" absPos="0" infrastructureManagerRef="ima01"/> | <trackTopology> | ||
.. | <trackBegin id="tb01" pos="0" absPos="0">..</trackBegin> | ||
< | <trackEnd id="te01" pos="500" absPos="500">..</trackEnd> | ||
.. | </trackTopology> | ||
< | <trackElements> | ||
<ownerChange id="och02" pos="0" absPos="500" infrastructureManagerRef=" | .. | ||
.. | <ownerChange id="och01" pos="0" absPos="0" infrastructureManagerRef="ima01"/> | ||
< | .. | ||
</trackElements> | |||
</track> | |||
<track id="tr02"> | |||
<trackTopology> | |||
<trackBegin id="tb02" pos="0" absPos="500">..</trackBegin> | |||
<trackEnd id="te02" pos="500" absPos="1000">..</trackEnd> | |||
</trackTopology> | |||
<trackElements> | |||
.. | |||
<ownerChange id="och02" pos="0" absPos="500" infrastructureManagerRef="ima02" name="Bahnverw.grenze Bad Schandau Gr"/> | |||
.. | |||
</trackElements> | |||
</track> | |||
</syntaxhighlight> | </syntaxhighlight> | ||
It is important to ensure the correct definition of the railway tracks. Every railway track should have an {{tag|IS|ownerChange}} at the beginning of the track positioned at a zero coordinate. Additional semantic constraints apply for the {{tag|IS|speedChange}} <ref>{{site|1=https://www.railml.org/forum/index.php?t=msg&th=905&start=0&|2=railML2 <speedChange> semantic constraints revision forum post}}</ref>. | It is important to ensure the correct definition of the railway tracks. Every railway track should have an {{tag|IS|ownerChange}} at the beginning of the track positioned at a zero coordinate. Additional semantic constraints apply for the {{tag|IS|speedChange}} <ref>{{site|1=https://www.railml.org/forum/index.php?t=msg&th=905&start=0&|2=railML2 <speedChange> semantic constraints revision forum post}}</ref>. | ||
== References == | == References == |
Revision as of 13:22, 5 December 2023
The overarching objective of the EU Directive 2012/34/EU is to establish a single European railway area. Contributing to this objective is the requirement for improved cooperation of infrastructure managers and ‘cross-border agreements’ to enable seamless operations for train paths crossing borders, or ‘handover points’ (defined in [1] as “the point where legal responsibility changes between the infrastructure managers”).
The photo shows an example of a ‘handover point’ at the Germany-Czech Republic border on the Děčín to Dresden-Neustadt 6240 railway line. This line is operated by two different rail operating companies, Správa železnic in the Czech Republic and Deutsche Bahn Netz in Germany, meaning there is a change in infrastructure managers.
In the source code, shown below, there are two tracks belonging to two infrastructure managers. Ownership is represented by <ownerChange> elements. Further information is given in the <infrastructureManager> element and corresponding code list (link to the railML® website).
<metadata> <organizationalUnits> <infrastructureManager id="ima01" code="DBN"/> <infrastructureManager id="ima02" code="SZD"/> </organizationalUnits> </metadata> .. <track id="tr01"> <trackTopology> <trackBegin id="tb01" pos="0" absPos="0">..</trackBegin> <trackEnd id="te01" pos="500" absPos="500">..</trackEnd> </trackTopology> <trackElements> .. <ownerChange id="och01" pos="0" absPos="0" infrastructureManagerRef="ima01"/> .. </trackElements> </track> <track id="tr02"> <trackTopology> <trackBegin id="tb02" pos="0" absPos="500">..</trackBegin> <trackEnd id="te02" pos="500" absPos="1000">..</trackEnd> </trackTopology> <trackElements> .. <ownerChange id="och02" pos="0" absPos="500" infrastructureManagerRef="ima02" name="Bahnverw.grenze Bad Schandau Gr"/> .. </trackElements> </track>
It is important to ensure the correct definition of the railway tracks. Every railway track should have an <ownerChange> at the beginning of the track positioned at a zero coordinate. Additional semantic constraints apply for the <speedChange> [2].