| UC NEST Positioning approach for lineSegment with 2 or more tracks [message #3635] |
Wed, 28 May 2025 14:49  |
Jim Kjellberg
Messages: 12 Registered: January 2025
|
Junior Member |
|
|
Hello RailML Forum.
I need some advice regarding positioning approach of a <line> of type lineSegment with multiple tracks in UC:NEST
When referencing all microscopic net elements on the line segment I get the following result.
<line id="line1">
<name name="Example Line/>
<linearLocation id="linLoc_1" applicationDirection="both">
<associatedNetElement netElementRef="ne1" intrinsicCoordBegin="0" intrinsicCoordEnd="1" sequence="1">
<linearCoordinateBegin positioningSystemRef="lps_1" measure="0" />
<linearCoordinateEnd positioningSystemRef="lps_1" measure="1000" />
</associatedNetElement>
<associatedNetElement netElementRef="ne2" intrinsicCoordBegin="0" intrinsicCoordEnd="1" sequence="2">
<linearCoordinateBegin positioningSystemRef="lps_1" measure="0" />
<linearCoordinateEnd positioningSystemRef="lps_1" measure="1000" />
</associatedNetElement>
</linearLocation>
</line>
This is referencing both microscopic net elements on the same line segment between two stations
As I have understood this would not be 100% correct for a linearLocation as the associatedNetElement with sequence 2 has the same meassure as sequence 1, as it is a parallel track
In my topology I also have a mesoscopic netElement representing the 2 microscopic net elements
<netElement id="ne1_2me" length="1000">
<elementCollectionUnordered id="nc1_2me">
<elementPart ref="ne1" />
<elementPart ref="ne2" />
</elementCollectionUnordered>
<associatedPositioningSystem id="aps1" positioningSystemRef="lps_1">
<intrinsicCoordinate id="ic1" intrinsicCoord="0">
<linearCoordinate positioningSystemRef="lps_1" measure="0" />
</intrinsicCoordinate>
<intrinsicCoordinate id="ic2" intrinsicCoord="1">
<linearCoordinate positioningSystemRef="lps_1" measure="1000" />
</intrinsicCoordinate>
</associatedPositioningSystem>
</netElement>
Would this mesoscoping netElement be considered a linear net element or a non linear net element?
I think its considered a linear netElement as it simply allows travel between station A and station B on one of the tracks, but I am not sure if this is enough to be considered a linear mesoscopic net element.
If referencing to it, should I use linearLocation and intrinsic coordinate begin = 0 and intrinsic coordinate end = 1
or
Should I use Line.SpotLocation and intrinsic coordinate = 0?
Another option perhaps would be Line.AreaLocation referencing both microscopic netElements?
With Kind Regards
Jim Kjellberg
Trafikverket
|
|
|
|
| Re: UC NEST Positioning approach for lineSegment with 2 or more tracks [message #3636 is a reply to message #3635] |
Wed, 28 May 2025 20:52   |
Mathias Vanden Auweele
Messages: 180 Registered: February 2025 Location: Brussels
|
Senior Member |
|
|
Hello Jim,
Quote:As I have understood this would not be 100% correct for a linearLocation as the associatedNetElement with sequence 2 has the same meassure as sequence 1, as it is a parallel track
That is correct. If ne1 and ne2 are parallel NetElements and not sequencial, then you shouldn't be using a LinearLocation for defining the line entity. You should be using two LinearLocations or two AreaLocations. So something like this:
<line id="line1">
<name name="Example Line/>
<linearLocation id="linLoc_1" applicationDirection="both">
<associatedNetElement netElementRef="ne1" intrinsicCoordBegin="0" intrinsicCoordEnd="1" sequence="1">
<linearCoordinateBegin positioningSystemRef="lps_1" measure="0" />
<linearCoordinateEnd positioningSystemRef="lps_1" measure="1000" />
</associatedNetElement>
</linearLocation>
<linearLocation id="linLoc_2" applicationDirection="both">
<associatedNetElement netElementRef="ne2" intrinsicCoordBegin="0" intrinsicCoordEnd="1" sequence="1">
<linearCoordinateBegin positioningSystemRef="lps_1" measure="0" />
<linearCoordinateEnd positioningSystemRef="lps_1" measure="1000" />
</associatedNetElement>
</linearLocation>
</line>
Although I think an AreaLocation would make more sense for a definition of a line, since it's very likely that both NetElements are coupled together by connecting tracks and ordering the NetElements might not make a lot of sense.
LinearLocations are always sequential ordering of NetElements. Here's a good explanation: https://wiki.railtopomodel.org/index.php?title=Object_positi oning_in_the_network
Mathias Vanden Auweele
Railway data freelancer
https://matdata.eu
Brussels, Belgium
|
|
|
|
| Re: UC NEST Positioning approach for lineSegment with 2 or more tracks [message #3637 is a reply to message #3636] |
Wed, 28 May 2025 21:07   |
Mathias Vanden Auweele
Messages: 180 Registered: February 2025 Location: Brussels
|
Senior Member |
|
|
Quote:Would this mesoscoping netElement be considered a linear net element or a non linear net element?
I think its considered a linear netElement as it simply allows travel between station A and station B on one of the tracks, but I am not sure if this is enough to be considered a linear mesoscopic net element.
From memory, a LinearNetElement has a length and direction. Since you've defined the NetElement with two AssociatedPositioningSystems for intrinsic coordinates 0 and 1, it has both, and therefor is a LinearNetElement. Which also makes sense because the subclass was intended for this use exactly, the element that links 'nonlinear' elements and serves as pathways. Although I don't think there is a good definition for it anywhere..
And it's probably not needed anymore, since the most recent version of RTM, v1.5, has removed the subclasses and the XSD files of railML 3.3 no longer have the element defined.
Quote:If referencing to it, should I use linearLocation and intrinsic coordinate begin = 0 and intrinsic coordinate end = 1
or
Should I use Line.SpotLocation and intrinsic coordinate = 0?
Another option perhaps would be Line.AreaLocation referencing both microscopic netElements?
I'm assuming you're asking the questioned related to the positioning of the 'Line' entity? In that case, you could use either the LinearLocation or the AreaLocation. But not the SpotLocation as that would only relate to one IntrinsicCoordinate.
Mathias Vanden Auweele
Railway data freelancer
https://matdata.eu
Brussels, Belgium
|
|
|
|
| Re: UC NEST Positioning approach for lineSegment with 2 or more tracks [message #3643 is a reply to message #3637] |
Wed, 11 June 2025 16:42   |
christian.rahmig
Messages: 596 Registered: January 2016
|
Senior Member |
|
|
Dear Jim and Mathias,
thank you for your questions and answers!
Everything described by Mathias is correct: You can locate your two-track line segment...
* on the microscopic topology using an areaLocation, and/or
* on the mesoscopic topology using a linearLocation.
When aggregating (linear) microscopic netElements representing open tracks, you will get a (linear) mesoscopic netElement representing a line segment.
Best regards
Christian
Christian Rahmig – Infrastructure schema coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
|
|