March 2023 - Therion

kml color
by Philippe Vernant 25 Oct '25

25 Oct '25

Hi guys, I can’t find a way to change the light greyish color of the kml export except by going into the kml file and change it after it has been created. Is there a way to specify the color when creating the kml ? Thanks, Phil

3 3

Transparency and connection issue
by david Le berre 23 Mar '23

23 Mar '23

Dear All New comer on this forum and new user of Therion for 18 months, I'm currently stucked by 2 issues that are certainly obvious for most of you but after lots of trials I dare to ask you!!! 1- Transparency on colour filled areas: Since I have colored some areas and customized some colors as well, I have lost transparency on overlapping cavities. Despite many trials in the layouts no success.I use in my layout for exemple: #clay-orange def a_clay (expr p) = T:=identity; thfill p withcolor (0.96, 0.82, 0.55); enddef; Result it looks better but it is far more difficult to understand some overlapping areas, see hereunder. I guess if I define a special pattern including 50% of colour and 50% of non-colored pixel it could work but I'm not skilled enough to play with metapost.Any ideas to have the transparency back? 2. Connexions lines for offseted scraps:My project covers a 4 kms cave that I have splitted into 4 sub-projects (called networks), I work in each network and gather them to get final export, usually I use connexion point in the scrap. - Network 1 is above Network 2, therefore in the final presentation I offset Network 2 - Network 2 includes itself offseted areas which appear well when I work on export of Network 2 only. When I compile the global project all connexion's doted lines inside network 2 appears then linked to the shadow of the network 2 offseted from the Network 1 instead of staying linked to the Network 2 representation, result is hawfull with dotted lines crossing every where and ending in the shadow area.Any ideas to maintain local connexion dotted line where they were at the beginning? Thanks in advance David

4 23

3 Map-connection issue - effect of map-level
by Bruce Mutton 19 Mar '23

19 Mar '23

From: Bruce Mutton <bruce(a)tomo.co.nz> Sent: Tuesday, 12 July 2022 21:08 To: 'List for Therion users' <therion(a)speleo.sk> Subject: Map-connection issue - effect of map-level And noting that map-level progressively chops out the offsets, starting with the level-1 offset. Undocumented feature for export of maps? At least it does not change the map-connection line behaviour. export map -projection plan \ -layout LayoutMapThisCave \ -layout LayoutMapThisCavePlan \ -output ../Output/PlanMap.pdf select PlanMap@Cave -map-level 0 select PlanMap@Cave -map-level 1 select PlanMap@Cave -map-level 2 select PlanMap@Cave -map-level 3 select PlanMap@Cave -map-level 4 (and -map-level basic and -map-level 5 etc) Bruce

3 3

2 Map-connection issue - Going to four levels - Offset tests SAMD-ITF-IS example
by Bruce Mutton 13 Mar '23

13 Mar '23

From: Bruce Mutton <bruce(a)tomo.co.nz> Sent: Monday, 11 July 2022 15:02 To: 'List for Therion users' <therion(a)speleo.sk> Subject: Map-connection issue - Going to four levels - Offset tests SAMD-ITF-IS example I managed to squeeze five levels of maps out of my example, going to 4 levels of offset (offset of offset of offset of offset). All of the offsets are correctly made, relative to their parent maps. However the line created by point map-connection is only correctly originating from its parent map at the most deeply nested level of offset and at the 1st level offset. At all other offset levels, the map-connection line reverts to originating from the top-level map, and not from its direct parent. In the marked up diagram below: * #1, #2 indicates the offset level * The squares indicate the scope of the various maps subordinate to the main map * The extreme left (green) and right (yellow- almost) map-connection lines correctly originate from their parent maps * The map-connection lines highlighted pink and blue originate from the main map, and not from their parent map, even though the offset is correctly made from the parent. The recti-linear lines I have sketched show where I expect the map-connection lines to be drawn. For comparison https://therion.speleo.sk/wiki/mapconnectors?s[]=connection <https://therion.speleo.sk/wiki/mapconnectors?s%5b%5d=connection> describes offsets 2 levels deep, and as I have found and on that wiki page, 2 levels deep behaves as it should. It is only once we get to 3 levels of offset that the behaviour deviates and becomes problematic. So the pattern is clearer, and I am becoming more confident it is a bug. Why a bug? * Because at 2 levels of offset the effective behaviour is that each map-connection line originates from its direct parent. * And at 3 and 4 levels of offset, the effective behaviour is that the only the most deeply nested and the 1st level of offset map-connections originate from their direct parent. The intermediary level offset map-connections originate from the main map location and not from their direct parent. So maybe it is a problem with the definition of point map-connection, or the way that the origin and destination locations are parsed to the map-connection lines? Bruce

1 0

1 map-connection issue - Offset tests SAMD-ITF-IS example
by Bruce Mutton 13 Mar '23

13 Mar '23

From: Bruce Mutton <bruce(a)tomo.co.nz> Sent: Monday, 11 July 2022 10:16 To: 'List for Therion users' <therion(a)speleo.sk> Subject: map-connection issue - Offset tests SAMD-ITF-IS example Tarquin, David The results of our little quiz made me uneasy, so I found an old test project that I believe is structured like Tarquin's, a pattern I call 'scrap and map definitions - inside trip file - inside survey' SAMD-ITF-IS. The outcome I feared (due to my large collection of projects structured differently) is that map-connections with multi-level offsets would work just fine with SAMD-ITF-IS. That has not been the case, I have the same (I think) behaviour with this test project as I have with my other projects. So perhaps a degree of relief but still a mystery to resolve. With my test project: * Offsets work OK. * Offsets of offsets (level 2 offsets) work just fine so long as the most deeply nested offset map is comprised of scraps (and not maps). * Offsets of offsets (level 2 offsets) do not work (connection emanates from grandparent, not the parent) if the most deeply nested offset map is comprised of maps (a necessary prerequisite when preparing for the third level of offsetting). * Offsets of offsets of offsets (level 3 offsets) map-connections correctly emanate from their parent level 2 offset map, but the level 2 map-connection continues to incorrectly emanate from its grandparent. I have not progressed this to a fourth level, brain is starting to hurt and I ran out of scraps associated with the particular sub-survey that I picked on. Re-reading Tarquin's last email mentioning sub-sub-sub-surveys, I wonder if we are at cross purposes a little (or Tarquin is using 'survey' loosely to refer also to maps). In my example below (which I think is structured like Tarquin's) there are two surveys (1 and 2) and a parent cave survey that contains those two surveys, so only two levels of survey. However I have created three levels of map which offset correctly. When I create a fourth level of map in preparation for 3 levels of offset, the map-connection breaks. The code examples below show only to the level 2 and level 3 offset maps, and these are the maps on the left hand side of the diagrams, as annotated. Offset of offset is OK like this map 1-BottomUpPlan-Bottom \ -projection plan 1-BottomUpPlan-s2 break 1-BottomUpPlan-s1 #bottom terminal chamber endmap 1-BottomUpPlan-Bottom Offset of offset is not OK when same as above but map-of-scraps is split into map-of-maps that references maps-of-scraps ##Setup for OffsetLevel 3 map 1-BottomUpPlan-Bottom \ -projection plan 1-BottomUpPlan-B2 # break 1-BottomUpPlan-B1 endmap 1-BottomUpPlan-Bottom map 1-BottomUpPlan-B2 \ -projection plan 1-BottomUpPlan-s2 endmap 1-BottomUpPlan-B2 map 1-BottomUpPlan-B1 \ -projection plan 1-BottomUpPlan-s1 #bottom terminal chamber endmap 1-BottomUpPlan-B1 Offset of offset of offset is OK BUT its parent is not (as above) ##Setup for OffsetLevel 3 map 1-BottomUpPlan-Bottom \ -projection plan 1-BottomUpPlan-B2 # break 1-BottomUpPlan-B1 [0 10] below #OffsetLevel 3 endmap 1-BottomUpPlan-Bottom map 1-BottomUpPlan-B2 \ -projection plan 1-BottomUpPlan-s2 endmap 1-BottomUpPlan-B2 map 1-BottomUpPlan-B1 \ -projection plan 1-BottomUpPlan-s1 #bottom terminal chamber endmap 1-BottomUpPlan-B1 For what it is worth, here is the overall survey file, consistent with my SAMD-ITF-IS pattern: survey Cave map CavePlan -projection plan 2-EntrancePlan@2 1-BottomUpPlan@1 [0 -20] below #OffsetLevel 1 endmap CavePlan input 1-BottomUp.th input 2-Entrance.th centreline equate 1.4@1 <mailto:1.4@1> 1.4@2 <mailto:1.4@2> endcentreline endsurvey Cave So Tarquin, Can you pick any fundamnetal differences? Are we doing the same things? Are we talking about the same things?

1 0