BeniI think that I tend to arrange my projects as you have described. Are you
using the 'break' statement in map definitions to enforce the separation of
different levels within the cave?If you are, you should not experience random
rendering, and it will solve your problem most of the time. The situation where
it fails is when one of your regions is generaly lower than another, but there
is for example one piece that is higher than and overlaps that other region. In
this situation I think that we have to rearrange the map structure (just
locally), which is, I admit, philosophically painful. Have I understood your
original correctly? BruceSent from my Samsung Galaxy smartphone.
-------- Original message --------From: Benedikt Hallinger <[email protected]>
Date: 31/05/19 01:54 (GMT+12:00) To: List for Therion users
<[email protected]> Subject: [Therion] Sorting scraps/maps by height in default
mode 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" command in the region.th
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
[email protected]https://mailman.speleo.sk/listinfo/therion
_______________________________________________
Therion mailing list
[email protected]
https://mailman.speleo.sk/listinfo/therion
