July 2020 - 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

How to calculate the volume of a cave
by Bill Gee 31 Jan '22

31 Jan '22

Hello everyone - What tools can be used to calculate the volume of a cave based on center line and LRUD data? I found an email from Martin Sluka from about 4 years ago describing how to use Loch to export a .lox file in other formats, then run that file through CloudCompare or ParaView. The process looks very complex to me, and besides - Loch does not run on my computers, so there is no way for me to generate an export. As far as I can tell, Survex does not have a way to calculate volume. Could it be done with a KML file and Google Earth? -- Bill Gee

8 11

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

texts_rs and a remark about karren vs anastomosis
by ivana miskovic 09 Feb '21

09 Feb '21

Hello, Here I put the translation file of map outputs in Serbian language. It would be great if texts_rs.txt were compiled in next Therion release. Also, unrelated to the translation itself, during translation I found some confusion in point symbols for karren and for anastomosis. It seems like they are inverted. Karren are generally sharp limestone formations on the floor, and anastomosis are usually remain like rounded rock formations in the cave ceiling. Unfortunately, in the UIS official symbol list, karren and anastomoses were put on the same picture. Thanx and c u in next surveyes, Ivana

3 4

context related hide with custom point
by Axel 31 Jul '20

31 Jul '20

2 1

Selecting parts of a survey with the "select" statement
by Tarquin Wilton-Jones 31 Jul '20

31 Jul '20

Hi folks (and particularly Stacho), Just trying to revive an idea we had last year, which solves a significant problem; drawing cross sections through multiple passages/stations. The idea is to be able to select a subset of legs and splays from a survey, for export (eg. as an XVI). https://github.com/therion/therion/issues/156 group foo 2 3 2.706 351.41 -77.19 3 - 0.440 232.38 13.38 3 - 0.824 193.77 56.68 3 - 0.648 149.94 47.91 endgroup And in .thconfig: source "cave.th" select foo(a)survey1.cave select bar(a)survey1.cave select baz(a)survey2.cave export map -projection [elevation 180] -fmt xvi -output "sections_a.xvi" Can anyone see any better ways to do this with existing stuff, or should I keep trying to persuade someone to implement it? Stacho, would you be able to say if such a thing would actually be possible to implement? Cheers, Tarquin

1 0

Splays - Revisiting Breaking extended elevations
by Bruce Mutton 30 Jul '20

30 Jul '20

Another random observation on extend control. Extending left and right using a block of control statements (as opposed to in-line with the survey data) results in Therion extending the splays incorrectly. This behaviour is present regardless of whether data is imported via PocketTopo, TopParser or SexyTopo. Examples below. Below, a SexyTopo elevation surveying to the right (splays are correctly drawn) Below, the above SexyTopo elevation exported to Therion (it is the same – good) Below, the above elevation from Therion exported left (splays are wrong) Notice how all the splays are extended in the direction that the legs are extended in. Another example of Therion export to pdf showing splays incorrectly extending in the direction that the legs have been extended. It should be more aligned to the approach that TopoDroid uses (page 19 of the user manual) <https://sites.google.com/site/speleoapps/home/topodroid/user-manual> “mid-line = centreline” “azimuth = bearing” Bruce

4 6

Extended Gridl ines longer and other font for altitude
by Axel 29 Jul '20

29 Jul '20

2 4

Re: [Therion] Revisiting Breaking extended elevations on specific stations
by Marco Corvi 23 Jul '20

23 Jul '20

i realized i was too naive: the "principle" of the spanning tree is ok, but it is not enough. suppose to have five legs at a station 6-7 7-8 20-7 7-21 7-45 and some of them belongs to loop(s). Suppose that the user wants to have 6-7 7-8 together, and 20-7 7-21 together but the two pairs separated, because of the way loops get extended. and 7-45 attached to 6-7 7-8 at station 7. the abstract picture i came up with was to replace a crossway station, like "7" in the above example, with a complete graph (for 3-leg crossway this is trivial) to make the story short i think therion syntax needs a way to specify that 6-7 7-8 and 7-45 share station "7" in the extended elevation and 20-7 7-21 share a separate station "7". marco

2 3

Re: [Therion] Revisiting Breaking extended elevations on specific stations
by Tarquin Wilton-Jones 16 Jul '20

16 Jul '20

> extend ignore 8 7 11 > extend ignore 6 7 12 > > should save the situation. Am I missing something? This is basically what I also thought; you need to supply three stations to control it. I was going to suggest the opposite notation: extend prefer 8 7 12 meaning "to get to 12, prefer to start from the 8-7 leg". But either preferring one triplet, or preventing the other, should work. So I would be just as happy with your suggestion. Either of these would also solve the "extend stop" problem at the same time.

1 0