I recently used Therion to produce a map for a short horizontal cave. The cave is only a little over 100' long and the floor is almost level from one end to the other. The "depth" information that Therion generated for the legend is 3 feet even though some of the passage in the cave is 5 feet high. I'm assuming that therion uses the vertical difference between the highest station and the lowest station to generate the depth number without regard to LRUD data, is this correct? And does anybody have a suggestion for how I can easily get the correct depth output onto my map? I can see how this could be a significant issue if you had a cave with little vertical extent except for a high dome. You would have to shoot a shot to a station at the top of the dome to capture it's vertical extent in the legend data. Also, I experimented with using "walls on" to see if it would get Therion to use the LRUD data to determine depth. It didn't, but I found that Therion is reading my LRUD data as meters instead of feet. I use the command "units length feet" before the data but seems to only work for the tape measurement. Am I missing something? Sorry if these questions are a little basic, but I've still got a lot to learn about Therion. Much thanks, JP McLendon
On Tue, Jun 26, 2012 at 05:06:50PM -0400, McLendonJP@aol.com wrote:
Therion is reading my LRUD data as meters instead of feet. I use the command "units length feet" before the data but seems to only work for the tape measurement. Am I missing something?
The therion book doesn't seem to explicitly include these in the list of valid quantities, but the syntax comes from Survex so this should work: units left right up down feet Cheers, Olly
I'm assuming that therion uses the vertical difference between the highest station and the lowest station to generate the depth number without regard to LRUD data, is this correct?
Yes.
And does anybody have a suggestion for how I can easily get the correct depth output onto my map?
You can add some tex code to a layout. See http://therion.speleo.sk/wiki/doku.php?id=tex#overriding_data_supplied_by_th erion_map_headers Eg code tex-map \cavedepth{300\thinspace{}ft} %forcing reported depth to 300 ft endcode
I can see how this could be a significant issue if you had a cave with little vertical extent except for a high dome. You would have to shoot a shot to a station at the top of the dome to capture it's vertical extent in the legend data.
That would avoid the need to manually edit the depth each time you suspected a new survey might change the depth of the cave. It would be my preferred method, even if it means creating an artificial shot to replicate the 'up' data. It would need 'flags duplicate' to prevent it being added to the reported survey network length. Bruce
participants (3)
-
Bruce -
McLendonJP＠aol.com -
Olly Betts