| Re: [railML 3] Defining passing points for ATO data [message #3021 is a reply to message #2784] |
Tue, 14 June 2022 15:35  |
christian.rahmig
Messages: 436
Registered: January 2016
|
Senior Member |
|
|
Dear Thomas,
in railML 2.x passing points are modelled using <ocp> elements (operation control point). They can be placed anywhere on the track using a <crossSection> "anchor point" (see [1]).
In railML 3.x the functional infrastructure element <operationalPoint> fulfills a similar role like the <ocp> in railML 2. Therefore, I agree with your idea to use <operationalPoint> elements for passing points. As any functional infrastructure element the <operationalPoint> can be located within the topology using one of its possible <*location> child elements. In addition, you can link the <operationalPoint> with a specific infrastructure element (e.g. a signal or an axle counter) via the <opEquipment / ownsInfrastructureElement> child element.
From application point of view, it will be interesting to know the average distance between these passing points. Do you have any examples?
A lot has happened with the railML schema since your forum post (I apologize for the delayed reply...). The new version railML 3.2 that has been published end of April 2022 contains also a first version of the timetable schema. Did you have a look at this schema and find the link with infrastructure?
Thank you very much and best regards
Christian
Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
Members
Search
Help
Login
Home
