February 2019 - Therion

"\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

SVG output gives blank file and compiling error
by Andrew Atkinson 05 Mar '19

05 Mar '19

Using 5.4.3ds1-4 on Debian testing The thconfig.thc at http://www.cave-registry.org.uk/svn/WookeyCatchment/SludgePit/ works fine for pdf map output, but if I try to output svg a file is produced that does not display in any of the svg programs I have. It also does not finishing compiling giving a red ERROR in xtherion The log file just seems to stop here is the end of it ##################### end of pdftex log file ##################### done writing output/SludgePitP.svg ... ####################### metapost log file ######################## This is MetaPost, version 2.00 (TeX Live 2019/dev/Debian) (kpathsea version 6.3.1/dev) 25 FEB 2019 13:01 **data.mp (/usr/share/texlive/texmf-dist/metapost/base/mpost.mp (/usr/share/texlive/texmf-dist/metapost/base/plain.mp Preloading the plain mem file, version 1.005) ) (./data.mp {randomseed:=42} [4001] [4002] [4003] [4004] [4005] [4006] [4007] [4008] [4009] [4010] [4011] [ 4012] [4013] [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20] [21] [22] [23] [24] [25] [26] [27] [28] [29] [30] [31] [Warning: scrap outline intersects itself in scrap 4PotsLowerSP2(a)Maze.SludgePit ] [32] [33] [34] [35] [36] [37] [38] [39] [40] [41] [42] [43] [44] [45] [46] [47] [48] [49] [50] [51] [52] [53] [54] [55] [56] [57] [58] [59] [60] [61] [62] [63] [64] [65] [66] [67] [68] [69] [70] [71] [72] [73] I have also tried xhtml which the manual says is SVG embedded in XHTML file which contains also legend and only a legend is produced. Spent a while looking at the manual and wiki pages, and not finding my mistake, can anyone help thanks Andrew

5 9

Depth in the header
by Xavier Robert 26 Feb '19

26 Feb '19

Dear all, I have an other question link to the depth definition with Therion. In the header, Therion print only the total vertical distance between the highest point and the lowest point of the cave by default. As for the point depth, lots of my co-cavers/surveyors made me the remark that it would be better if we can print the depth in the form +xx, -yy where * +xx is the height of the highest point of the cave in regards to the main entrance, * -yy is the height of the lowest point of the cave in regards to the main entrance, It also ask question depending of the data: * If there are different entrances, which entrance to use? In that case, a solution will be to choose the entrance defined in the survey block with the option -entrance * If there are different caves on the map, what reference point to choose ? A solution could be to choose the highest entrance. I tried to find Therion's variables to calcule that, but it seems that we lack an info that is the altitude of the main entrance. Does anyone has an idea how to do that ? Do I need to open a request on Github (I am not sure to be able to code that myself) ? Cheers, Xav

3 4

Point altitude/deph, Help !
by Xavier Robert 25 Feb '19

25 Feb '19

Dear all, On the caves’ survey I draw, I am often adding the altitude of points that are characteristic in the cave by using the point « altitude ». I find that really great and I want to keep it. However, I received several remarks from my co-cavers/surveyors that this is not quite readable, and that they would prefer if I can also add the depth since the entrance at those points. I can do it manually with the point label, but for a complex system, that will be a pain to maintain each time we add a new survey or a connection with an other cave previously unconnected. I thus tried to add a new user defined point (u:prof) based on the present altitude definition. However I am really not a mpost guru and I am facing two problems. Here is the code I wrote : ###### New point depth ###### code metapost def p_u_prof (expr pos, R, S, A) = T:=identity aligned A scaled 1.5S rotated R shifted pos; # calcul of the depth of the point: altitude of the point - altitude max of the cave # (it will be better with the altitude of the main entrance # defined by the option -entrance of the survey block) depth := \thaltitude - \cavemaxz; # Print the label begingroup interim defaultscale:=1; label (btex {-- } depth {m --} etex, (0, 0)) transformed T withcolor(0.5,0.,0.); # 1) Why is profondeur value NOT printed ? Where is the error ? endgroup; enddef; initsymbol("p_u_prof") endcode ############################## The problem is that this point will print the text "-- depth m --", but not the value of the depth. I suspect that : 1. the depth calcul may not be accurate? 2. the way I call the variable depth is not accurate? Does anyone has a clue for that problem? My second problem/question deals with the way to calculate the depth. Here I try to calculate it by using the maximum altitude of the cave (\cavemaxz). But it should be better if I use the altitude of the main entrance if it exists. But I did not find if there is such a varaible already defined. Does anyone knows how to do that ? Cheers, Xavier

1 1

Inconsistent SELECT behaviour for pdf and xvi map output with background sketches..
by Duncan Collis 15 Feb '19

15 Feb '19

In my th2 file I've got scraps with -sketch specified, and stations placed to enable warping/morphing of these background images. In th2 a map is defined (let's call it map_A) which includes the scraps I want. Then in .thconfig: select map_A layout morph scale 1 500 grid bottom grid-size 100 100 100 m sketches on grid off endlayout # Output plan in Therion pdf format export map \ -projection plan \ -format pdf\ -output map_A.pdf \ -layout morph # Output plan in Therion xvi format export map \ -projection plan \ -format xvi\ -output map_A.xvi\ -layout morph PDF output is as expected from the manual. It shows the background images attached to the scraps in the selected map, plus only the parts of the centreline that are used in those scraps. However if I change the export command to use XVI format, I get the background images and the centreline for the whole project, which contains over 20,000 stations. This is very difficult to use as it takes a long time for XTherion to load it, and then the area I'm interested in is tiny compared with the whole drawing area, so it requires quite a bit of zooming and scrolling to get there before I can start working. Am I right in thinking that the XVI output should contain the same bits of centreline as appear in the PDF output, rather than the whole lot? Am I missing something? Also: 'grid off' does not seem to affect the XVI output, which is why I've specified a fairly large grid size so that the grid isn't obscuring the sketches. I'd really like to be able to disable the grid in XVI completely. Is there a way to achieve these two things? Best regards, Duncan.

3 8

Morphing of background scketches fails on Win10 when Therion installation path contains spaces
by Duncan Collis 14 Feb '19

14 Feb '19

Hi, Another problem I encountered when trying to morph background sketches, this time with an easy workaround which I am posting here in the hope that it will of use to someone. With Therion installed in: D:\Program Files\Therion the following error appears in the compiler window when trying to morph background sketches: 'D:\Program' is not recognized as an internal or external command, operable program or batch file. Reinstalling Therion in: D:\Therion solves the problem, which seems to be due to the space in the original installation path. Best regards, Duncan.

2 3