And thanks to Kevin Dixon for reminding me. You can find much of relevance to Therion within the Survex Manual. There is a link to it on the front page of the Therion wiki. Search the Survex manual for "flags" and you will learn more. Bruce From: Therion <therion-bounces@speleo.sk> On Behalf Of Bruce Mutton via Therion Sent: Thursday, 10 May 2018 8:02 AM To: 'List for Therion users' <therion@speleo.sk> Cc: Bruce Mutton <bruce@tomo.co.nz> Subject: Re: [Therion] Therion Map Header Overrides Nick Here are some examples of various 'flags' usage, for shot flags, not to be confused with station flags. They are a survey property, not so much a drawing property. Approximate and duplicate: https://therion.speleo.sk/wiki/extend?s[]=flags#summary_of_all_extend_option s_for_survey_centrelines <https://therion.speleo.sk/wiki/extend?s%5b%5d=flags#summary_of_all_extend_o ptions_for_survey_centrelines> and scroll down to the code below "Creating links between separate caves that are close to each other". That one is a bit oddball, not typical usage. https://therion.speleo.sk/wiki/metapost?s[]=flags#general_symbol_examples <https://therion.speleo.sk/wiki/metapost?s%5b%5d=flags#general_symbol_exampl es> to redefine centrelines to reflect flag states. And, um, yes, there is not too much on actual usage examples for flags surface. Here is a snippet from my last Sunday's survey efforts. A short cave that required three ptopo files to adequately capture it. It is part of a survey loop that goes out of one entrance and into another. data normal from to tape compass clino ignoreall . #following legs are within the cave #3.18 3.19 2.099 355.01 -32.84 3.19 entrance rock #3.18 3.19 2.098 355.2 -32.67 #3.18 3.19 2.098 355.31 -32.69 3.18 3.19 2.098 355.11 -32.73 Calculated leg from 3 above 3.19 - 0.269 49.83 -12.76 3.19 - 0.588 43.99 45.86 3.19 - 0.714 21.48 76.27 . flags surface #following legs are on the surface # extend right #3.19 3.20 2.819 254.97 -14.44 3.21 other entrance rock #3.19 3.20 2.818 255.03 -14.34 #3.19 3.20 2.819 255.11 -14.33 3.19 3.20 2.819 255.0 -14.37 Calculated leg from 3 above 3.20 - 0.556 102.47 -59.13 3.20 - 1.045 129.78 5.18 #3.20 3.21 6.017 207.42 -12.3 #3.20 3.21 6.026 207.53 -12.4 #3.20 3.21 6.067 207.48 -12.46 3.20 3.21 6.037 207.47 -12.39 Calculated leg from 3 above flags not surface #following legs are within the cave 3.21 - 1.275 43.78 -4.28 3.21 - 2.58 41.32 3.61 3.21 - 2.914 39.54 15.74 . # extend left #3.21 3.22 3.613 113.19 23.44 #3.21 3.22 3.616 113.08 23.59 #3.21 3.22 3.609 113.05 23.6 #rename 3.22 as 3.14 to acknowledge loop 3.21 3.14 3.613 113.13 23.55 Calculated leg from 3 above 3.14 - 4.408 324.85 -51.94 The survey-list output for this cave looks like. Title Length Depth Explored Approx. Duplicate Surface Shots Stations Wairoa Valley Cave, Nelson 128 10 0 0 3 9 428 431 1-Wairoa 46 7 0 0 0 0 131 132 2-Upper, Wairoa Cave 15 3 0 0 0 0 61 62 3-Downstream, Wairoa Cave 67 3 0 0 0 9 235 235 The total survey length (surface + cave + duplicate) is 140m, and 9m of it is on the surface. There is also 3m of survey in there that is duplicated (happens to be a nosurvey "shot" for a visual-only connection established at the whole-cave level of survey. Bruce From: Therion <therion-bounces@speleo.sk <mailto:therion-bounces@speleo.sk>
On Behalf Of Nick Bairstow via Therion Sent: Thursday, 10 May 2018 3:02 AM To: List for Therion users <therion@speleo.sk <mailto:therion@speleo.sk> > Cc: Nick Bairstow <Nick@pff.uk.com <mailto:Nick@pff.uk.com> > Subject: Re: [Therion] Therion Map Header Overrides
Bruce, I have never used flags. I have just been though the Therion book and wiki for information but for clarification could you post an example of surface flag use please. Thanks. Nick From: Therion [mailto:therion-bounces@speleo.sk] On Behalf Of Bruce Mutton via Therion Sent: 09 May 2018 11:04 To: 'List for Therion users' <therion@speleo.sk <mailto:therion@speleo.sk> > Cc: Bruce Mutton <bruce@tomo.co.nz <mailto:bruce@tomo.co.nz> > Subject: [Therion] Therion Map Header Overrides Nick
The override below is to change the Therion default team, cave length, cave depth data on the map output. Used in this case because a short surface survey needed to be shown on the map but the data was skewing the actual cave length and depth.
I'm not sure that is a very good way to deal with the issue. In the screenshot below I have a surface survey shown (green dots), designated surface by use of 'flags surface', 'flags not surface' interleaved with the survey data as appropriate. No need to fudge the cave length or depth because Therion does not include surface data in the cave length. There is some complexity around it, but you can show or hide the cave and surface centrelines using; symbol-show group surface-centreline symbol-hide group cave-centreline Bruce
