| [railML3]: operationalPoint of operationalType="block" [message #2689] |
Thu, 08 April 2021 14:51  |
Dominik Looser
Messages: 18
Registered: March 2020
|
Junior Member |
|
|
Dear all,
After internal discussion with our customer (BaneNor and Jernbanedirektoratet in Norway) we would like to ask a question here:
In RailML3.1 (and later 3.2) we are not sure how to export operationalPoints of @operationalType="block". These are often 0 meters long and limited by two signals (<signalIL> with @function="block") that are located on the same position.
Other operationalPoints, e.g. those with @type="station" have a subelement with @netElementRef pointing to the mesoscopic netElement of that station.
For block posts, we do not have a mesoscopic netElement, as they are only considered to exist in the microscopic world.
Our suggestion is to reference the microscopic netElement that corresponds to the line between the stations that the block post lies between.
<operationalPoint id="opp1014">
<name language="NO" name="Kalvsjø bp."/>
<areaLocation id="al1014">
<associatedNetElement keepsOrientation="true" netElementRef="ne_588" posBegin="2202.0" posEnd="2202.0"/>
</areaLocation>
<opEquipment>
<ownsSignal ref="sig826"/>
<ownsSignal ref="sig827"/>
</opEquipment>
<opOperations>
<opOperation operationalType="block"/>
</opOperations>
</operationalPoint>
(Kalvsjø is the block post and lies between the stations of Roa and Grindvoll. The netElement id="ne_588" is the microscopic netElement between those two stations.)
The key question is, if it a good idea to reference a microscopic netElement from an operationalPoint.
Are there any other suggestions or best practices on how to model a block post operational point?
Thank you in advance
Best regards,
Dominik Looser
trafit solutions gmbh
|
|
|
|
Members
Search
Help
Login
Home
