[Therion] maps on off feature characteristics

[Bruce Mutton]

I've just been playing with the new maps on/off feature a little more.
These are just some observations.

There seems to be a bug regarding map altitudes in all cases, and scrap
altitudes where the scraps are empty.  On the other hand it is a good way to
highlight the existence of empty scraps!

 

The notes below may not be particularly coherent, but together with the
attached log files, you should be able to figure out what is going on.

Setting maps to off quadruples compile time and increases pdf size by 15
times (not sure why that should be).

 

Maps off

On running a project with 614 scraps reported;

This log entry was caused by an empty scrap definition, regardless of
whether the empty scrap appears in a map definition

S
-899999999999999990000000000000000000000000000000000000000000000000000000000
0000000000000000000000000.00  04-BangAndBeyondPlan-s2 at BlackSabbath ()

ie

scrap 04-BangAndBeyondPlan-s2 -projection plan -scale [0 0 787.4 787.4 0 0
10 10 m]

endscrap

It seems I have 16 empty scraps in that project, a legacy of using
topparser, and not always using all of the scrap definitions that it
creates.

 

Maps on

On running same project with 254 scraps/maps reported;

1. Empty Scrap causes map that contains it not to appear in log, sometimes

04-BangAndBeyondPlan-s2 at BlackSabbath is empty and for some reason the
following map is not reported in the log file at all.

 

map 04-BangAndBeyondPlan -title "04 beyond the capped rock - black sabbath
plan" -projection plan

                04-BangAndBeyondPlan-s1

                04-BangAndBeyondPlan-s2

endmap

 

2. All maps are reported with elevation of;

M
-899999999999999990000000000000000000000000000000000000000000000000000000000
0000000000000000000000000.00

 

3.  Unexplained empty 'scrap' reported at high altitude.  Looking at my
data, I cannot explain why this might happen.  In the 254 lines, there are
only two of these.

 

M
-899999999999999990000000000000000000000000000000000000000000000000000000000
0000000000000000000000000.00 61-AngelicaPlan at MiddleEarth (61 Angelica plan)

S   473.40  61-AngelicaPlan-s1 at MiddleEarth ()

S   489.54  61-AngelicaPlan-s2 at MiddleEarth ()

S  1219.69  @ ()

 

map 61-AngelicaPlan -title "61 Angelica plan" -projection plan

                61-AngelicaPlan-s1 #9C start surveying up pitch

                61-AngelicaPlan-s2 # to base of 20C

endmap

 

4. Similar things happen with projected elevation outputs, but there are
many more of empty report lines, as in 3. above, and the altitudes reported
seem somewhat random and just wrong.  I wonder if the altitudes are really
some measure of distance into or out of the 'page'?

 

Behaviours seem to be the same whether maps or atlas are exported.  Very
nice for disabling passage offsets and previews.

 

Bruce

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.speleo.sk/pipermail/therion/attachments/20190628/fdce4045/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: therion-maps on.log
Type: application/octet-stream
Size: 123456 bytes
Desc: not available
URL: <http://mailman.speleo.sk/pipermail/therion/attachments/20190628/fdce4045/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: therion-maps off.log
Type: application/octet-stream
Size: 152594 bytes
Desc: not available
URL: <http://mailman.speleo.sk/pipermail/therion/attachments/20190628/fdce4045/attachment-0001.obj>