| Re: [railML3.3] xs:choice between linearCoordinate and geometricCoordinate [message #3699 is a reply to message #3597] |
Fri, 22 August 2025 14:41   |
christian.rahmig
Messages: 532
Registered: January 2016
|
Senior Member |
|
|
Dear Mathias and Morten,
thank you for bringing up this topic and sorry for my late reply. I finally looked at the situation in schemas railML 3.2 and railML 3.3:
In 3.2 you can define both, a linearCoordinate and a geometricCoordinate for one spotLocation. In 3.3 you have to choose between them.
Well, both implementations are far away from being perfect. For example, you cannot model two linear coordinates (with different linear coordinate systems) for one spotLocation...
From my perspective, we have two possible solutions:
a) Allow for only one coordinate instance within one spotLocation element (which actually is the solution with railML 3.3)
b) Allow for multiple linear or geometric coordinate instances within one spotLocation
Of course, each solution need to be adapted to linearLocation and areaLocation accordingly to provide a consistent schema.
Dear beloved railML infrastructure community: which solution do you prefer?
As usual, any kind of feedback is highly appreciated...
Best regards
Christian
PS: Until this issue is solved, the way to model one infrastructure element location with several different coordinates, is to model several spotLocation child elements for this infrastructure element...
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
