[Therion] Altitude point in absolute AND relative in the same survey ?

[Gilbert (liste)]

Hello,

the altitude point is very usefull to set the altitude in the final 
survey. The altitude value is calculated with the Z value of the 
entrance Point and the depth survey of the station point. OK.


But, in my final survey (pdf), can I have the absolute value (from the 
sea level) and the depht value (from the entrance) in the same time ?


exemple :

 * the entrance of the cave is at altitude 1000m
 * my station point is at depth -100

I want to have the altitude value "-100" and "900 m" (from the sea 
level), on 2 specific altitude point, using and option, on the altitude 
point.


Does it existe ? Is it a new issue to create ?

Thanks

Gilbert
___
Therion mailing list
Therion@speleo.sk
https://mailman.speleo.sk/listinfo/therion

[Therion] Altitude colors range

[Marco Menchise]

On Mon, Jan 12, 2015 at 1:04 PM, Wookey  wrote:

Feedback on whether it fixes the problem would be appreciated.
>
> I made a test, the patch fixes the colors issue.

Thanks,
Marco
-- next part --
An HTML attachment was scrubbed...
URL: 

[Therion] Altitude colors range

[Bruce]

>Now I have added this into my surveys, I see that the centreline is

rendered as solid lines when you include the centreline (and have not

set the centreline symbol group to be hidden), but if you do not

include the centreline then the survey lines renderer in the scraps

are just dashes at each station rather than complete lines running the

complete distance between pairs of stations. Not a problem, but

curious as to why I get two different styles for cave survey lines.



  It has always been this way.  I did delve into the metapost once to
see why, from a code perspective.  It seems rational behaviour as far as
'using it' goes.



>Then I tried this on my 66km system survey and with centrelines set to

show in my layout, I found metapost used up all the words of memory it

is allowed so I get no output. From my logfile:

...

How can I get around this limitation?



  Interesting.  I have never come across this limitation, although
metapost usually logs messages of seeming complaint.  I inquired on the
forum years ago, and one of the Martin's or Stacho assured me that it should
never actually run out.  Not sure if I have ever plotted 66km of centreline?
I have probably come close.



>I can see how it is useful to be able to render centrelines and stations
for the entire system regardless.



  Yes, very useful.  I add each survey as it becomes available.  It is
then in the outputs as a reminder to draw the scraps!  Further - you can
differentiate the flags that apply to each survey shot with colour and line
style.

See the wiki
http://therion.speleo.sk/wiki/doku.php/metapost#general_symbol_examples 



Under the heading "Visualize cave centreline shot flags with colour for
splay and duplicate, and dash for approximate shot flags"



Bruce





-- next part --
An HTML attachment was scrubbed...
URL: 

[Therion] Altitude colors range

[Stacho Mudrak]

Wrong colors with centerline attached is a bug, that has allways been
there. Just change thscrap.cxx:68 and next line to

this->z = thnan;
this->a = thnan;

and it should be fixed (if you can compile therion). Thanks for finding
this out.

S.



On 8 January 2015 at 19:59, Bruce  wrote:

>
>
> >Now I have added this into my surveys, I see that the centreline is
>
> rendered as solid lines when you include the centreline (and have not
>
> set the centreline symbol group to be hidden), but if you do not
>
> include the centreline then the survey lines renderer in the scraps
>
> are just dashes at each station rather than complete lines running the
>
> complete distance between pairs of stations. Not a problem, but
>
> curious as to why I get two different styles for cave survey lines.
>
>
>
> *  It has always been this way.  I did delve into the metapost once to
> see why, from a code perspective.  It seems rational behaviour as far as
> 'using it' goes.*
>
>
>
> >Then I tried this on my 66km system survey and with centrelines set to
>
> show in my layout, I found metapost used up all the words of memory it
>
> is allowed so I get no output. From my logfile:
>
> ...
>
> How can I get around this limitation?
>
>
>
> *  Interesting.  I have never come across this limitation, although
> metapost usually logs messages of seeming complaint.  I inquired on the
> forum years ago, and one of the Martin's or Stacho assured me that it
> should never actually run out.  Not sure if I have ever plotted 66km of
> centreline? I have probably come close.*
>
>
>
> >I can see how it is useful to be able to render centrelines and stations
> for the entire system regardless.
>
>
>
> *  Yes, very useful.  I add each survey as it becomes available.  It
> is then in the outputs as a reminder to draw the scraps!  Further - you can
> differentiate the flags that apply to each survey shot with colour and line
> style.*
>
> *See the wiki
> http://therion.speleo.sk/wiki/doku.php/metapost#general_symbol_examples
>  *
>
>
>
> *Under the heading “Visualize cave centreline shot flags with colour for
> splay and duplicate, and dash for approximate shot flags”*
>
>
>
> *Bruce*
>
>
>
>
>
> ___
> Therion mailing list
> Therion at speleo.sk
> http://mailman.speleo.sk/mailman/listinfo/therion
>
>
-- next part --
An HTML attachment was scrubbed...
URL: 

[Therion] Altitude colors range

[Bruce]

7. 1. 2015 v 19:41, Bruce :


>>So what it is looking like, if the contributory maps are all derived from
scraps (or maps in turn derived from scraps), then the altitude range is
correct.

But if there is a map that is centerline derived (ie has no scraps) then the
altitude minima is set to zero.





>Only one question: do you have defined entrance?



Yes, the survey network has a number of entrances defined.  One of which is
present in the exported map I was experimenting with.

Bruce



-- next part --
An HTML attachment was scrubbed...
URL: 

[Therion] Altitude colors range

[Wookey]

+++ Footleg [2015-01-08 16:01 +]:
> Now I have added this into my surveys, I see that the centreline is
> rendered as solid lines when you include the centreline (and have not
> set the centreline symbol group to be hidden), but if you do not
> include the centreline then the survey lines renderer in the scraps
> are just dashes at each station rather than complete lines running the
> complete distance between pairs of stations. Not a problem, but
> curious as to why I get two different styles for cave survey lines.
> 
> Then I tried this on my 66km system survey and with centrelines set to
> show in my layout, I found metapost used up all the words of memory it
> is allowed so I get no output. From my logfile:
> 
> Here is how much of MetaPost's memory you used:
>  6498 strings out of 6522
>  15689 string characters out of 34452
>  151 words of memory out of 150
>  1389 symbolic tokens out of 16384
>  12i,75n,41p,489b,3f stack positions out of 300i,84n,5000p,608b,15f
>  10510 string compactions (moved 140463121 characters, 13446441
> strings)371 output files written: data.1 .. data.4017
> 
> How can I get around this limitation?

Not sure if this is the right answer but see if the info from line 113 of 
http://sources.debian.net/src/therion/5.3.16-3/debian/README.Debian/
helps at all

You'll have to translate it to windows-speak

Wookey
-- 
Principal hats:  Linaro, Debian, Wookware, ARM
http://wookware.org/

[Therion] Altitude colors range

[Footleg]

Now I have added this into my surveys, I see that the centreline is
rendered as solid lines when you include the centreline (and have not
set the centreline symbol group to be hidden), but if you do not
include the centreline then the survey lines renderer in the scraps
are just dashes at each station rather than complete lines running the
complete distance between pairs of stations. Not a problem, but
curious as to why I get two different styles for cave survey lines.

Then I tried this on my 66km system survey and with centrelines set to
show in my layout, I found metapost used up all the words of memory it
is allowed so I get no output. From my logfile:

Here is how much of MetaPost's memory you used:
 6498 strings out of 6522
 15689 string characters out of 34452
 151 words of memory out of 150
 1389 symbolic tokens out of 16384
 12i,75n,41p,489b,3f stack positions out of 300i,84n,5000p,608b,15f
 10510 string compactions (moved 140463121 characters, 13446441
strings)371 output files written: data.1 .. data.4017

How can I get around this limitation?

Footleg

On 8 January 2015 at 10:28, Footleg  wrote:
> I see it too now. I have not realised you could include just a
> centreline in the map. It shows every survey station and leg in the
> cave, rather than just those included in scraps right? When I add that
> my altitude baseline is set to 0m like yours using 5.3.16
>
> I've not done this before as I had assumed I could only see survey
> sections which were drawn in scraps. I can see how it is useful to be
> able to render centrelines and stations for the entire system
> regardless.
>
> Footleg
>
> On 7 January 2015 at 18:41, Bruce  wrote:
>>>Or maybe I am not understanding what you mean by including the centreline
>>> in the map
>>
>>
>>
>> Like this
>>
>> map DeckExtensionPlanMap -title "The Deck ExtensionUpper
>> LevelsMiddle Earth CaveGreenlink System"
>>
>>  …
>>
>>  36-BigWednesdayPlan at MiddleEarth
>>
>>  36-BigWednesdayPlanCL at MiddleEarth
>>
>> …
>>
>> end map
>>
>>
>>
>> where the contributory maps look like this…
>>
>>
>>
>> map 36-BigWednesdayPlanCL -title "36-BigWednesday centreline Plan"
>> -projection plan
>>
>>   36 #centreline survey
>>
>> endmap
>>
>>
>>
>> map 36-BigWednesdayPlan -title "36-BigWednesday Plan" -projection plan
>>
>>   36-BigWednesdayPlan-s1 #scraps
>>
>>   36-BigWednesdayPlan-s2
>>
>> endmap
>>
>>
>>
>> So what it is looking like, if the contributory maps are all derived from
>> scraps (or maps in turn derived from scraps), then the altitude range is
>> correct.
>>
>> But if there is a map that is centerline derived (ie has no scraps) then the
>> altitude minima is set to zero.
>>
>>
>>
>> One other thing.
>>
>> All my tests so far use survex for loop closure.  I have not tried using
>> Therion loop closure.
>>
>> And all my files are native Therion files – no survex imports.
>>
>>
>>
>> Bruce
>>
>>
>>
>> 
>>
>> From: therion-bounces at speleo.sk [mailto:therion-bounces at speleo.sk] On 
>> Behalf
>> Of Marco Menchise
>> Sent: Thursday, 8 January 2015 3:05 a.m.
>> To: List for Therion users
>> Subject: Re: [Therion] Altitude colors range
>>
>>
>>
>> I checked and I can confirm what Bruce is saying. If you don't include
>> centerline in map, the altitude range is correct.
>>
>>
>>
>> If you hide the centerline in the layout (leaving it in the map) the
>> altitude range keeps starting from 0 m.
>>
>>
>>
>> Marco
>>
>>
>>
>>
>>
>> On Wed, Jan 7, 2015 at 2:52 PM, Footleg  wrote:
>>
>> I am not seeing this Bruce. I just tested with 5.3.16. My survey imports the
>> centreline from a Survex .3d file however, so that might make a difference?
>> Or maybe I am not understanding what you mean by including the centreline in
>> the map. I turned off the centreline using 'symbol-hide line survey'. If I
>> comment that out in my layout then the centreline is drawn in the map, but
>> my altitude range still covers only the range of my scraps.
>>
>>
>>
>> Footleg
>>
>>
>>
>> On 5 January 2015 at 22:40, Bruce  wrote:
>>
>> OK, the problem is not the previews or the offsets, as it occurs in the map
>> examples below regardless of presence of previews or offsets.
>>
>> What does seem to control whether the altitudes start at zero meters is
>> whether the map definition includes a survey centerline.
>>
>> If part of map definition includes a survey centerline, then altitudes are
>> coloured from zero meters to survey maxima (a bug?).
>>
>> If map definition has no survey centerline as part of it’s definition, then
>> coloured from survey minima to survey maxima (correct behaviour).
>>
>> Hence I find this behaviour manifests in maps in progress, but when they are
>> finished and I (usually) turn off the centerline maps, they correct
>> themselves.
>>
>>  Bruce
>>
>>
>>
>>
>> ___
>> Therion mailing list
>> Therion at speleo.sk
>> http://mailman.speleo.sk/mailman/listinfo/therion
>>

[Therion] Altitude colors range

[Footleg]

I see it too now. I have not realised you could include just a
centreline in the map. It shows every survey station and leg in the
cave, rather than just those included in scraps right? When I add that
my altitude baseline is set to 0m like yours using 5.3.16

I've not done this before as I had assumed I could only see survey
sections which were drawn in scraps. I can see how it is useful to be
able to render centrelines and stations for the entire system
regardless.

Footleg

On 7 January 2015 at 18:41, Bruce  wrote:
>>Or maybe I am not understanding what you mean by including the centreline
>> in the map
>
>
>
> Like this
>
> map DeckExtensionPlanMap -title "The Deck ExtensionUpper
> LevelsMiddle Earth CaveGreenlink System"
>
>  …
>
>  36-BigWednesdayPlan at MiddleEarth
>
>  36-BigWednesdayPlanCL at MiddleEarth
>
> …
>
> end map
>
>
>
> where the contributory maps look like this…
>
>
>
> map 36-BigWednesdayPlanCL -title "36-BigWednesday centreline Plan"
> -projection plan
>
>   36 #centreline survey
>
> endmap
>
>
>
> map 36-BigWednesdayPlan -title "36-BigWednesday Plan" -projection plan
>
>   36-BigWednesdayPlan-s1 #scraps
>
>   36-BigWednesdayPlan-s2
>
> endmap
>
>
>
> So what it is looking like, if the contributory maps are all derived from
> scraps (or maps in turn derived from scraps), then the altitude range is
> correct.
>
> But if there is a map that is centerline derived (ie has no scraps) then the
> altitude minima is set to zero.
>
>
>
> One other thing.
>
> All my tests so far use survex for loop closure.  I have not tried using
> Therion loop closure.
>
> And all my files are native Therion files – no survex imports.
>
>
>
> Bruce
>
>
>
> 
>
> From: therion-bounces at speleo.sk [mailto:therion-bounces at speleo.sk] On 
> Behalf
> Of Marco Menchise
> Sent: Thursday, 8 January 2015 3:05 a.m.
> To: List for Therion users
> Subject: Re: [Therion] Altitude colors range
>
>
>
> I checked and I can confirm what Bruce is saying. If you don't include
> centerline in map, the altitude range is correct.
>
>
>
> If you hide the centerline in the layout (leaving it in the map) the
> altitude range keeps starting from 0 m.
>
>
>
> Marco
>
>
>
>
>
> On Wed, Jan 7, 2015 at 2:52 PM, Footleg  wrote:
>
> I am not seeing this Bruce. I just tested with 5.3.16. My survey imports the
> centreline from a Survex .3d file however, so that might make a difference?
> Or maybe I am not understanding what you mean by including the centreline in
> the map. I turned off the centreline using 'symbol-hide line survey'. If I
> comment that out in my layout then the centreline is drawn in the map, but
> my altitude range still covers only the range of my scraps.
>
>
>
> Footleg
>
>
>
> On 5 January 2015 at 22:40, Bruce  wrote:
>
> OK, the problem is not the previews or the offsets, as it occurs in the map
> examples below regardless of presence of previews or offsets.
>
> What does seem to control whether the altitudes start at zero meters is
> whether the map definition includes a survey centerline.
>
> If part of map definition includes a survey centerline, then altitudes are
> coloured from zero meters to survey maxima (a bug?).
>
> If map definition has no survey centerline as part of it’s definition, then
> coloured from survey minima to survey maxima (correct behaviour).
>
> Hence I find this behaviour manifests in maps in progress, but when they are
> finished and I (usually) turn off the centerline maps, they correct
> themselves.
>
>  Bruce
>
>
>
>
> ___
> Therion mailing list
> Therion at speleo.sk
> http://mailman.speleo.sk/mailman/listinfo/therion
>

[Therion] Altitude colors range

[Bruce]

>Or maybe I am not understanding what you mean by including the centreline
in the map



Like this

map DeckExtensionPlanMap -title "The Deck ExtensionUpper
LevelsMiddle Earth CaveGreenlink System"

 .

 36-BigWednesdayPlan at MiddleEarth

 36-BigWednesdayPlanCL at MiddleEarth

. 

end map



where the contributory maps look like this.



map 36-BigWednesdayPlanCL -title "36-BigWednesday centreline Plan"
-projection plan

  36 #centreline survey

endmap



map 36-BigWednesdayPlan -title "36-BigWednesday Plan" -projection plan

  36-BigWednesdayPlan-s1 #scraps

  36-BigWednesdayPlan-s2

endmap



So what it is looking like, if the contributory maps are all derived from
scraps (or maps in turn derived from scraps), then the altitude range is
correct.

But if there is a map that is centerline derived (ie has no scraps) then the
altitude minima is set to zero.



One other thing.

All my tests so far use survex for loop closure.  I have not tried using
Therion loop closure.

And all my files are native Therion files - no survex imports.



Bruce



  _  

From: therion-bounces at speleo.sk [mailto:therion-boun...@speleo.sk] On Behalf
Of Marco Menchise
Sent: Thursday, 8 January 2015 3:05 a.m.
To: List for Therion users
Subject: Re: [Therion] Altitude colors range



I checked and I can confirm what Bruce is saying. If you don't include
centerline in map, the altitude range is correct.



If you hide the centerline in the layout (leaving it in the map) the
altitude range keeps starting from 0 m.



Marco





On Wed, Jan 7, 2015 at 2:52 PM, Footleg  wrote:

I am not seeing this Bruce. I just tested with 5.3.16. My survey imports the
centreline from a Survex .3d file however, so that might make a difference?
Or maybe I am not understanding what you mean by including the centreline in
the map. I turned off the centreline using 'symbol-hide line survey'. If I
comment that out in my layout then the centreline is drawn in the map, but
my altitude range still covers only the range of my scraps.



Footleg



On 5 January 2015 at 22:40, Bruce  wrote:

OK, the problem is not the previews or the offsets, as it occurs in the map
examples below regardless of presence of previews or offsets.

What does seem to control whether the altitudes start at zero meters is
whether the map definition includes a survey centerline.

If part of map definition includes a survey centerline, then altitudes are
coloured from zero meters to survey maxima (a bug?).

If map definition has no survey centerline as part of it's definition, then
coloured from survey minima to survey maxima (correct behaviour).

Hence I find this behaviour manifests in maps in progress, but when they are
finished and I (usually) turn off the centerline maps, they correct
themselves.

 Bruce



-- next part --
An HTML attachment was scrubbed...
URL: 
<http://mailman.speleo.sk/pipermail/therion/attachments/20150108/cf047746/attachment.html>

[Therion] Altitude colors range

[Bruce]

>If someone is working on this area, then it would be good to allow the
minimum and maximum altitude to be used for the colour range to be specified
in maps. 

I agree.



-- next part --
An HTML attachment was scrubbed...
URL: 

[Therion] Altitude colors range

[Martin Sluka]

7. 1. 2015 v 19:41, Bruce :

> So what it is looking like, if the contributory maps are all derived from 
> scraps (or maps in turn derived from scraps), then the altitude range is 
> correct.
> But if there is a map that is centerline derived (ie has no scraps) then the 
> altitude minima is set to zero.
> 

Only one question: do you have defined entrance?

m.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Therion] Altitude colors range

[Marco Menchise]

I checked and I can confirm what Bruce is saying. If you don't include
centerline in map, the altitude range is correct.

If you hide the centerline in the layout (leaving it in the map) the
altitude range keeps starting from 0 m.

Marco


On Wed, Jan 7, 2015 at 2:52 PM, Footleg  wrote:

> I am not seeing this Bruce. I just tested with 5.3.16. My survey imports
> the centreline from a Survex .3d file however, so that might make a
> difference? Or maybe I am not understanding what you mean by including the
> centreline in the map. I turned off the centreline using 'symbol-hide line
> survey'. If I comment that out in my layout then the centreline is drawn in
> the map, but my altitude range still covers only the range of my scraps.
>
> Footleg
>
> On 5 January 2015 at 22:40, Bruce  wrote:
>
>>   OK, the problem is not the previews or the offsets, as it occurs in
>> the map examples below regardless of presence of previews or offsets.
>>
>> What does seem to control whether the altitudes start at zero meters is
>> whether the map definition includes a survey centerline.
>>
>>
>>
>> If part of map definition includes a survey centerline, then altitudes
>> are coloured from zero meters to survey maxima (a bug?).
>>
>> If map definition has no survey centerline as part of it’s definition,
>> then coloured from survey minima to survey maxima (correct behaviour).
>>
>>
>>
>> Hence I find this behaviour manifests in maps in progress, but when they
>> are finished and I (usually) turn off the centerline maps, they correct
>> themselves.
>>
>>
>>
>> Bruce
>>
>>
>>  --
>>
>> *From:* therion-bounces at speleo.sk [mailto:therion-bounces at speleo.sk] 
>> *On
>> Behalf Of *Bruce
>> *Sent:* Sunday, 4 January 2015 10:42 a.m.
>> *To:* 'List for Therion users'
>> *Subject:* Re: [Therion] Altitude colors range
>>
>>
>>
>> Hmm, seems like there is an issue here.
>>
>> Comparing 5.3.10 map with 5.3.16 map as attached.
>>
>>
>>
>>  Not sure if it might be a side effect of something else, as I think the
>> colour range is OK sometimes (I think I noticed some irregularities with
>> 5.3.15 but assumed I was imagining things at the time) – maybe the preview
>> below triggers it?  - I might investigate further if I get time.
>>
>>
>>
>> Bruce
>>
>>
>>  --
>>
>> *From:* therion-bounces at speleo.sk [mailto:therion-bounces at speleo.sk] 
>> *On
>> Behalf Of *Marco Menchise
>> *Sent:* Saturday, 3 January 2015 8:45 a.m.
>> *To:* List for Therion users
>> *Subject:* [Therion] Altitude colors range
>>
>>
>>
>> Hello,
>>
>> I use to color maps by scrap altitude.
>>
>>
>>
>> Lately I noticed Therion color gradient starts from 0 m altitude to
>> maximum cave altitude. Because caves don't reach 0 m almost all color range
>> is unused and most scraps are colored with similar colors. If I remember
>> correctly some time ago Therion used all color range because color gradient
>> extended from minimum cave altitude (not 0 m) to maximum.
>>
>>
>>
>> Am I missing something? Is there a way to use all available colors?
>>
>>
>>
>> Thanks,
>>
>> Marco
>>
>> ___
>> Therion mailing list
>> Therion at speleo.sk
>> http://mailman.speleo.sk/mailman/listinfo/therion
>>
>>
>
> ___
> Therion mailing list
> Therion at speleo.sk
> http://mailman.speleo.sk/mailman/listinfo/therion
>
>
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://mailman.speleo.sk/pipermail/therion/attachments/20150107/f251c14f/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 123853 bytes
Desc: not available
URL: 
<http://mailman.speleo.sk/pipermail/therion/attachments/20150107/f251c14f/attachment.jpg>
-- next part --
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 123727 bytes
Desc: not available
URL: 
<http://mailman.speleo.sk/pipermail/therion/attachments/20150107/f251c14f/attachment-0001.jpg>

[Therion] Altitude colors range

[Footleg]

I am not seeing this Bruce. I just tested with 5.3.16. My survey imports
the centreline from a Survex .3d file however, so that might make a
difference? Or maybe I am not understanding what you mean by including the
centreline in the map. I turned off the centreline using 'symbol-hide line
survey'. If I comment that out in my layout then the centreline is drawn in
the map, but my altitude range still covers only the range of my scraps.

Footleg

On 5 January 2015 at 22:40, Bruce  wrote:

>   OK, the problem is not the previews or the offsets, as it occurs in the
> map examples below regardless of presence of previews or offsets.
>
> What does seem to control whether the altitudes start at zero meters is
> whether the map definition includes a survey centerline.
>
>
>
> If part of map definition includes a survey centerline, then altitudes are
> coloured from zero meters to survey maxima (a bug?).
>
> If map definition has no survey centerline as part of it’s definition,
> then coloured from survey minima to survey maxima (correct behaviour).
>
>
>
> Hence I find this behaviour manifests in maps in progress, but when they
> are finished and I (usually) turn off the centerline maps, they correct
> themselves.
>
>
>
> Bruce
>
>
>  --
>
> *From:* therion-bounces at speleo.sk [mailto:therion-bounces at speleo.sk] *On
> Behalf Of *Bruce
> *Sent:* Sunday, 4 January 2015 10:42 a.m.
> *To:* 'List for Therion users'
> *Subject:* Re: [Therion] Altitude colors range
>
>
>
> Hmm, seems like there is an issue here.
>
> Comparing 5.3.10 map with 5.3.16 map as attached.
>
>
>
>  Not sure if it might be a side effect of something else, as I think the
> colour range is OK sometimes (I think I noticed some irregularities with
> 5.3.15 but assumed I was imagining things at the time) – maybe the preview
> below triggers it?  - I might investigate further if I get time.
>
>
>
> Bruce
>
>
>  --
>
> *From:* therion-bounces at speleo.sk [mailto:therion-bounces at speleo.sk] *On
> Behalf Of *Marco Menchise
> *Sent:* Saturday, 3 January 2015 8:45 a.m.
> *To:* List for Therion users
> *Subject:* [Therion] Altitude colors range
>
>
>
> Hello,
>
> I use to color maps by scrap altitude.
>
>
>
> Lately I noticed Therion color gradient starts from 0 m altitude to
> maximum cave altitude. Because caves don't reach 0 m almost all color range
> is unused and most scraps are colored with similar colors. If I remember
> correctly some time ago Therion used all color range because color gradient
> extended from minimum cave altitude (not 0 m) to maximum.
>
>
>
> Am I missing something? Is there a way to use all available colors?
>
>
>
> Thanks,
>
> Marco
>
> ___
> Therion mailing list
> Therion at speleo.sk
> http://mailman.speleo.sk/mailman/listinfo/therion
>
>
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://mailman.speleo.sk/pipermail/therion/attachments/20150107/d0f52d3f/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 123853 bytes
Desc: not available
URL: 
<http://mailman.speleo.sk/pipermail/therion/attachments/20150107/d0f52d3f/attachment.jpg>
-- next part --
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 123727 bytes
Desc: not available
URL: 
<http://mailman.speleo.sk/pipermail/therion/attachments/20150107/d0f52d3f/attachment-0001.jpg>

[Therion] Altitude colors range

[Footleg]

If someone is working on this area, then it would be good to allow the
minimum and maximum altitude to be used for the colour range to be
specified in maps. I currently do this via a hack in my maps, including a
scrap containing two artificial fixed survey stations at the min. and max.
altitudes I want the map to use for colouring. Provided the rest of the
scraps in the map are in this range then the entire map is coloured the
same regardless of which scraps I include. So I can generate a map of part
of the cave with the same colours as the map of the entire cave. Otherwise
maps of small areas of the cave get coloured with very different scrap
colours due to the small altitude range of the scraps in the map.

Footleg

On 5 January 2015 at 22:40, Bruce  wrote:

>   OK, the problem is not the previews or the offsets, as it occurs in the
> map examples below regardless of presence of previews or offsets.
>
> What does seem to control whether the altitudes start at zero meters is
> whether the map definition includes a survey centerline.
>
>
>
> If part of map definition includes a survey centerline, then altitudes are
> coloured from zero meters to survey maxima (a bug?).
>
> If map definition has no survey centerline as part of it’s definition,
> then coloured from survey minima to survey maxima (correct behaviour).
>
>
>
> Hence I find this behaviour manifests in maps in progress, but when they
> are finished and I (usually) turn off the centerline maps, they correct
> themselves.
>
>
>
> Bruce
>
>
>  --
>
> *From:* therion-bounces at speleo.sk [mailto:therion-bounces at speleo.sk] *On
> Behalf Of *Bruce
> *Sent:* Sunday, 4 January 2015 10:42 a.m.
> *To:* 'List for Therion users'
> *Subject:* Re: [Therion] Altitude colors range
>
>
>
> Hmm, seems like there is an issue here.
>
> Comparing 5.3.10 map with 5.3.16 map as attached.
>
>
>
>  Not sure if it might be a side effect of something else, as I think the
> colour range is OK sometimes (I think I noticed some irregularities with
> 5.3.15 but assumed I was imagining things at the time) – maybe the preview
> below triggers it?  - I might investigate further if I get time.
>
>
>
> Bruce
>
>
>  --
>
> *From:* therion-bounces at speleo.sk [mailto:therion-bounces at speleo.sk] *On
> Behalf Of *Marco Menchise
> *Sent:* Saturday, 3 January 2015 8:45 a.m.
> *To:* List for Therion users
> *Subject:* [Therion] Altitude colors range
>
>
>
> Hello,
>
> I use to color maps by scrap altitude.
>
>
>
> Lately I noticed Therion color gradient starts from 0 m altitude to
> maximum cave altitude. Because caves don't reach 0 m almost all color range
> is unused and most scraps are colored with similar colors. If I remember
> correctly some time ago Therion used all color range because color gradient
> extended from minimum cave altitude (not 0 m) to maximum.
>
>
>
> Am I missing something? Is there a way to use all available colors?
>
>
>
> Thanks,
>
> Marco
>
> ___
> Therion mailing list
> Therion at speleo.sk
> http://mailman.speleo.sk/mailman/listinfo/therion
>
>
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://mailman.speleo.sk/pipermail/therion/attachments/20150107/4495f8e0/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 123727 bytes
Desc: not available
URL: 
<http://mailman.speleo.sk/pipermail/therion/attachments/20150107/4495f8e0/attachment.jpg>
-- next part --
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 123853 bytes
Desc: not available
URL: 
<http://mailman.speleo.sk/pipermail/therion/attachments/20150107/4495f8e0/attachment-0001.jpg>

[Therion] Altitude colors range

[Bruce]

OK, the problem is not the previews or the offsets, as it occurs in the map
examples below regardless of presence of previews or offsets.

What does seem to control whether the altitudes start at zero meters is
whether the map definition includes a survey centerline.



If part of map definition includes a survey centerline, then altitudes are
coloured from zero meters to survey maxima (a bug?).

If map definition has no survey centerline as part of it's definition, then
coloured from survey minima to survey maxima (correct behaviour).



Hence I find this behaviour manifests in maps in progress, but when they are
finished and I (usually) turn off the centerline maps, they correct
themselves.



Bruce



  _  

From: therion-bounces at speleo.sk [mailto:therion-boun...@speleo.sk] On Behalf
Of Bruce
Sent: Sunday, 4 January 2015 10:42 a.m.
To: 'List for Therion users'
Subject: Re: [Therion] Altitude colors range



Hmm, seems like there is an issue here.

Comparing 5.3.10 map with 5.3.16 map as attached.







Not sure if it might be a side effect of something else, as I think the
colour range is OK sometimes (I think I noticed some irregularities with
5.3.15 but assumed I was imagining things at the time) - maybe the preview
below triggers it?  - I might investigate further if I get time.



Bruce



  _  

From: therion-bounces at speleo.sk [mailto:therion-boun...@speleo.sk] On Behalf
Of Marco Menchise
Sent: Saturday, 3 January 2015 8:45 a.m.
To: List for Therion users
Subject: [Therion] Altitude colors range



Hello,

I use to color maps by scrap altitude. 



Lately I noticed Therion color gradient starts from 0 m altitude to maximum
cave altitude. Because caves don't reach 0 m almost all color range is
unused and most scraps are colored with similar colors. If I remember
correctly some time ago Therion used all color range because color gradient
extended from minimum cave altitude (not 0 m) to maximum. 



Am I missing something? Is there a way to use all available colors?



Thanks,

Marco

-- next part --
An HTML attachment was scrubbed...
URL: 
<http://mailman.speleo.sk/pipermail/therion/attachments/20150106/b74d1146/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 123727 bytes
Desc: image001.jpg
URL: 
<http://mailman.speleo.sk/pipermail/therion/attachments/20150106/b74d1146/attachment.jpg>
-- next part --
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 123853 bytes
Desc: image002.jpg
URL: 
<http://mailman.speleo.sk/pipermail/therion/attachments/20150106/b74d1146/attachment-0001.jpg>

[Therion] Altitude colors range

[Bruce]

Hmm, seems like there is an issue here.

Comparing 5.3.12 map with 5.3.16 map as attached.







Not sure if it might be a side effect of something else, as I think the
colour range is OK sometimes (I think I noticed some irregularities with
5.3.15 but assumed I was imagining things at the time) - maybe the preview
below triggers it?  - I might investigate further if I get time.



Bruce



  _  

From: therion-bounces at speleo.sk [mailto:therion-boun...@speleo.sk] On Behalf
Of Marco Menchise
Sent: Saturday, 3 January 2015 8:45 a.m.
To: List for Therion users
Subject: [Therion] Altitude colors range



Hello,

I use to color maps by scrap altitude. 



Lately I noticed Therion color gradient starts from 0 m altitude to maximum
cave altitude. Because caves don't reach 0 m almost all color range is
unused and most scraps are colored with similar colors. If I remember
correctly some time ago Therion used all color range because color gradient
extended from minimum cave altitude (not 0 m) to maximum. 



Am I missing something? Is there a way to use all available colors?



Thanks,

Marco

-- next part --
An HTML attachment was scrubbed...
URL: 
<http://mailman.speleo.sk/pipermail/therion/attachments/20150104/267c6489/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 123727 bytes
Desc: image002.jpg
URL: 
<http://mailman.speleo.sk/pipermail/therion/attachments/20150104/267c6489/attachment.jpg>
-- next part --
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 123853 bytes
Desc: image003.jpg
URL: 
<http://mailman.speleo.sk/pipermail/therion/attachments/20150104/267c6489/attachment-0001.jpg>

[Therion] Altitude colors range

[Marco Menchise]

Hello,
I use to color maps by scrap altitude.

Lately I noticed Therion color gradient starts from 0 m altitude to maximum
cave altitude. Because caves don't reach 0 m almost all color range is
unused and most scraps are colored with similar colors. If I remember
correctly some time ago Therion used all color range because color gradient
extended from minimum cave altitude (not 0 m) to maximum.

Am I missing something? Is there a way to use all available colors?

Thanks,
Marco
-- next part --
An HTML attachment was scrubbed...
URL: 

[Therion] Altitude colours

[Stacho Mudrak]

Hi John,

I am afraid, using your own color scheme for altitude is not yet finished -
although it is the last thing I have been working on, so hopefully, it will
be finished soon.

Currently, there is only one predefined spectrum.

S.

On 18 September 2014 19:58, John Stevens  wrote:

>   Is there somewhere I can change the colours for altitude?
> Can I choose my own colour spectrum and increase the number of colours
> used.
> How many are there at present?
>
> John S
>
> ___
> Therion mailing list
> Therion at speleo.sk
> http://mailman.speleo.sk/mailman/listinfo/therion
>
>
-- next part --
An HTML attachment was scrubbed...
URL: 

[Therion] Altitude colours

[John Stevens]

Is there somewhere I can change the colours for altitude?
Can I choose my own colour spectrum and increase the number of colours used.
How many are there at present?

John S
-- next part --
An HTML attachment was scrubbed...
URL: 

[Therion] Altitude Units

[Dave Clucas]

Altitude Units
Sorry but I don't understand this answer. My problem is not that I want to 
change the units that the altitude is displayed in but that I want to display 
the units as a suffix after the value as in "1562m" or "1562 m".

It sounds as though I've misunderstood the meaning of this paragraph in thbook

altitude: the value specied is the altitude dierence from the nearest station. 
If the
altitude value is prexed by \fix" (e.g. -value [fix 1300]), this value is used 
as an
absolute altitude. The value can optionally be followed by length units.


> Message: 4
> Date: Wed, 10 Feb 2010 20:07:08 +0100
> From: Stacho Mudrak 
> Subject: Re: [Therion] Therion bugs
> To: List for Therion users 
> Message-ID:
>   <55e5b7b51002101107u1bacc7fy40ade323f0213a73 at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
> 
>> I've had a couple of problems
>> 1. I put an altitude point at the entrance to a cave. According to thbook 
>> this can be optionally followed by units but no units show on the output 
>> pdf. I tried the following options but none of them worked
>> -value [fix 1562 meter]
>> -value [fix 1562 metre]
>> -value [fix 1562 m]
> 
> These units are parsed when file is read. On the output, all altitudes
> are converted to meters, regardless of input units.
> 
> Best regards, S.
> 
> 
> --
> 
> ___
> Therion mailing list
> Therion at speleo.sk
> http://mailman.speleo.sk/mailman/listinfo/therion
> 
> 
> End of Therion Digest, Vol 51, Issue 10
> ***



Dave Clucas
email:dave at daveclucas.com 
Website: http://daveclucas.com
 http://mycaves.org
Skype: daveclucas




-- next part --
An HTML attachment was scrubbed...
URL: 

[Therion] Altitude

[Martin Budaj]

On Mon, Jun 2, 2008 at 9:35 PM, Ben Cooper  wrote:
> "scale" works with point label, though.  Why do you say it is ignored for
> labels?

Well, it used to be ignored (therion functionality sometimes surprises
even the authors ;-). Now we will implement it consistently also for
altitude.

Martin

[Therion] Altitude

[Ben Cooper]

Thanks Martin.  That would be fabulous.
- Ben 

-Original Message-
From: therion-bounces at speleo.sk [mailto:therion-boun...@speleo.sk] On Behalf
Of Martin Budaj
Sent: 06 June 2008 20:55
To: therion at speleo.sk
Subject: Re: [Therion] Altitude

On Mon, Jun 2, 2008 at 9:35 PM, Ben Cooper  wrote:
> "scale" works with point label, though.  Why do you say it is ignored 
> for labels?

Well, it used to be ignored (therion functionality sometimes surprises even
the authors ;-). Now we will implement it consistently also for altitude.

Martin
___
Therion mailing list
Therion at speleo.sk
http://www.speleo.sk/mailman/listinfo/therion

[Therion] Altitude

[Martin Budaj]

On Tue, May 27, 2008 at 10:22 PM, Ben Cooper  wrote:
> I've noticed that the "scale" option does not appear to work with the
> "altitude" point symbol.  Is there any particular reason for that?

It belongs to labels, for which the scale option is ignored. Anyway,
did you try to scale the dot or the text?

Martin

[Therion] Altitude

[Stacho Mudrak]

Either you can use altitude option for a wall point - just enter
"altitude ." to the line point options text editor, as Martin has
written. This way we prefer. Or you can add -align option to your
label - e.g. "-align tl" would probably help in your case (tl means
top left).

Regards, S.

2008/5/6 Martin Sluka :
>
>
>
> On 6.5.2008, at 22:55, Ben Cooper wrote:
>
>
>
>
> Can anyone advise me on this one?
> The simplest way is to add to point of line "wall" the option "altitude ."
> You should find in section "Line points" the black rectangle. Highlight the
> point of wall you want to add the altitude and write "altitude ." there.
>
> "altitude  . can be speci ed only with the wall type. This option
> creates an
> altitude label on the wall. All altitudes are exported as a di erence
> against grid Z
> origin (which is 0 by default). If the value is speci ed, it gives the
> altitude di erence
> of the point on the wall relative to the nearest station. The value can be
> pre xed by a
> keyword \fix", then no nearest station is taken into consideration; the
> absolute given
> value is used instead. Units can follow the value. Examples: +4, [+4 m],
> [fix 1510
> m]."
>
>
> "7 General altitude label. All altitudes are exported as a di erence against
> grid Z origin (which is 0
> by default). To display altitude on the passage wall, use altitude option
> for any line point of the
> passage wall."
>
> M.
>
>
> ___
>  Therion mailing list
>  Therion at speleo.sk
>  http://www.speleo.sk/mailman/listinfo/therion
>
>

[Therion] Altitude

[ca...@caver.plus.com]

> just enter
> "altitude ."

Thanks Stacho.  I had not realised the " ." was required - this was not
clear from The Book.  I had struggled to get this to work.  The align
option for points is also really useful - again I had not spotted this one
before!
- Ben

[Therion] Altitude

[Martin Sluka]

On 6.5.2008, at 22:55, Ben Cooper wrote:

>
> Can anyone advise me on this one?

The simplest way is to add to point of line "wall" the option  
"altitude ." You should find in section "Line points" the black  
rectangle. Highlight the point of wall you want to add the altitude  
and write "altitude ." there.

"altitude  . can be speci ed only with the wall type. This  
option creates an
altitude label on the wall. All altitudes are exported as a di erence  
against grid Z
origin (which is 0 by default). If the value is speci ed, it gives  
the altitude di erence
of the point on the wall relative to the nearest station. The value  
can be pre xed by a
keyword \fix", then no nearest station is taken into consideration;  
the absolute given
value is used instead. Units can follow the value. Examples: +4, [+4  
m], [fix 1510
m]."

"7 General altitude label. All altitudes are exported as a di erence  
against grid Z origin (which is 0
by default). To display altitude on the passage wall, use altitude  
option for any line point of the
passage wall."

M.


-- next part --
An HTML attachment was scrubbed...
URL: 

-- next part --
A non-text attachment was scrubbed...
Name: Picture 1.png
Type: image/png
Size: 17049 bytes
Desc: not available
URL: 

[Therion] Altitude

[Ben Cooper]

I'm trying to put "altitude" points into my map.  I've used point altitude
successfully, but the number over-writes the cave.  I've found I can move
the point outside the cave outline, and it still reports the correct
altitude, but it the "dot" appears now outside the cave, of course, as
attached.  









Is there a way of specifying the position of the altitude "point" within the
cave passage, but moving the text outside?  I could do this manually of
course with a point label, but then the altitude data would not be computed
from the centreline, so not ideal.  



Can anyone advise me on this one?
- Ben



-- next part --
An HTML attachment was scrubbed...
URL: 

-- next part --
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 6789 bytes
Desc: not available
URL: