|
Forum: railML.infrastructure
|
|
Topic: [railML3] Restricting IS:line and RTM:linearPositioningSystem
|
| Re: [railML3] Restricting IS:line and RTM:linearPositioningSystem [message #3236 is a reply to message #3231] |
Mon, 29 April 2024 16:24 |
Larissa Zhuchyi
Messages: 32
Registered: November 2022
|
Member |
|
|
The idea of IS:014 was to try to avoid postprocessing of split file when merging them together issued by either:
- multiple partial linear positioning systems in the merged file or
- one linear positioning system with multiple e.g. @endMeasure attributes.
From what I understand merging may happen even in your use case of surveys. As conceptually what you produce, partitioned files, can be considered as equivalent to split ones. Please correct me if I'm wrong.
How would you handle it if you made incremental surveys and the data would belong to the same railway line?
- introduce one linear positioning system with persistent identifier only in the first measurement trip and then replace @endMeasure every time new data come from the next measurement trip or
- introduce new linear positioning systems every time new data come. Then the railway line will be associated with more then one linear positioning systems.
Larissa Zhuchyi – Ontology Researcher
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
Members
Search
Help
Login
Home
