| [railVIVID 2.2.0 beta 1] checking semantic constraint IS:023 [message #4051] |
Wed, 17 June 2026 14:22  |
Mathias Vanden Auweele
Messages: 167 Registered: February 2025 Location: Brussels
|
Senior Member |
|
|
Hello,
I think there is an issue with the implementation of semantic constraint IS:023
Our railML files has this LPS:
<linearPositioningSystem id="_ips" startMeasure="0" endMeasure="-1" linearReferencingMethod="absolute" units="metres">
<name name="Intrinsic linear positioning system" language="en" description="This LPS is used for defining measuring tape distances on NetElements." />
<isValid from="2000-01-01" />
</linearPositioningSystem>
Note the endMeasure="-1".
All the linear coordinates that we use in our file that refer to this LPS, are marked as violating the IS:023 by railVIVID.
We have implemented based on the presentation given by Christian at the 46th conference where the internal positioning systems were introduced and more specifically on the slide with this title:
#541 Positioning approach (3/26)
Here's an extract of the slide:
Quote:
Intrinsic positioning system:
• This is a <linearPositioningSystem> with
• @startMeasure=0.0
• @endMeasure={infinity} → use value „-1" (because real pos values must not be negative)
• @units=metres
• @linearReferencingMethod=absolute
So we assume that "-1" is a valid value for "endMeasure" in our use case. Does railVIVID take this into account?
We notice that the wiki documentation doesn't show this -1. https://wiki3.railml.org/wiki/RTM:linearPositioningSystem
Which is probably the reason why this exception was not implemented in railVIVID.
If this -1 exception is still possible, I propose to implement it in railVIVID and make a note about this in the attribute on the wiki.
Thanks!
Mathias Vanden Auweele
Railway data freelancer
https://matdata.eu
Brussels, Belgium
|
|
|
|