Home » railML newsgroups » railml.timetable » How to represent open circulations in railML?
How to represent open circulations in railML? [message #1663] Fri, 17 November 2017 16:20 Go to previous message
Leopold Kühschelm is currently offline  Leopold Kühschelm
Messages: 8
Registered: September 2015
Junior Member
Dear railML Timetable Community!

When defining an rostering with an open (non-cyclic) circulation of blocks, there are two different possibilities to model them in railML.

Either with an final open circulation Element at the end:

<circulations>
           <circulation blockRef="b00380" operatingPeriodRef="op0103" nextBlockRef="b00381" nextOperatingPeriodRef="op0104"/>
           <circulation blockRef="b00381" operatingPeriodRef="op0104" nextBlockRef="b00382" nextOperatingPeriodRef="op0105"/>
           <circulation blockRef="b00382" operatingPeriodRef="op0105" nextBlockRef="b00383" nextOperatingPeriodRef="op0106"/>
           <circulation blockRef="b00383" operatingPeriodRef="op0106" nextBlockRef="b00384" nextOperatingPeriodRef="op0107"/>
           <circulation blockRef="b00384" operatingPeriodRef="op0107"/>
       </circulations>

So you can see in the example there is a final circulation with no nextBlockRef and nextOperatingPeriodRef attributes. But in my point of view this last circulation element is redundant and may be left out - like the following example depicts:

<circulations>
           <circulation blockRef="b00380" operatingPeriodRef="op0103" nextBlockRef="b00381" nextOperatingPeriodRef="op0104"/>
           <circulation blockRef="b00381" operatingPeriodRef="op0104" nextBlockRef="b00382" nextOperatingPeriodRef="op0105"/>
           <circulation blockRef="b00382" operatingPeriodRef="op0105" nextBlockRef="b00383" nextOperatingPeriodRef="op0106"/>
           <circulation blockRef="b00383" operatingPeriodRef="op0106" nextBlockRef="b00384" nextOperatingPeriodRef="op0107"/>
       </circulations>

As well I have read the railML-Wiki entry on circulations (http://wiki.railml.org/index.php?title=TT:circulationWink. There I found following section on this question:

"There exists a <circulation> element for every block on every operational day. Via the attributes nextBlockRef and nextOperatingperiodRef the blocks are connected to a chain and form a rostering. ..."

I am not quit sure how to interpret this phrase. Is it sufficient to refer the final block and operatingPeriod in an nextBlockRef and nextOperatingPeriodRef attribute, or do I have to add an additional circulation element at the end with a blockRef and operatingPeriodRef pointing to the last block and operatingPeriod?

Best regards,
Leopold Kühschelm

[Updated on: Mon, 20 November 2017 11:33] by Moderator

Report message to a moderator

 
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: example data: East Saxony railway network by FBS
Next Topic: DepartureDay / ArrivalDay at first <ocpTT> of a train run
Goto Forum:
  


Current Time: Thu Apr 25 07:16:00 CEST 2024