Re: [railML3] Positioning approach [message #3160 is a reply to message #3159] |
Wed, 08 November 2023 06:46 |
christian.rahmig
Messages: 465 Registered: January 2016
|
Senior Member |
|
|
Dear Thomas,
thank you for your feedback and input to complete the refactoring of the locations. Yes, we still have to talk about the linearCoordinate and geometricCoordinate children of linearLocation and areaLocation, which result from the RTM modelling.
If you want to model a (linear or area) location with reference to the topology layer (netElements...), you have to do it using associatedNetElement and relevant child elements and attributes. So, the remaining question is if we should allow for linearLocation or areaLocation without reference to the topology? Btw: a spotLocation is always linked with the topology...
So, in order to harmonize the approach with spotLocation, I agree with your suggestion to deprecate linearCoordinate and geometricCoordinate in linearLocation and areaLocation. And if someone really needs to define a location without a reference to the topology, he or she may still make use of the gmlLocations and its child elements lineString and point.
Question to the community:
Who is using the child elements linearCoordinate and geometricCoordinate in elements linearLocation and areaLocation?
Any feedback is highly appreciated...
Best regards
Christian
Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|