| [railmML3] Handling multiple (geometric & linear) positioning systems [message #3756] |
Thu, 23 October 2025 09:35  |
Mathias Vanden Auweele
Messages: 90
Registered: February 2025
Location: Brussels
|
Member |
|
|
Hello all,
I need to work with multiple linear positioning systems (not including intrinsic) and geometric positioning systems (different EPSG).
railML3 currently doesn't allow me to put more than 1 <...Coordinate> in a <SpotLocation> or <AssociatedNetElement>. It doesn't allow me to combine a <GeometricCoordinate> and a <LinearCoordinate>, nor does it allow me to put 2 <...Coordinate> with a different @...PositioningSystemRef.
This leads to having multiple <SpotLocation> or <AssociatedNetElement> per <NetEntity> for the same @intrinsicCoordinate and @netElementRef, which seems very redundant.
From a conceptual modelling perspective, this is very strange. I understand a <SpotLocation> as a unique position on the topology, defined only by the @onElement, @intrinsicCoordinate and @applicationDirection attributes (and validity attributes). If two entities have the same values for these 3 attributes, we could infer that these are the same 1 entity.
Instead now, the <SpotLocation> is further also defined by the <...PositioningSystem> that is link to the <...Coordinate>. Wouldn't it make more sense, conceptually, to keep the identity of a <SpotLocation> free of it's link with a <...PositioningSystem>?
Mathias Vanden Auweele
Railway data freelancer
https://matdata.eu
Brussels, Belgium
|
|
|
|
|
|
Members
Search
Help
Login
Home
