Dev:Railway station ownership

From railML 2 Wiki
Revision as of 14:28, 20 February 2024 by RailML Orga Ontology (talk | contribs) (fixed reference)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
2023-05-23 railML railway station's ownership representation in railML.gif

In this example, will consider a way to represent the fact “railway station X is located in country Y”

A 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 by two railway operation managers Správa železnic of the Czech Republic and Deutsche Bahn Netz of Germany. Schöna is a German railway station and Dolní Žleb is a Czech one. This example is based on Schöna.

In railML®, countries are present in the infrastructure manages code list. The fact “railway station X is located in country Y” should be decomposed into the following ones:

• railway station X has track Z

• track Z is managed by infrastructure manager J

• infrastructure manager J is of country Y.

The last fact is already present in the code list of railML®. The user should define the first two ones.

The “railway station X has track Z” fact is represented by <propEquipment> child of an ocp.

In railML®, “track Z is managed by infrastructure manager J” fact is represented by the <ownerChange> element of infrastructure subschema referring to <infrastructureManager> ones of metadata.

They affect the definition of the railway tracks. Every railway track should have an <ownerChange> at the beginning of the track positioned at zero coordinate. But also, the additional semantic constraints apply like for the <speedChange>:[1]

• Only applies if speedChanges (ownerChange) are exported at all [as they are not required by XSD (editor's comment)].

• If both directions are accessible, then <ownerChange> should also be defined for the <trackEnd>