March 2019 - Therion

Re: [Therion] Point altitude/deph, Help !
by Xavier Robert 28 Jun '22

28 Jun '22

Hi all, I think I have found a trick. The other Xavier led me to the right tracks, thanks a lot ! Finally, this is quite simple with the point altitude, and no need to change anything inside the : - If we use the point altitude only with the option -align, we get the altitude - If we use the point altitude with the options -align and -value [-1004 m] where 1004 is the altitude of the main entrance, we print the depth only for that point (Do not forget the " - " before the altitude of the main entrance), and thus, we do not erase the classic point altitude. The only (small) limits are : * If the main entrance changes, we need to manually update ALL the points that print the depth. But that should not be be everyday, and not a big issue to do that. * the symbology of the two points is the same. I will have a look for a way to modify that and let you know if I find a trick (If I copy the code of the point Altitude, and call it p_u_depth(expr pos, R, S, A), it crashes...). Cheers, Xav

4 4

"\legendbox" "\loadpicture" and absolute paths
by rowena 14 Mar '21

14 Mar '21

Hello, I am using the "\loadpicture" capability in "\legendbox" constructs to include map sections, elevations, etc. It all works nicely on my PC where I am using relative paths to the pdf files. My club has a desire to archive the map data for posterity - ie if my pc dies or I go walkabout, the map data should still be available so that others can add to the maps as they are extended. I would prefer to have the images included using relative pathnames, rather than absolute pathnames, so that future explorers can download the map data and extend it, without having to duplicate my file hierarchy. How can I include relative paths in the \loadpicture functionality? Thanks, Rowena

4 5

extend
by Marco Corvi 02 Jun '20

02 Jun '20

i think that extend should take values in the interval [-1,1], ie also fractional values, plus some special value such as "ignore" to open loops, and "undefined" to let the program choose, because it's a nuisance to enter a decimal number for every shot (legs + splays). therion uses the left/right normal/reverse etc. solution, and users should be allowed to set extend also for splays, if they need to. for now, let's use left/right/vert, and ignore only to open loops btw, are vertical extend considered in the computation of the cave length by therion ? marco

5 6

Re: [Therion] Therion 5.4.2. potential bug
by Martin Budaj 31 Jul '19

31 Jul '19

On Sat, Jan 12, 2019 at 10:51 AM Michael <knollesimage(a)t-online.de> wrote: > I have now attached a minimal cave sample produced with 5.4.1. and one > produced with 5.4.2. to demonstrate the displacement. > Hi, the problem is that EPSG:31467 projection uses the "potsdam" datum and the PROJ library used by Therion changed the way how to transform potsdam datum to the standard WGS84 datum – it switched from a simple string parameter (towgs84) to using external grid file (see https://proj4.org/resource_files.html#transformation-grids for examples). No grid files are currently included in the windows Therion distribution, so the transformation is not correct in 5.4.2. Therion needs to be modified to include and use those files – hopefully soon. Best regards Martin

5 8

Page Size
by Markus Boldt 31 Jul '19

31 Jul '19

Hello, how is it possible to "say" Therion to make a PDF-File with for example a Size of DIN A4 (21 x 29,7 cm)? I have tried Page-setup 21 29.7 20 29 0.1 0.1 cm it doesn`t work I have tried Size 21 29.7 cm It doesn`t, too The command is ignored. Greetings Markus

4 5

TerrainTool
by Graham Mullan 28 Jun '19

28 Jun '19

Mike McCombe's TerrainTool has been fixed and is available again from http://www.ubss.org.uk/terraintool/terraintool.php Download and enjoy. It may not use the latest data but it remains the most straightforward way of adding topographic detail to Therion 3D models. Graham

8 30

FYI - scrap is too large to process in metapost in this scale - maximal scale for this scrap is
by Bruce Mutton 08 Mar '19

08 Mar '19

Possibly, but probably not, related to the issues with coordinates, that seem to be resolved just now with eddb4c3. I have one thconfig file, (in amongst a large project with many thconfigs that work just fine), with a mysterious scale related error. I suspect this must be of my own making, and not a Therion bug. C:\Program Files (x86)\Therion\therion.exe: error -- scrap RiwakaResurgenceRoughPlan-s1(a)RiwakaResurgence.RiwakaArea.RiwakaSystem defined at ./RiwakaArea/./RiwakaResurgenceCave/RiwakaResurgenceRoughPlan.th2 [9] is too large to process in metapost in this scale -- maximal scale for this scrap is 1 : 210 The scale I am using is 1:5000, which I assume is considered smaller than the 1:210 that is being complained about by Therion. This is a thconfig for a large project that I only tend to run once every year or so, therefore I'm not sure when the problem manifested. I have not figured out why the all component caves compile OK, but the whole system fails. Unless anyone has any brilliant insights I'm not really seeking a solution from the forum just yet. I have yet to find time to explore all the possible mistakes I may have made. I have tried removing the offending scrap from it's parent map, but then another scrap in a completely different cave triggers the same error. All the same, any insight gratefully received. Bruce

1 0

5.4.3 has broken output cs conversions
by Bruce Mutton 08 Mar '19

08 Mar '19

Therion version 5.4.3 and subsequent development versions have broken the functionality whereby coordinates entered with a variety of coordinate systems are converted to a user selected coordinate system for output. The 5.4.2 output attached is from the last installation file I have that gives a correct output (all coordinates start with 159), and the next one, 5.4.3 and all subsequent versions have coordinates some 1000 km apart. It makes it a very long cave, but unfortunately two of the entrances are in the middle of the pacific ocean! The problem is that Therion is assuming that they are all in the chosen output coordinate system, but it is not performing any conversion. No errors are reported (although there are mysterious scale related errors in other datasets that could be as a result of this problem). I am using these coordinate systems for input; cs EPSG:2193 #NZ Transverse Mercator 2000 cs EPSG:27200 #NZ Map Grid 1949 cs lat-long and for output in this case I am using; cs EPSG:2193 #NZ Transverse Mercator 2000 Bruce

2 2

Flowstone Symbols
by Nick Bairstow 05 Mar '19

05 Mar '19

Has anyone got the code to make the UIS point Flowstone symbol (horizontal lines) into an area fill in contrast to the default Therion ASF Flowstone area fill (scallops). Nick

1 0

tex outcsname variable broken
by Bruce Mutton 05 Mar '19

05 Mar '19

It seems a problem with the outcsname token register has been introduced with release 5.4.3. Instead of containing the output coordinates system name, it now contains the output coordinates system code. As below, stepping through recent Therion releases. Version 5.4.2 creates this in my customised header; .as does therion 5.4.2+16a5e3e (2019-01-17) But 5.4.3 and all subsequent versions create this; Bruce

2 1