February 2025 - 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

smooth option details
by Rodrigo Severo 13 Apr '25

13 Apr '25

Hi, I am trying to better uderstand the line segment smooth option. Therion Book currently states that: "* smooth <on/off/auto> -> whether the line is smooth at the given point. Auto is default." From some tests I believe that the resulting behaviour could be explained in details as: "* smooth <on/off/auto> -> whether the line is smooth at the given point. Auto is default. This setting only has any effect if both segments that passes through the point affected by the smooth setting are Bezier Curves (the one arriving at it and the one leaving it). On means that the line connection at this point will be smoothed, both by therion and by xTherion. Off means that smoothness at the point is not guaranteded. Auto means that, if both segments that passes through the point are Bezier Curves, Therion will automatically detected if they are smooth and, if they are detected as smooth, Therion will keep them smooth in it's transformations. xTherion always creates Bezier Curves as smooth, even if the previous segment was a straight one." Is this detailed explanation correct? Is there any correction or inclusion that would be appropriate? Regards, Rodrigo

3 2

Generating list of drawers
by Benedikt Hallinger 08 Mar '25

08 Mar '25

Hi, before I dig into SQL myself, does by chance somebody already made a script or SQL to generate a list showing: "who has drawn how much length of the surveys". Something along: Person A: 250m Person B: 199m Person C: 80m ... Thank you :)

5 8

Need help installing Therion on windows arm64
by Philip Schuchardt 25 Feb '25

25 Feb '25

I have a mac. I have therion install on my mac, but I want to try out *csurvey. *csurvey only runs on Windows, which I've installed in a Windows 11 VM (arm64), but when I go to install therion I get this error: [image: Screenshot 2025-02-25 at 1.24.51 PM.png] Most x64 software will run just fine on arm windows, it just goes through an emulation layer. I think this is just a check in the installer. Do you all have any ideas? Or should I try to build Therion from source on windows? It would be nice if the windows binary was sign so you don't get this message (I know it spendy and annoying to get EV certification): [image: Screenshot 2025-02-25 at 1.24.23 PM.png] Thanks! Phi|ip

1 0

Therion & QGIS Styles
by Xavier Robert 21 Feb '25

21 Feb '25

Dear all, Some months ago, I told you that Alex Pont and me were working on setting GIS solution using shapefiles exported from Therion. Since some days, we have uploaded on GitHub the styles we are applying in QGIS for the shapefiles that we export from Therion. You will find them here : https://github.com/Alex38Lyon/QGis_Therion. You should install them in QGIS with the plugin : QGIS Ressources Sharing. Feel free to use it ! Doing that, we have found that some informations given in the th2 are missing in the shapefiles produced by Therion. An issue has been open there : https://github.com/therion/therion/issues/635 Cheers, Xavier

2 4

Embedded image does not appear in some layouts
by Bill Gee 20 Feb '25

20 Feb '25

Here is a puzzle ... I have set up a thconfig file to create a profiles map, then used the "map-image" layout directive to include it in the output files. It works ... SOMETIMES! Take a look at the thconfig file embedded below. The profiles image appears on the files produced from the MainMap and MainMapNoColor layouts. It does not appear on MainMapPrint. Why? Does it have something to do with the TeX code in MainMapPrint? Thanks! -- =============== Bill Gee encoding utf-8 # Bring in the main configuration file source GeronimoSpringsCave.th # Used for most of the maps select GeronimoSpringsCave # Load the Metapost code for custom symbols input ../TherionMasterFiles/CustomSymbolsCode.txt # Bring in the code for custom scale bar input ../TherionMasterFiles/ScaleBarCode.txt # This layout is for the main 2D map, all on one page layout basics language en_US units imperial scale-bar 50 feet page-numbers on scale 1 200 north true symbol-color area water [0 0 100] map-comment "A DistoX survey of Geronimo Springs Cave (CAM-086), Missouri" statistics explo all legend on map-header 3 60 w symbol-set UIS # Set point height symbols to be enclosed in boxes code metapost p_label_mode_height:=6; endcode # Section for PDF properties doc-author "Bill Gee" doc-title "Map of Geronimo Springs Cave (CAM-086)" doc-subject "Plan map of Geronimo Springs Cave (CAM-086)" # Section for map photos # Add in the elevations maps # Bring in the custom symbols copy CustomSymbols # Bring in the custom scale bar copy CustomScaleBar # Reassign names symbol-assign point gradient AMER symbol-assign point stalagmite AMER symbol-assign point stalactite AMER symbol-assign point pillar AMER symbol-assign point popcorn AMER endlayout # This layout is for profile maps. It turns off the legend and other stuff layout profiles legend off map-header 0 0 off symbol-hide group centerline color map-fg [100 86 66] endlayout layout MainMapPrint copy basics scale 1 200 debug off symbol-hide group centerline color map-fg [100 86 66] # Entrance passage profile map-image 0 0 sw GeronimoSpringsCave-Profiles.pdf # Change the size of the legend code metapost tmpscale=1.3; def draw_legend_box = % Next line controls size of symbol in each symbol table box currentpicture := currentpicture scaled tmpscale; % Next line controls size of symbol table box background clip currentpicture to unitsquare inscale xscaled tmpscale yscaled tmpscale; drawoptions(); pickup PenB; % I think the next line controls the size of each symbol table box draw unitsquare inscale xscaled tmpscale yscaled tmpscale; enddef; %clear the background of the larger legend boxes def clean_legend_box = unfill unitsquare inscale xscaled tmpscale yscaled tmpscale; enddef; %change the value of inscale to fill the legend boxes def inscale = xscaled (legend_scale*tmpscale) yscaled (0.618*legend_scale*tmpscale) enddef; endcode code tex-map \def\maplayout{ \legendbox{3}{85}{W}{ \def\txtsize{16} % Define the default text size \legendwidth=20 cm \legendtextsectionsize={\size[\txtsize]} \legendtextsize={\size[\txtsize]} \legendtextheadersize={\size[40]} \hsize=\legendwidth \the\legendcontent={\size[\txtsize]} \the\legendtextsize\ Map generated at \the\time \the\currentdate\medskip \the\legendtextsize\ Therion version \the\thversion } } endcode #end of TeX code to change legend size endlayout # Layouts to specify colors layout MainMapNoColor copy basics color map-fg [100 86 66] # Entrance passage profile map-image 0 0 sw GeronimoSpringsCave-Profiles.pdf endlayout layout MainMapColorized copy basics color map-fg altitude # Entrance passage profile map-image 0 0 sw GeronimoSpringsCave-Profiles.pdf endlayout # Change the legend callouts input ../TherionMasterFiles/LegendCallouts.txt # Profiles map export map -proj elevation -layout profiles -o GeronimoSpringsCave-Profiles.pdf # Basic plan map, normal colors export map -proj plan -layout MainMapNoColor -o GeronimoSpringsCave.pdf # Map with no centerline export map -proj plan -layout MainMapPrint -o GeronimoSpringsCave-Print.pdf # Basic plan map, colorized for elevations export map -proj plan -layout MainMapColorized -o GeronimoSpringsCaveColored.pdf # 3D map for use with Loch export model -fmt loch -o GeronimoSpringsCave.lox # 3D map for use with Aven export model -fmt 3d -o GeronimoSpringsCave.3d # 3D map for use with ArcGIS export model -fmt esri -o ./GeronimoSpringsCave-ESRI # KML file for overlay in Google Earth - Requires lat-long specified in the survey data file export map -proj plan -fmt kml -o GeronimoSpringsCave.kml # Produce the debug maps system "/usr/local/bin/therion -l therion-Debug.log thconfig-Debug"

5 15

3d to QGIS - different alignment
by Andrew Atkinson 20 Feb '25

20 Feb '25

Hi all Not strictly a Therion question, but the answer is likely to be in the data entry or the interpretation of data in Therion. I'm slowly incorporating QGIS into my workflow, and trying to automate it. As such I'm using a modified version of the survex 3d importer https://github.com/AndrewAkinson/qgis3-survex-import_amend So that items can be easily switched on and off I'm going down the line of importing the 3d files by cave rather than the generated one for the whole catchment For now I'm doing it with the data in http://www.cave-registry.org.uk/svn/CheddarCatchment/ Currently I'm working on the Longwood Valley area as Longwood Valley Sink has been recently discovered. The directories I'm using RRift/ (3d needs to be generated from survex) LongwoodValleySink/ Longwood/ (Fake data with calibrate compass -90!) Toothache/ (single leg) In each of these directories the .th file generates a survex 3d file Also in the the root there is a LongwoodValley.thcfg which has the above caves (plus maybe Charterhouse, GB, TynningsGS and Reads depending on how I left it) In the diagram attached (hopefully this list does attachments!) The Dark purple dots are the import of the 3d file that has Rhino, Longwood, LongwoodValley Sink and Toothache together. The light pink, yellow dots are the individual imports (and entrances from the MCRA database.) Also included is an overlay of a scree shot from aven, which agrees with the group import. The question is why is Longwood different when imported as a 3d on its own compared with as a group? They are both using the same data! Andrew

2 3

Automatic declination correction by date to Eastings and Northings different to survex
by Andrew Atkinson 20 Feb '25

20 Feb '25

I have a few files that are fake data made from paper surveys. These come in various formats but a common one, and the one I tend to make if I do it is in the form of data cartesian station easting northing altitude It appears that Therion applies automatic declination by date to this form of data, so it defaulting to cartesian magnetic This is not the same default as Survex "By default, the North used is True North, but you can specify to use Magnetic or Grid North (in the input coordinate system) with the *cartesian command, and also specify an additional rotation to apply " The cartesian command does not seem to work in Therion. For now I've bodged it buy applying declination 0 degrees but it would be better if Therion followed the Survex manual to which the Therion book refers to for commands. An example file is http://www.cave-registry.org.uk/svn/CheddarCatchment/Longwood/Renolds/Renol… You will need revision 479, otherwise you will get the bodge fix thanks Andrew

1 0

Date before 1900 error - but where?
by Andrew Atkinson 20 Feb '25

20 Feb '25

Hi all I could really do with some help searching for a problem. In the data http://www.cave-registry.org.uk/svn/CheddarCatchment/ (downloadable svn repository) Trying to run any of the thconfig (well I've tried most) files leads to this error configuration file: LongWoodValley.thcfg reading ... done reading source files ... done preprocessing database ... done therion: error -- automatic declination calculation before 1900 not supported, please specify declination explicitly writing xtherion file ... done This is not a useful error. This data set use to work, I've produced lots of surveys from it. It seems to indicate a date in the error message. Although grep has shown up a couple that I needed to fix for other reasons, none have shown dates before 1900. So I have no idea how to track down this error What else should I be looking for? Running therion with -d does not give any further information Help! thanks Andrew

4 6

Tags/Attr split from [Extended elevation control - Embedded image does not appear in some layouts]
by Andrew Atkinson 19 Feb '25

19 Feb '25

On 19/02/2025 17:02, Benedikt Hallinger wrote: > 2. tagged elements only if they are selected in the thconfig > > 3. actual systematic is user-defined, so we have maximum flexibility. > For example, I could imagine mixing several systematics, one for desired > output scale and another for special purposes: > > --------- thconfig -------- > select tag scale:250 > select tag scale:500 > select tag remarks > select tag crossSections:abc > export map .... > --------------------------- > In the th2's I just tag the items with "-tag scale:500" or "-tag > crossSections:abc" (or both). > This would completely (and optionally) decouple the show/hide from > internal magic and support various usecases out of the box. One just > needs to think of a good tagging systematic for his usecases/dataset. I agree the attr so nearly does this, you can set attr like -attr scale 250 -attr crossSection abc However, it is not exposed to the select or the symbol-hide/show. It appears to be only accessible from metapost and the database export (the thbook also says it is exported in shape files) Andrew

1 0