| Re: Use railML to model parts of a large network [message #3244 is a reply to message #3136] |
Mon, 13 May 2024 16:21   |
Larissa Zhuchyi
Messages: 38
Registered: November 2022
|
Member |
|
|
Dear all
The current intermediate result after half a year of the work on the "splitting" topic is a document describing all the requirements gathered from the infrastructure and interlocking working groups [1]. railML.org still follows the connector approach at the topology level [2, Figure 2 on page 6].
Please reply whether these meet your expectations so far and keep in mind that they are currently rather rough as are in the draft stage! The use case template is used not officially, only in illustrative purpose.
The document [1] consists of many pages therefore please see a short summary below.
NEST working group requested splitting network into railway lines.
ETCS working group requested splitting lines into line sections and stations.
SCTP working group requested splitting everywhere, but this is currently interpreted as splitting tracks into parts.
For all of these requests valid railML files (input -> split -> merged) are produced.
railML.org plans the further work as follows (phases may overlap):
- the review by users;
- producing description of best practices in wiki;
- elaboration of interlocking part e.g. handling routes.
See also related forum posts on restricting linearPositioningSystem [3] and aggregation principles [4] inspired by this "splitting" initiative! Hopefully this will give more context to them.
[1] https://cloud.railml.org/s/GddqjsSYoacY5ee
[2] https://cloud.railml.org/s/wFeHeFAgPEbwaRA
[3] https://www.railml.org/forum/index.php?t=msg&th=946& start=0&
[4] https://www.railml.org/forum/index.php?t=msg&th=948& start=0&
Sincerely,
Larissa Zhuchyi – Ontology Researcher
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
Members
Search
Help
Login
Home
