Hello, I currently play around with the layer feature. Currently it is so, that each "select"ed map goes in its own layer, which is fine. In my data there are nested maps however. They get collated into one big layer. I don't know PDF specifics, but it would be very handy to have "nested" layers, i.e. submaps as separate layers in the main layer. If sublayersa re not possible, it would be cool to have an optional option at the export config command to instruct therion to not collate submaps into a bigger layer, but add each map as independent layer. Something like this: ---- therion source ---- map A A1 A2 endmap map B B1 endmap map A1 scrap1 endmap map A2 scrap2 endmap map B1 scrap3 endmap ------------------------ ----- PDF layer list ----- - A + A1 + A2 - B + B1 ---------------------------
On 23/11/2021 15:08, Benedikt Hallinger wrote:
I don't know PDF specifics, but it would be very handy to have "nested" layers, i.e. submaps as separate layers in the main layer.
That would be very useful, don't know if it is possible
If sublayersa re not possible, it would be cool to have an optional option at the export config command to instruct therion to not collate submaps into a bigger layer, but add each map as independent layer.
If I understand correctly what you are after I think what you maybe looking for are the options used with select. I used -map-level 2 to get what you describe. Other options are recursive <on/off> and chapter-level <number> I cannot say I really understand these fully, however trial and error got me there Andrew
Yes, exactly, when i use "select" and fetch the maps that way, it generates layers as expected. However, in this instance i just have one big "map" element, but it would be nice if i could have the submaps also as distinct layers. Am 2021-11-23 16:41, schrieb Andrew Atkinson:
On 23/11/2021 15:08, Benedikt Hallinger wrote:
I don't know PDF specifics, but it would be very handy to have "nested" layers, i.e. submaps as separate layers in the main layer.
That would be very useful, don't know if it is possible
If sublayersa re not possible, it would be cool to have an optional option at the export config command to instruct therion to not collate submaps into a bigger layer, but add each map as independent layer.
If I understand correctly what you are after I think what you maybe looking for are the options used with select. I used -map-level 2 to get what you describe.
Other options are
recursive <on/off> and chapter-level <number>
I cannot say I really understand these fully, however trial and error got me there
Andrew _______________________________________________ Therion mailing list Therion@speleo.sk https://mailman.speleo.sk/listinfo/therion
On 23/11/2021 15:49, Benedikt Hallinger wrote:
es, exactly, when i use "select" and fetch the maps that way, it generates layers as expected. However, in this instance i just have one big "map" element, but it would be nice if i could have the submaps also as distinct layers.
With a map definition in th file map mymap map1 map2 map3 endmap then in thconfig select mymap should give you map1, map2.. as leyers in pdf if you also have in a th file map map1 mapA mapB mapC endmap select mymap -maplevel 2 should give you layers of mapA, mapB... In your example you had scraps, I don't think the map-level works on scraps. If I have a survey with a single survey I always make it into a map, I find this makes things easier in the end. I also do this if In have many scraps that I want on several layers map SingleScrap SingleScrapA endmap (I have no idea why scraps cannot just be treated as maps, it's probably something to do with the coding, however it is easy to just turn them into maps, I've not found any downside, well apart from a little more typing and a larger map tree) Andrew
Hi, no, i really have submaps in my example. mymap in my case is defined in my thconfig file, and it references a mainmap as submap. That submap again is a collection of other submaps, that finally contain scraps: ------------- source map 164-Grundriss -title "Mappe 164: Wandaugenlabyrinth Ost" #preview above 172-Hauptplan@172.Wandaugenlabyrinth.Hirlatzhoehle preview above 162-Hauptplan@162.Wandaugenlabyrinth.Hirlatzhoehle preview above 180-Hauptplan@180.Wandaugenlabyrinth.Hirlatzhoehle preview above 170-Hauptplan@170.Wandaugenlabyrinth.Hirlatzhoehle preview above 171-Hauptplan@171.Wandaugenlabyrinth.Hirlatzhoehle 164-Hauptplan@164.Wandaugenlabyrinth.Hirlatzhoehle #<-- this contains several other maps, which finally contain scraps endmap endsource ----------------
select 164-Grundriss -map-level 2 This works, but removes the previews (from 164-Grundriss) and also the offsets defined in 164-Hauptplan. I also tried "select 164-Grundriss -map-level basic" with the same result.
Am 2021-11-23 17:01, schrieb Andrew Atkinson:
On 23/11/2021 15:49, Benedikt Hallinger wrote:
es, exactly, when i use "select" and fetch the maps that way, it generates layers as expected. However, in this instance i just have one big "map" element, but it would be nice if i could have the submaps also as distinct layers.
With a map definition in th file
map mymap map1 map2 map3 endmap
then in thconfig
select mymap
should give you map1, map2.. as leyers in pdf
if you also have in a th file
map map1 mapA mapB mapC endmap
select mymap -maplevel 2
should give you layers of mapA, mapB...
In your example you had scraps, I don't think the map-level works on scraps. If I have a survey with a single survey I always make it into a map, I find this makes things easier in the end. I also do this if In have many scraps that I want on several layers
map SingleScrap SingleScrapA endmap
(I have no idea why scraps cannot just be treated as maps, it's probably something to do with the coding, however it is easy to just turn them into maps, I've not found any downside, well apart from a little more typing and a larger map tree)
Andrew _______________________________________________ Therion mailing list Therion@speleo.sk https://mailman.speleo.sk/listinfo/therion
On Tue, Nov 23, 2021 at 4:42 PM Andrew Atkinson <andrew@wotcc.org.uk> wrote:
On 23/11/2021 15:08, Benedikt Hallinger wrote:
I don't know PDF specifics, but it would be very handy to have "nested" layers, i.e. submaps as separate layers in the main layer.
That would be very useful, don't know if it is possible
There is some support for a tree-like hierarchy of the optional content layers in the PDF specification, but you can't select/unselect a group of sublayers at once. See the attached picture for an illustration: you can change the visibility of the lowest-level maps (the "leafs") only, not the higher-level maps or groups (the "branches"). So it's not very helpful in this case except for having some labels indicating the hierarchical structure of maps. If all the tree was interactive, we could simply expand it to all sub-maps to have complete and easy control of the displayed content. Martin
Thank you Martin, for clarification!
Am 30.11.2021 um 20:49 schrieb Martin Budaj <m.budaj@gmail.com>:
On Tue, Nov 23, 2021 at 4:42 PM Andrew Atkinson <andrew@wotcc.org.uk> wrote:
On 23/11/2021 15:08, Benedikt Hallinger wrote:
I don't know PDF specifics, but it would be very handy to have "nested" layers, i.e. submaps as separate layers in the main layer.
That would be very useful, don't know if it is possible
There is some support for a tree-like hierarchy of the optional content layers in the PDF specification, but you can't select/unselect a group of sublayers at once. See the attached picture for an illustration: you can change the visibility of the lowest-level maps (the "leafs") only, not the higher-level maps or groups (the "branches"). So it's not very helpful in this case except for having some labels indicating the hierarchical structure of maps. If all the tree was interactive, we could simply expand it to all sub-maps to have complete and easy control of the displayed content.
Martin
_______________________________________________ Therion mailing list Therion@speleo.sk https://mailman.speleo.sk/listinfo/therion
participants (3)
-
Andrew Atkinson -
Benedikt Hallinger -
Martin Budaj