Graham, 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. Thanks, JP In a message dated 6/27/2012 6:18:31 A.M. Eastern Daylight Time, graham.mullan@coly.org.uk writes:
From: McLendonJP@aol.com
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?
Can I assume that you have separate blocks of data for the centreline and the LRUD? If so then you need to enter the "units length feet" line again after the "data dimensions station left right up down" line. Alternatively just take all your measurements in metres ;-) You are right, however, that Therion determines depth by the difference between the highest and lowest stations. It is difficult to see how else it would work. It is a trivial matter to mark your highest and lowest points as stations. Graham
Today's Topics:
1. Incorrect depth generated for legend (McLendonJP@aol.com) 2. Re: Incorrect depth generated for legend (Olly Betts) 3. Re: Incorrect depth generated for legend (Bruce)
----------------------------------------------------------------------
Message: 1 Date: Tue, 26 Jun 2012 17:06:50 -0400 (EDT) From: McLendonJP@aol.com Subject: [Therion] Incorrect depth generated for legend To: Therion@speleo.sk Message-ID: <1fbcc.371cc17a.3d1b7e6a@aol.com> Content-Type: text/plain; charset="us-ascii"
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
-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mailman.speleo.sk/pipermail/therion/attachments/20120626/1c2c4eea/attachment.html>
------------------------------
Message: 2 Date: Wed, 27 Jun 2012 00:10:42 +0100 From: Olly Betts <olly@survex.com> Subject: Re: [Therion] Incorrect depth generated for legend To: McLendonJP@aol.com Cc: Therion@speleo.sk Message-ID: <20120626231042.GM21560@survex.com> Content-Type: text/plain; charset=us-ascii
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
------------------------------
Message: 3 Date: Wed, 27 Jun 2012 18:09:39 +1200 From: Bruce <bruce@tomo.co.nz> Subject: Re: [Therion] Incorrect depth generated for legend To: 'List for Therion users' <therion@speleo.sk> Message-ID: <6FA0C0A3E79A4D7F920D3CF3BE25F5AD@JUICEBRAIN> Content-Type: text/plain; charset="us-ascii"
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
-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mailman.speleo.sk/pipermail/therion/attachments/20120627/ca2c0b00/attachment-0001.htm>
------------------------------
_______________________________________________ Therion mailing list Therion@speleo.sk http://mailman.speleo.sk/mailman/listinfo/therion
End of Therion Digest, Vol 78, Issue 23 ***************************************
_______________________________________________ Therion mailing list Therion@speleo.sk http://mailman.speleo.sk/mailman/listinfo/therion
Hi JP Try "units imperial". Best, Torsten McLendonJP@aol.com hat am 27. Juni 2012 um 14:23 geschrieben:
Graham, 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.
Thanks, JP
In a message dated 6/27/2012 6:18:31 A.M. Eastern Daylight Time, graham.mullan@coly.org.uk writes:
From: McLendonJP@aol.com
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?
Can I assume that you have separate blocks of data for the centreline and the LRUD? If so then you need to enter the "units length feet" line again after the "data dimensions station left right up down" line.
Alternatively just take all your measurements in metres ;-)
You are right, however, that Therion determines depth by the difference between the highest and lowest stations. It is difficult to see how else it would work. It is a trivial matter to mark your highest and lowest points as stations.
Graham
Today's Topics:
1. Incorrect depth generated for legend (McLendonJP@aol.com) 2. Re: Incorrect depth generated for legend (Olly Betts) 3. Re: Incorrect depth generated for legend (Bruce)
----------------------------------------------------------------------
Message: 1 Date: Tue, 26 Jun 2012 17:06:50 -0400 (EDT) From: McLendonJP@aol.com Subject: [Therion] Incorrect depth generated for legend To: Therion@speleo.sk Message-ID: <1fbcc.371cc17a.3d1b7e6a@aol.com> Content-Type: text/plain; charset="us-ascii"
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
Try "units imperial".
At first look that seems to be the obvious answer, but (without doing any tests) I notice the therion book lists this as an option within a layout, so in principle it only affects the output (forces conversion of metric data to imperial units is how I have used it in the past), and does not specify what the input data units are. Or am I mistaken? The other place it is listed is as an entry in the therion initialisation file. Does this usage specify both unit system for both input and output perhaps? And perhaps it can be used in the thconfig file to the same effect? The above affects the entire dataset though, which is only convenient in some situations. Can "units [imperial/metric]" be used within a survey or centreline though? As for specifying the type of input data, this is the place where it would seem logical to put it. I can imagine that in the US, some caves might comprise both metric and imperial source data, and in NZ we might for example have some 1960's data to include with modern data. Clarification anyone? Bruce
participants (3)
-
Bruce -
McLendonJP＠aol.com -
Torsten Schnitter