drawing data for the
famous Therion Extended Elevation Control
<https://therion.speleo.sk/samples.doc/25.html> sample, then I might remain
inspired enough to generate a more comprehensive set of examples.
Enjoy your caves
Bruce
___
Therion mailing list
> A better approach would be to define your own line type rope and assign it
> an already defined linetype (like 'border'). Â [This is quite easy but I'd
> have to look it up -obviously not so easy as I would have done it already! -
> someone else may have it on the tip of their tongue]
>
> This
Hi Andrew
I have not really used extend yet, but have it in mind for some future
projects. I am hoping to use 'revise' to allow multiple extended elevation
projections of the same piece of cave and to move the 'extend' out of the
survey data and into the map definition where it more logically sits
I am struggling with the extend: left right normal and reverse, they do
not seem to be doing what I would expect or as described at
http://therion.speleo.sk/wiki/doku.php?id=tfc:321
therion 5.3.7 on debian wheezy
These have been generated from the th file attached, which was an import
from
On Sat, 05 Mar 2005 00:21:22 +0100
Stacho Mudrak wrote:
>> There is a new developement snapshot with new extended elevation
>> processing. Now you can work with it like with plan/elevation
>> projections. Specifications can be done via extend option in
>> centerline(see CHANGES file). Also
>>
>>
>> Again, add in layout:
>>
>> color map-fg 50
>> symbol-hide group all
>> symbol-show area water
>>
>> code metapost
>> def a_water (expr p) =
>> T:=identity;
>> thfill p withcolor (0.1, 0.2, 0.8);
>> enddef;
It would be more correct do define own symbol set than to redefine the
Eric Madelaine wrote:
> Here is the data off the embut de la Pinee, including whatever cause this
> wrong extended elevation map.
> I have not included any scan images (except for the ext. elevatin itself) as
> it would have be over 4 Mo large...
Well, I had a look at your code, and there
