December 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

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

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

Re: [Therion] Showing qestion mark texts broken?
by Benedikt Hallinger 05 Jan '19

05 Jan '19

Forwarding an off list mail to me that explains Am 2018-12-24 11:27, schrieb Marco Corvi: > benedikt, > > from my tests, > options, eg "-text", are referred as ATTR__text (double underscore), > custom attributes, eg "-attr code", as > ATTR_code (single underscore) > > feel free to forward to the list. > > thx for pointing out the error in my page, > > marco

1 2

a_blocks_SKBB_ (expr p,o,s_beg,s_end,d_beg,d_end) =
by Andrew Atkinson 31 Dec '18

31 Dec '18

When playing with the area blocks in the data.mp file I found def a_blocks_SKBB_ (expr p,o,s_beg,s_end,d_beg,d_end) = Different from def a_blocks_SKBB (expr p) = The name has an _ on the end, however, I have no idea how to use it, also if I copy it in to a code endcode layout I cannot get it to work even if I make it def a_blocks_SKBB_TEST (expr p,o,s_beg,s_end,d_beg,d_end) = It seems to go into an infinate loop, is this maybe as I have not defined the extra variable o,s_beg,s_end,d_beg,d_end, if that is what they are, and if so how do I define them. Basically it looks interesting, but I have no idea how to play with it, Help! thanks Andrew

1 0

Metapost area block
by Andrew Atkinson 31 Dec '18

31 Dec '18

After a meeting the UK Cave Surveying Group had in November, some thought the the block did not look that good, and could be improved, with different sided block. Work started and I have eventually got round to finishing it. Based on the AUT version (which is based on others by the looks of it.) I have made it so that there are variables at the start so people can adjust it to their personal preference with nearly no knowledge of MetaPost (not that I have much!) https://therion.speleo.sk/wiki/metapost#customisable_area_blocks_with_diffe… The loop for drawing different sided blocks could be improved, this is the quick and dirty play. Some things I could really do with help improving. To get rid of the transparency of other blocks below, I have had to call thclean three times, there has to be a better way. Also blocks at the edge, there tends to be too much space, I have an infinite loop, which works, sort of, but tends to leave spaces, a better solution would be good. Blocks tend to pile up near walls, but that would need to be able to differentiate between the lines that make up the border, can that be done? I have also added a fixed rotation, then some variability around that, to try to simulate bedding blocks. Currently uniformdeviate is used, MetaPost seems to have normaldeviate, which may be better for this, but when trying it in Therion, it appears not to be a recognised command? This also leads to the question, can any of these settings be accesses from the th2 file, maybe as an option rather than by changing the MetaPost? For people to play, I've placed the test files at http://wotcc.org.uk/__Survey/BoulderTestArea.zip sorry lots of questions, thanks in advance Andrew

1 0

No passage walls converting .plt to .lox
by Marco Menchise 28 Dec '18

28 Dec '18

Hello, I have a Compass .plt file which I am able to display with Loch. I happily see station names and passage walls. I'm trying to generate a .lox file to display with CaveView on the web. CaveView needs .lox format. To do this, I import the .plt in Therion then export the lox model enabling all features (walls, splays, etc.), but I get no walls in the final file. I tried to generate a .lox model from a test .th file written by hand and I was able to get all the features. Am I missing something? Thanks, Marco

1 0