| [railML3.3] xs:choice between linearCoordinate and geometricCoordinate [message #3596] |
Mon, 28 April 2025 11:14  |
Mathias Vanden Auweele
Messages: 40
Registered: February 2025
Location: Brussels
|
Member |
|
|
Hello all,
Since v3.3, a SpotLocation or LinearLocation can only contain LinearCoordinates or GeometricCoordinates.
This means that if we want to supply both LinearCoordinates and GeometricCoordinates for a NetEntity, we'll need to create 2 SpotLocations with the same IntrinsicCoordinate and other attributes. This effectively changes the conceptual meaning of SpotLocation to one that is specifically tied to a PositioningSystem.
What was the reason for this chance?
This seems wasteful and a possible source for mistakes. Can we roll this back in the next version (or preferably, even doing a bugfix on the 3.3 version)?
Mathias Vanden Auweele
Railway data freelancer
https://matdata.eu
Brussels, Belgium
[Updated on: Mon, 28 April 2025 11:16] Report message to a moderator |
|
|
|
| Re: [railML3.3] xs:choice between linearCoordinate and geometricCoordinate [message #3597 is a reply to message #3596] |
Mon, 28 April 2025 13:41  |
Morten Torstensen
Messages: 4
Registered: October 2023
Location: Oslo, Norway
|
Junior Member |
|
|
A spotLocation is a single spot that can be referred to using many different coordinate systems. As you can have many geometric positioning systems and many linear positioning systems, you should be able to model it in the same spotLocation.
I am not sure what the reasoning was to only allow a single positioning element for a spotLocation? Happy to be enlightened.
Morten Torstensen
Bane NOR - Norwegian Infrastructure Manager
Digital Information Model for railway infrastructure
Ontology, modeling, mapping
|
|
|
|
Members
Search
Help
Login
Home
