June 2018 - 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

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

Therion and DEM
by Xavier Robert 24 Jan '19

24 Jan '19

Dear all, For a quite large project, I am using a relatively high-resolution DEM (i.e. 1 px = 1 m), and I am trying to use it within Therion to produce a .lox-3D file. I am however facing some problems: If I export the full resolution DEM to a .th file (6540*4307 cells) with the line "grid 325816.2990788577 5106250.599820679 1 1 6540 4307 ». I have the error « therion: error -- dem.th [14] -- line too long ». This line 14 correspond to the first row of the DEM. ASC parameters are « #NCOLS = 6540, NROWS = 4307, XLLCORNER = 325816.2990788577, YLLCORNER =5106250.599820679, CELLSIZE = 1.0 » If I export the DEM with a 5 m pixel resolution (1308*861 cells) (with the line "grid 325816.299079 5106250.59982 5.001161440185831 5.001161440185831 1308 861 », I get the same error, If I export the DEM with a 10 m pixel resolution (654 * 431 cells) (with the line « grid 325816.299079 5106250.59982 9.996519721577727 9.996519721577727 654 431 »), everything compiles OK and the result is quite OK (https://www.groupe-speleo-vulcain.com/wp-content/themes/custom_theme/3d/JB.… ; be patient, it takes time to load), but not with the full resolution. The process to build each .th DEM is exactly the same, I do not touch any end of line. I edit the .asc DEM with vi to translate it into a .th file. I thus suspect that there is a size limitation for the DEM in Therion, I imagine a limitation in the number of row/columns of the DEM. Is that true ? If yes, what is this size limit for DEMs ? As anyone an idea how to overtake that and use the full resolution DEM ? Cheers, Xavier

4 5

Scale dependant error when using area fills
by Tom Foord 20 Jan '19

20 Jan '19

Hi all I'm having some problems compiling a project which includes debris area fills. Depending on the exact symbol fill that I use, I am getting strange scale-dependant errors which seem to cause the compiler to loop endlessly until I force it to stop. I originally noticed the problem when using a custom area fill that I made by modifying the standard a_debris_AUT symbol fill. I've attached my modified metapost definition in the attached text file 'a_debris_WUG.txt'. The error occurs for any scale between 1:2000 and 1:4483 (outside of this range the project compiles fine). See attached output log 'Output log - a_debris_WUG.txt'. As you can see, the file seems to loop over and over again. Initially I thought this problem was specific to my custom fill, but then I noticed that I also get a similar error when using the standard a_debris_AUT fill, however this time the error only occurs when the scale is set to exactly 1:2000 (any other scale seems to be fine). See attached output log 'Output log - a_debris_AUT.txt'. Can anyone help with this problem? Thanks Tom

9 21

Point with entrance coordinates ?
by Xavier Robert 29 Jun '18

29 Jun '18

Dear all, I am very pleased with the use and the outputs of Therion. However, for the map views and/or elevation (projected or extended) views, it always seems to me that there is a lack of a convenient way to add the entrance(s) coordinates somewhere. It could be inside the header, or near the given entrance on the drawing. I think that this is an information that needs to be on a cave map. Some times ago, I tried to modify my header to add that information, but I could not find the right tex variables corresponding to the entrances coordinates. For the moment, I am always adding them by hand with the point « label » (see example in attachement). This solution does not convince me because this is not linked to the data I entered in the .th file. I am thus looking for a way to add those coordinates in a map, preferentially with a new point definition that read the coordinates from the survey data and print it to the map. What would be great is to also have an option to be able to print the coordinates on the map either in the map projection system (defined in the layout/thconfig) or in geographic coordinates (point u:coords -entrance <entrance_names/fixed_point> -latlong for instance?). Does anyone have an idea on how to do that ? Thanks for your lights, Cheers, Xavier

1 0

Problems with KML-File and PDF-Display
by Markus Boldt 26 Jun '18

26 Jun '18

Hello, I have some Problems with a "spezial" presentation. I need that presentation as overlay Google-Earth (KML). The PDF works but there is another displaying of the right part in the PDF as in the drawing (th2-File). The "walls" respectively the area is moved In the KML-File the right part of the drawing is completely missing. What is happening? I don`t see the fault. Can anyone help me please. Greetings Markus Necessary Files attached

2 4

Tex variables to report according to cs, projection type and angle
by Bruce Mutton 25 Jun '18

25 Jun '18

Hi all I was just trying to make a new header definition that could report appropriately, dependant on presence of a coordinate system, plan, extended or projected elevation. It was mostly progressing OK until I realised I was pinning my hopes on using the metapost ATTR__elevation variable in a block of tex code. That and my very poor grasp of tex Boolean testing ( \if ATTR__elevation is probably the wrong syntax) mean that I am probably doomed to fail. Since I have got this far, I may as well ask a few questions.. In the code below. Is there a tex variable equivalent to the ATTR__elevation metapost variable? Is it possible to differentiate extended elevations from projected elevations (and plans) with tex? For example, can we determine the projection angle of a projected elevation? How to format the magdecl output to just 1 decimal place? Bruce # % print coordinate system and projection related information \if ATTR__elevation % print elevation specific text %THIS TEST ALWAYS FALSE?? # % extended elevation {\the\legendtextsize\ss {Idealised elevation} \par} %' looking generally East' %this whole line probably redundant # % projected elevation \edef\tmp{\the\outcsname} \ifx\tmp\empty %ie if no cs {\the\legendtextsize\ss {Elevation looking xxx deg magnetic}\par} %NEED TO SEE IF PROJECTION ANGLE AVAILABLE TO TEX \else %there is a cs {\the\legendtextsize\ss\the\outcsname { elevation looking xxx deg}\par} %NEED TO SEE IF PROJECTION ANGLE AVAILABLE TO TEX \fi \else % not ATTR__elevation % print plan specific text # % plan \edef\tmp{\the\outcsname} \ifx\tmp\empty %ie if no cs %{\the\legendtextsize\ss {Plan projection (not georeferenced)}\par} %remove preceding % for redundant long form {\the\legendtextsize\ss Arrow points to magnetic north} \else %there is a cs \the\legendtextsize\ss\the\outcsname %{ plan projection}\par %remove preceding % for redundant long form \edef\tmp{\the\northdir} \ifx\tmp\empty \else {\the\legendtextsize\ss { arrow points \the\northdir { north}}} % grid or true north \fi # % Could report declination here \edef\tmp{\the\magdecl} \ifx\tmp\empty \else {\the\legendtextsize\ss\the\magdecl { deg magnetic declination}\par} %HOW TO LIMIT TO ONE DECIMAL PLACE? \fi \fi \par\par \fi % ATTR__elevation % end plan Above code produces the top couple of lines of this header snapshot. It should be different depending whether it is a plan or elevation, but at present is always this way. However the coordinate system test does work properly.

1 0

WG: Wanted: Flag to exclude certain legs from loop closure algorithm
by Michael 21 Jun '18

21 Jun '18

Hello Ben, Thanks for the hint to use "SD" but I need some more help with that. For example, I want *only* leg from WGB27 to WGB28 to exclude from modification by Therion's loop closure algorithms. What statements do I need to insert at what places to ensure that? data normal from to length compass clino ignoreall WGB26 WGB27 20.5 30 0 WGB27 WGB28 17.1 95 0 WGB28 WGB29 9.5 120 0 Michael.

3 3

How to properly scale xvi for using as a background image for drawing
by Marco Menchise 19 Jun '18

19 Jun '18

Hello, is there a simple way to scale .th2 scraps to make they perfectly match the scale factor of a .xvi file used as background image in xtherion? I want to edit a set of scraps (which are contained in a single th2 file) while having centerline and splays as a background image. So I usually generate the .xvi file from centerline data and load it as a background image of the scrap in xtherion. If the scraps don't have the same scale factor of the background I'm not able to superimpose them and edit the drawing. How to make they match? Should I edit .th2 files by hands and do some calculations? Could someone please clarifiy how Therion manages scale factor of scraps? My scraps usually contain stations so I'm quite sure I don't have to change the "-scale" option of the scraps. Thanks, Marco

2 3