Home » railML newsgroups » railml.infrastructure » [railML3]: operationalPoint of operationalType="block" (How to link them to a netElement)
[railML3]: operationalPoint of operationalType="block" [message #2689] Thu, 08 April 2021 14:51 Go to next message
Dominik Looser is currently offline  Dominik Looser
Messages: 7
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
Re: [railML3]: operationalPoint of operationalType="block" [message #2692 is a reply to message #2689] Fri, 09 April 2021 13:54 Go to previous messageGo to next message
christian.rahmig is currently offline  christian.rahmig
Messages: 303
Registered: January 2016
Senior Member
Dear Dominik,

in general, your approach of locating the <operationalPoint> on a microscopic <netElement> is fine.
However, I don't understand why you want to locate an operational point with a length of zero meters using an <areaLocation>? I think, a <spotLocation> would suit better.

By the way: locating <operationalPoint> elements on microscopic topology is quite common. In particular, it is best practice to model the operational point center point (in railML2 language also known as "cross section") using a <spotLocation> on a microscopic <netElement>.

Are there any other best practice ideas from the community?

Best regards
Christian


Christian Rahmig - Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
Re: [railML3]: operationalPoint of operationalType="block" [message #2702 is a reply to message #2692] Tue, 13 April 2021 10:42 Go to previous message
Dominik Looser is currently offline  Dominik Looser
Messages: 7
Registered: March 2020
Junior Member
Dear Christian,

Thank you for your answer.

For "ordinary" stations, we are using <areaLocation> in <operationalPoint> to locate the station's extent (as defined by its signals), and a <spotLocation> to define the center point (if existing).
I think it is best to keep those usages consistent within the same file:

  • <areaLocation> for the station's extent,
  • <spotLocation> for the station's center
For block posts, there are no center points in our models, which means, that only an <areaLocation> of 0 meters is created.

Best regards,
Dominik
Previous Topic: [railML2] adding an attribute for clearance on switches and crossings.
Goto Forum:
  


Current Time: Wed Apr 14 22:57:40 CEST 2021