Home » railML newsgroups » railML.infrastructure » [railML3] Restricting IS:line and RTM:linearPositioningSystem (New semantic constraints suggested)
Re: [railML3] Restricting IS:line and RTM:linearPositioningSystem [message #3251 is a reply to message #3236] Thu, 13 June 2024 07:11 Go to previous messageGo to previous message
David Lichti is currently offline  David Lichti
Messages: 16
Registered: December 2020
Junior Member
I share Michael's concerns. As a data provider, we could only provide these values for the @startMeasure and @endMeasure attribute by calculating the minimum and maximum of all known linear positions associated to a linear positioning system.

This would not only be computationally quite expensive. The accuracy of these results would also depend on the available infrastructure data covering both end points of the linear positioning system. This is something we have no control over. In our (Hacon/TPS) infrastructure model, linear positioning systems are nothing but a label to specify linear positions. On data import, we do not use explicit value ranges. And on export, we cannot give any reliable and meaningful values.

I, therefore, suggest to make these two attributes optional. This would get around the need to update linear positioning system data when merging data from partial surveys at Bahnkonzept. And it would allow us to use the native linear positioning systems for the POMA use case.

Best regards

David

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [railML3] Need for modelling Euroloop
Next Topic: [railML3] Usage of //network/networkResource
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Jul 03 07:41:12 CEST 2024