[Therion] Sorting scraps/maps by height in default mode

[Benedikt Hallinger]

Hi Stacho, hello Bruce,
you understood correctly.

The problem here is, we are talking about uncorrelated maps and scraps. 
They are from several subsurveys.

is there any kind of debug output i can activate to get the average 
scrap height?

And is the sorting done scrap-wise, or are the maps averaged?


Am 2019-05-30 22:27, schrieb Stacho Mudrak:
> Hello,
> 
> if you select just survey, then all maps consisting of scraps in this
> and sub-surveys should be ordered by average altitude. But this may
> easily cause that some overlapping is not done correctly. But it is
> also possible, there is some bug and it is not done correctly. Are you
> able to post some minimalistic sample, where depth sort fails?
> 
> The only way how to manually order maps in the output is to create
> upper-level maps (in your case probably what you mean by
> <region>-Hautplan) consisting of lower level maps in the correct
> order.
> 
> HTH, S.
> 
> On Thu, 30 May 2019 at 15:55, Benedikt Hallinger <beni at hallinger.org>
> wrote:
> 
>> Hello there,
>> i have a very large dataset here. It is organised by regions like
>> this
>> (but much more leaf objects and regions):
>> 
>> =====snip=====
>> - survey TheCave
>> - survey RegionWest
>> - survey 1
>> - survey 3
>> - survey 5
>> - survey RegionEast
>> - survey 2
>> - survey 4
>> - survey 6
>> =====snap=====
>> 
>> I currently work from bottom to up, that is i draw the individual
>> surveys as scraps, based on original material (sometimes they are
>> really
>> large and cosnsist of several many scraps).
>> 
>> In each of they leaf surveys (the numbered ones) i make by
>> convention a
>> map called "<n>-Hauptplan". The main idea is that every leaf survey
>> can
>> be treaten modular and that i can compile varoius maps at upper
>> levels
>> (i.e regions).
>> 
>> Currently, the regions have no "<region>-Hautplan". When i use
>> "select
>> RegionWest.TheCave", therion is instructed to select all scraps
>> below
>> it. For the most part, this works like intendet and the overlappings
>> are
>> calculated correctly. There are some places however, where the upper
>> 
>> part of the passage is rendered below the lower part, which is
>> wrong.
>> This is with about 10-15% of the passages (so most is already ok).
>> 
>> I know from the manuals that therion does this "randomly" so there
>> is no
>> real way to adjust this from my perspective (placing the "input 2.th
>> [1]"
>> command in the region.th [2] file, wich then inputs the scraps etc,
>> lower in
>> the list does not help - it seems random where it is).
>> I think, however, that it would be a very great addition, if there
>> would
>> be some code in the renderer, that sorts the vertical presentation
>> of
>> the scraps/maps by average altitude of said scrap/map, and that this
>> 
>> behavior is controllable by some configuration (cmdline option, or
>> even
>> better, thconfig parameter).
>> => Is there maybe already something hidden like this i don't know so
>> 
>> far?
>> That would be very great, because when i look at the dataset, i face
>> 
>> about 30-50 hours producing correctly manually sorted handcrafted
>> maps
>> at the region level...
>> 
>> Sincerely, Beni
>> _______________________________________________
>> Therion mailing list
>> Therion at speleo.sk
>> https://mailman.speleo.sk/listinfo/therion
> 
> 
> Links:
> ------
> [1] http://2.th
> [2] http://region.th
> _______________________________________________
> Therion mailing list
> Therion at speleo.sk
> https://mailman.speleo.sk/listinfo/therion