Dev:Border between infrastructure managers and countries: Difference between revisions
[checked revision] | [checked revision] |
m (typo) |
m (typo) |
||
Line 5: | Line 5: | ||
Real world example of this concept can be found in the OpenRailwayPap defined for the Děčín–Dresden-Neustadt railway 6240 line. This line is operated be two railway operation managers Správa železnic of Czech Republic and Deutsche Bahn Netz of Germany. Schöna is a German railway station and Dolní Žleb is a Czech one. | Real world example of this concept can be found in the OpenRailwayPap defined for the Děčín–Dresden-Neustadt railway 6240 line. This line is operated be two railway operation managers Správa železnic of Czech Republic and Deutsche Bahn Netz of Germany. Schöna is a German railway station and Dolní Žleb is a Czech one. | ||
In railML handover points are represented by the {{site|1=https://wiki2.railml.org/wiki/IS:ownerChange|2=<ownerChange>}} element. As handover points represent the change of “Ims” {{site|1=https://wiki2.railml.org/wiki/IS:ownerChange|2=<ownerChange>}} elements of infrastructure subschema refer to <infrastructureManager> ones of metadata. | In railML handover points are represented by the {{site|1=https://wiki2.railml.org/wiki/IS:ownerChange|2=<ownerChange>}} element. As handover points represent the change of “Ims” {{site|1=https://wiki2.railml.org/wiki/IS:ownerChange|2=<ownerChange>}} elements of infrastructure subschema refer to {{site|1=https://wiki2.railml.org/wiki/IS:infrastructureManager|2=<infrastructureManager>}} ones of metadata. | ||
They affect the definition of the railway tracks. Every railway track should have an {{site|1=https://wiki2.railml.org/wiki/IS:ownerChange|2=<ownerChange>}} at the beginning of the track positioned at zero coordinate. But also, the additional semantic constraints apply like for the <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>: | They affect the definition of the railway tracks. Every railway track should have an {{site|1=https://wiki2.railml.org/wiki/IS:ownerChange|2=<ownerChange>}} at the beginning of the track positioned at zero coordinate. But also, the additional semantic constraints apply like for the <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>: |
Revision as of 17:56, 29 September 2023
In this example we will consider handover point as it is defined in [1]: “Point where legal responsibility changes between the Ims. This can be but does not have to be in conjunction with a state border”.
Real world example of this concept can be found in the OpenRailwayPap defined for the Děčín–Dresden-Neustadt railway 6240 line. This line is operated be two railway operation managers Správa železnic of Czech Republic and Deutsche Bahn Netz of Germany. Schöna is a German railway station and Dolní Žleb is a Czech one.
In railML handover points are represented by the <ownerChange> (link to the railML® website) element. As handover points represent the change of “Ims” <ownerChange> (link to the railML® website) elements of infrastructure subschema refer to <infrastructureManager> (link to the railML® website) ones of metadata.
They affect the definition of the railway tracks. Every railway track should have an <ownerChange> (link to the railML® website) at the beginning of the track positioned at zero coordinate. But also, the additional semantic constraints apply like for the <speedChange> [2]:
• Only applies if speedChanges (ownerChange) are exported at all [as they are not required by XSD];
• If both directions are accessible, then <ownerChange> (link to the railML® website) should also be defined for the <trackEnd> (link to the railML® website).
- ↑ unknown: TAP TSI and TAF TSI Sector Handbook for the Communication between Railway Undertakings and Infrastructure Managers (RU/IM Telematics Sector Handbook) Submitted on 20th October 2022
- ↑ railML2 <speedChange> semantic constraints revision forum post (link to the railML® website)