<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">On 2012-03-04, at 01:22, Bruce wrote:<br><br><blockquote type="cite">You would have to bear in mind the definition of cave length that you want to adhere to when surveying the cave, and choose stations accordingly. The legs that do not contribute to length would be flagged as duplicate.<br></blockquote><br><div>Any suggestion how to integrate that nicely into the data format - be it for therion itself, be it for post processing.</div><div>Generally what would help a lot is a way to say "of this leg 4.50m long only 3.50m should be added to the cave length.</div><div><br></div><div>This can be done within Therion today via</div><div><br></div><span class="Apple-tab-span" style="white-space:pre"> </span>flags duplicate<br><div><span class="Apple-tab-span" style="white-space:pre"> </span>P144<span class="Apple-tab-span" style="white-space:pre"> </span>P147a<span class="Apple-tab-span" style="white-space:pre"> </span>252<span class="Apple-tab-span" style="white-space:pre"> </span>-2<span class="Apple-tab-span" style="white-space:pre"> </span>1.00<br></div><span class="Apple-tab-span" style="white-space:pre"> </span>flags no duplicate<br><div> P147a<span class="Apple-tab-span" style="white-space:pre"> </span>P147<span class="Apple-tab-span" style="white-space:pre"> </span>252<span class="Apple-tab-span" style="white-space:pre"> </span>-2<span class="Apple-tab-span" style="white-space:pre"> </span>3.50</div><div><span class="Apple-style-span" style="white-space: pre; "><br></span></div><div>But this seems to be very error prone. An alternative would be to use an external program to determine cave length and just encode the information in the therion file. E.g.</div><div><br></div><div><br></div><span class="Apple-tab-span" style="white-space:pre"> </span>flags duplicate<br><span class="Apple-tab-span" style="white-space:pre"> </span>P144<span class="Apple-tab-span" style="white-space:pre"> </span>P147<span class="Apple-tab-span" style="white-space:pre"> </span>252<span class="Apple-tab-span" style="white-space:pre"> </span>-2<span class="Apple-tab-span" style="white-space:pre"> </span>4.50 # length:3.50<div><br></div><div>But this would mean not only parsing therion files but also parsing comments. Any suggestions how to incorporate such data with maximum clarity and comparability? <br><br></div><div>I'm unsure it will ever be possible to automatically extract cavelength in complex caves - see attached examples.</div><div>The "small reduction in length" was about 16% length reduction for the "Kluterthöhle" shown in the second attachment. And to my understanding all organized Austrian & German caving is basing their calculations today on the Trimmel method. Perhaps that is the reason therion sees relative little use (<a href="http://therion.speleo.sk/wiki/doku.php?id=projeurope#">http://therion.speleo.sk/wiki/doku.php?id=projeurope#</a>) in german speaking countries?</div><div><br></div><div>I'm not complaining. But I would be very grateful for guidance how i can integrate cave length calculation with minimal fuss and thus keeping the data in *.th files in a state where they document our surveys and are not full of hacks which nobody will be able to understand 25 years from now.</div><div><br></div><div>--md<br><div><br></div><div><br></div><div><br></div><div><br></div><div><img id="35247592-47cb-40a2-b049-381058d926fd" height="240" width="250" apple-width="yes" apple-height="yes" src="cid:A12A9DE5-457E-4FE7-8004-F7448B1A90CB@fritz.box"><img id="9d320bff-220f-4043-b3ec-b90feb9fe4a0" height="145" width="320" apple-width="yes" apple-height="yes" src="cid:C565DE80-5F22-4F65-BB5E-10BC29F60195@fritz.box"></div></div></body></html>