<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=US-ASCII" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 9.00.8112.16446"></HEAD>
<BODY style="FONT-FAMILY: Arial; COLOR: #000000; FONT-SIZE: 10pt" id=role_body
bottomMargin=7 leftMargin=7 rightMargin=7 topMargin=7><FONT id=role_document
color=#000000 size=2 face=Arial>
<DIV>Graham,</DIV>
<DIV>I've got the centerline and LRUD data all together in the same block, as in
"data normal station left right up down newline length compass clino" and
immediately before it "units length feet" but it still treats my input numbers
at meters instead of feet (for the LRUD). Olly's suggestion to use "units left
right up down feet" works perfectly to get Therion to treat the numbers as
feet.</DIV>
<DIV> </DIV>
<DIV>Thanks,</DIV>
<DIV>JP</DIV>
<DIV> </DIV>
<DIV>
<DIV>In a message dated 6/27/2012 6:18:31 A.M. Eastern Daylight Time,
graham.mullan@coly.org.uk writes:</DIV>
<BLOCKQUOTE
style="BORDER-LEFT: blue 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5px"><FONT
style="BACKGROUND-COLOR: transparent" color=#000000 size=2 face=Arial>>
From: McLendonJP@aol.com<BR><BR>> Also, I experimented with using "walls
on" to see if it would get<BR>>Therion<BR>> to use the LRUD data to
determine depth. It didn't, but I found that<BR>> Therion is reading
my LRUD data as meters instead of feet. I use the<BR>>command<BR>>
"units length feet" before the data but seems to only work for the
>tape<BR>> measurement. Am I missing something?<BR><BR>Can I assume that
you have separate blocks of data for the centreline<BR>and the LRUD? If so
then you need to enter the "units length feet" line<BR>again after the "data
dimensions station left right up down" line.<BR><BR>Alternatively just take
all your measurements in metres ;-)<BR><BR>You are right, however, that
Therion determines depth by the difference<BR>between the highest and lowest
stations. It is difficult to see how else<BR>it would work. It is a trivial
matter to mark your highest and lowest<BR>points as
stations.<BR><BR>Graham<BR>> <BR>> <BR>> Today's Topics:<BR>>
<BR>> 1. Incorrect depth generated for legend
(McLendonJP@aol.com)<BR>> 2. Re: Incorrect depth generated for
legend (Olly Betts)<BR>> 3. Re: Incorrect depth generated for
legend (Bruce)<BR>> <BR>> <BR>>
----------------------------------------------------------------------<BR>>
<BR>> Message: 1<BR>> Date: Tue, 26 Jun 2012 17:06:50 -0400
(EDT)<BR>> From: McLendonJP@aol.com<BR>> Subject: [Therion] Incorrect
depth generated for legend<BR>> To: Therion@speleo.sk<BR>> Message-ID:
<1fbcc.371cc17a.3d1b7e6a@aol.com><BR>> Content-Type: text/plain;
charset="us-ascii"<BR>> <BR>> I recently used Therion to produce a map
for a short horizontal cave. The <BR>> cave is only a little over
100' long and the floor is almost level from one <BR>> end to the
other. The "depth" information that Therion generated for the <BR>> legend
is 3 feet even though some of the passage in the cave is 5 feet high.
<BR>> I'm assuming that therion uses the vertical difference between
the highest <BR>> station and the lowest station to generate the
depth number without regard <BR>> to LRUD data, is this correct? And
does anybody have a suggestion for how I <BR>> can easily get the
correct depth output onto my map? I can see how this <BR>> could be a
significant issue if you had a cave with little vertical extent <BR>>
except for a high dome. You would have to shoot a shot to a station at
the <BR>> top of the dome to capture it's vertical extent in the
legend data.<BR>> <BR>> Also, I experimented with using "walls on"
to see if it would get Therion <BR>> to use the LRUD data to
determine depth. It didn't, but I found that <BR>> Therion is reading
my LRUD data as meters instead of feet. I use the command <BR>>
"units length feet" before the data but seems to only work for the tape
<BR>> measurement. Am I missing something?<BR>> <BR>> Sorry if
these questions are a little basic, but I've still got a lot to <BR>>
learn about Therion. <BR>> <BR>> Much thanks,<BR>> JP
McLendon<BR>> <BR>> <BR>> -------------- next part
--------------<BR>> An HTML attachment was scrubbed...<BR>> URL:
<http://mailman.speleo.sk/pipermail/therion/attachments/20120626/1c2c4eea/attachment.html><BR>>
<BR>> ------------------------------<BR>> <BR>> Message: 2<BR>>
Date: Wed, 27 Jun 2012 00:10:42 +0100<BR>> From: Olly Betts
<olly@survex.com><BR>> Subject: Re: [Therion] Incorrect depth
generated for legend<BR>> To: McLendonJP@aol.com<BR>> Cc:
Therion@speleo.sk<BR>> Message-ID:
<20120626231042.GM21560@survex.com><BR>> Content-Type: text/plain;
charset=us-ascii<BR>> <BR>> On Tue, Jun 26, 2012 at 05:06:50PM -0400,
McLendonJP@aol.com wrote:<BR>>> Therion is reading my LRUD data as
meters instead of feet. I use the command<BR>>> "units length feet"
before the data but seems to only work for the tape<BR>>> measurement.
Am I missing something?<BR>> <BR>> The therion book doesn't seem to
explicitly include these in the list of<BR>> valid quantities, but the
syntax comes from Survex so this should work:<BR>> <BR>> units left
right up down feet<BR>> <BR>> Cheers,<BR>>
Olly<BR>> <BR>> <BR>> ------------------------------<BR>> <BR>>
Message: 3<BR>> Date: Wed, 27 Jun 2012 18:09:39 +1200<BR>> From: Bruce
<bruce@tomo.co.nz><BR>> Subject: Re: [Therion] Incorrect depth
generated for legend<BR>> To: 'List for Therion users'
<therion@speleo.sk><BR>> Message-ID:
<6FA0C0A3E79A4D7F920D3CF3BE25F5AD@JUICEBRAIN><BR>> Content-Type:
text/plain; charset="us-ascii"<BR>> <BR>>> I'm assuming that therion
uses the vertical difference between the highest<BR>> station and the
lowest station to generate the depth number without regard<BR>> to LRUD
data, is this correct? <BR>> <BR>> Yes.<BR>> <BR>> <BR>>
<BR>>> And does anybody have a suggestion for how I can easily get the
correct<BR>> depth output onto my map? <BR>> <BR>> You can add some
tex code to a layout. See<BR>>
http://therion.speleo.sk/wiki/doku.php?id=tex#overriding_data_supplied_by_th<BR>>
erion_map_headers<BR>> <BR>> Eg<BR>> <BR>> code
tex-map<BR>> \cavedepth{300\thinspace{}ft}
%forcing reported depth to 300 ft<BR>> endcode<BR>>
<BR>> <BR>> <BR>> <BR>> <BR>>> I can see how
this could be a significant issue if you had a cave with<BR>> little
vertical extent except for a high dome. You would have to shoot a<BR>> shot
to a station at the top of the dome to capture it's vertical extent in<BR>>
the legend data.<BR>> <BR>> That would avoid the need to manually edit
the depth each time you suspected<BR>> a new survey might change the depth
of the cave. It would be my preferred<BR>> method, even if it means
creating an artificial shot to replicate the 'up'<BR>> data. It would
need 'flags duplicate' to prevent it being added to the<BR>> reported
survey network length.<BR>> <BR>> <BR>> <BR>> Bruce<BR>>
<BR>> <BR>> <BR>> -------------- next part
--------------<BR>> An HTML attachment was scrubbed...<BR>> URL:
<http://mailman.speleo.sk/pipermail/therion/attachments/20120627/ca2c0b00/attachment-0001.htm><BR>>
<BR>> ------------------------------<BR>> <BR>>
_______________________________________________<BR>> Therion mailing
list<BR>> Therion@speleo.sk<BR>>
http://mailman.speleo.sk/mailman/listinfo/therion<BR>> <BR>> <BR>>
End of Therion Digest, Vol 78, Issue 23<BR>>
***************************************<BR>>
<BR><BR>_______________________________________________<BR>Therion mailing
list<BR>Therion@speleo.sk<BR>http://mailman.speleo.sk/mailman/listinfo/therion<BR></FONT></BLOCKQUOTE></DIV></FONT></BODY></HTML>