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.
Any suggestion how to integrate that nicely into the data
format - be it for therion itself, be it for post processing.
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.
This can be done within Therion today via
P144 P147a 252 -2 1.00
flags
no duplicate P147a P147 252 -2 3.50
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.
P144 P147 252 -2 4.50 # length:3.50
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?
I'm unsure it will ever be possible to automatically extract
cavelength in complex caves - see attached examples.
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 (http://therion.speleo.sk/wiki/doku.php?id=projeurope#)
in german speaking countries?
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.
--md
_______________________________________________ Therion mailing list Therion@speleo.sk http://mailman.speleo.sk/mailman/listinfo/therion