Home » railML newsgroups » railML.infrastructure » Extension suggestion for on which (track)side of a crosSection the referenced ocp is
Extension suggestion for on which (track)side of a crosSection the referenced ocp is [message #1881] Sat, 14 July 2018 17:45 Go to previous message
Torben Brand is currently offline  Torben Brand
Messages: 158
Registered: March 2016
Senior Member
crossSection@nor:ocpRepSide

We see a need to map the ocp in relation to the track (s).
Today the ocp is linked to the crosssection so it knows on which pos/abspos it is placed. But it does not know on which side of the track/crossSection it is placed. Thus, we suggest an optional attribute with the enumeration values "left" or "right" (as seen in track direction)

This for the following use case: Network statement and schematic track plan and nice to have for capacity planning.

We see the need in the simple example. When you load the simple example, which does not contain visualisation coordinates, into NorRailView, the system places the OCP's on top of the tracks. This not in accordance with the schematic track plan of the simple example where the OCP is placed below the tracks.

I know this posting will raise a lot of questions of what constitutes and ocp. So I keep it somewhat open with using "Rep" in nor:OcpRepSide. "Rep" can stand for "representative", meaning the dispatcher (the dot in the simple example drawing) . It can also stand for "representation" as some tools use building icons to place the ocp as an object in the tool. This does not mean that there is a real building there. Thus, the use of "representation".

In the Norwegian national version of network statement (SJN http://orv.jbv.no/sjn/doku.php?id=strekningsbeskrivelse:fork laringer_og_forkortelser) we also declare on which side of a line the station/stoppingPoint is placed.

We will implement this as a Norwegian (nor:) extension in railML2.3. We suggest to implement the attribute also in railML2.4.
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: railML 2.3 infrastructure extension proposal - locks
Next Topic: Re-factoring of <infraAttributes>
Goto Forum:
  


Current Time: Sun Apr 28 06:54:24 CEST 2024