- Therion - speleo.sk

Re: [Therion] Getting started with Therioning a trad survey
by Wookey 29 Mar '20

29 Mar '20

Forwarding some queries as I only know the answer to 1 out of 4 :-) On 2020-03-29 02:25 +0100, Stuart Bennett wrote: > On 15/03/2020 17:30, Wookey wrote: > > It uses survex to do all the sums if survex is installed (and both use > > proj for the co-ordinate systems) so you should get exactly the same > > answers. Without survex it does a rather simple-minded job on its own. > > Ok, so suddenly having a lot more time at home I've made reasonable > progress, but have a few new questions. Various bits attached, should they > be relevant to the below. I don't know the answers to most of these, so forwarding to the therion list. > 1) I'd quite like it to say P33 next to the pitch, rather than just `33', > but using a `height' point type doesn't let me set a `value' including a > letter. Is there a way to use what seems like the semantically correct > type, or should I just use a label? > > 2) Having gone down the `import a .3d' route, I don't seem to get any dates > in the output, despite the 3d file knowing them, which is a shame. > Inserting a bogus centreline just to specify a date fails, as there's no > measurements. Is there a neat way around this? I think this is a feature, but it may be fixable. > 3) The boulders are enormous. The ones you get with a `breakdown'-type > point are much more suitable, but that defeats the point of having an area > fill. Is there a way to scale the area fill symbols? You want Andrew's 'fancy boulders' function. 'Customisable Area blocks' on https://therion.speleo.sk/wiki/metapost > 4) More generally, working with a survey drawn up in pencil over a Survex > printout is ok, but if I'd drawn up digitally first, would the LRUD data > have somehow been used/displayed automatically? Does using a .3d import vs > transcribing to Therion native format affect this? > > Thanks, Stuart > encoding utf-8 > import daves_hole.3d -surveys use > survey dh -title "Dave's Höhle" > input daves_hole.th2 > # date 2017.09.17 > # team SB insts > # team OGHM/KIH notes,dog > endsurvey > encoding utf-8 > ##XTHERION## xth_me_area_adjust -132.0 -1368 1883 141.0 > ##XTHERION## xth_me_area_zoom_to 50 > ##XTHERION## xth_me_image_insert {0 1 1.0} {0 {}} daves_hole_scan.png 0 {} > > > > scrap scrap1 -projection plan -scale [709.0 -992.25 1654.5 -991.6666666666666 0.0 0.0 40 0.0 m] > > point 686.0 -595.0 archeo-material > > point 1301.0 -445.0 continuation > > point 616.75 -766.5 height -value 1 > > point 648.0 -788.5 station -name 15 > > point 615.0 -698.0 station -name 14 > > point 848.5 -535.0 station -name 13 > > point 458.0 -681.5 station -name 12 > > point 564.5 -653.0 station -name 11 > > point 436.5 -141.0 station -name 10 > > point 504.0 -267.0 station -name 9 > > point 833.0 -769.0 station -name 8 > > point 946.5 -308.0 station -name 7 > > point 1180.5 -725.0 station -name 6 > > point 1284.0 -441.5 station -name 5 > > point 1241.5 -479.5 station -name 4 > > point 1026.5 -509.0 station -name 3 > > point 1219.0 -571.0 station -name 2 > > point 1350.5 -669.5 station -name 1 > > line pit -id l17-1162--732 -close on -reverse on > 1163.75 -734.25 > 1158.99 -733.3 1175.47 -717.75 1176.5 -717.5 > 1193.75 -713.25 1193.25 -722.0 1188.25 -729.25 > 1181.83 -738.56 1170.0 -735.5 1163.75 -734.25 > endline > > line floor-step -id l65-1266--488 -reverse on > 1288.0 -489.5 > 1275.0 -489.75 1238.0 -486.0 1241.5 -467.0 > smooth off > endline > > area blocks > l85-925--470 > l20-859--786 > l57-842--770 > l20-859--786 > l63-758--730 > endarea > > line border -id l85-925--470 -subtype invisible > 912.0 -716.0 > 970.0 -655.5 1012.64 -524.97 883.5 -431.0 > 777.0 -353.5 615.21 -361.72 582.0 -398.0 > 501.0 -486.5 597.5 -684.5 603.0 -733.5 > smooth off > endline > > area blocks > l17-558--678 > l65-1266--488 > l19-1314--500 > l20-859--786 > l83-1147--640 > endarea > > line border -id l83-1147--640 -subtype invisible > 1175.0 -425.5 > 1175.0 -598.59 1142.0 -677.0 1075.5 -804.0 > smooth off > endline > > line floor-step > 628.5 -763.0 > 633.25 -750.25 642.75 -743.25 653.25 -743.25 > smooth off > endline > > line ceiling-step -id l63-758--730 > 585.25 -700.75 > 615.0 -692.75 682.53 -679.87 691.25 -681.75 > 716.75 -687.25 773.0 -747.75 781.0 -754.0 > smooth off > endline > > line ceiling-step > 1339.5 -680.0 > 1406.6 -722.96 1433.75 -683.5 1362.0 -651.5 > smooth off > endline > > line ceiling-step -reverse on > 1284.25 -485.0 > 1272.25 -474.0 1254.5 -469.25 1243.0 -466.75 > smooth off > endline > > area flowstone > l17-558--678 > l60-937--312 > endarea > > area flowstone > l74-532--285 > endarea > > point 482.5 -128.75 popcorn -orientation 46.8 > > point 417.0 -144.25 popcorn -orientation 298.3 > > point 507.75 -179.5 popcorn -orientation 61.7 > > point 436.5 -209.75 popcorn -orientation 255.8 > > point 444.5 -263.75 popcorn -orientation 269.2 > > line border -id l74-532--285 -close on -subtype invisible > 511.75 -250.5 > 502.75 -252.5 471.8 -301.03 471.25 -313.0 > 470.25 -334.75 487.75 -361.75 515.25 -326.75 > 542.75 -291.75 530.51 -246.33 511.75 -250.5 > endline > > line ceiling-step -id l60-937--312 -reverse on > 953.5 -312.0 > 943.75 -310.25 928.0 -312.5 917.75 -318.25 > smooth off > endline > > line ceiling-step -id l59-500--232 -reverse on > 524.75 -224.75 > 500.5 -219.0 460.25 -265.5 453.25 -296.5 > smooth off > endline > > line ceiling-step -id l58-566--670 -reverse on > 544.25 -610.25 > 545.5 -627.0 558.5 -663.5 570.5 -676.5 > smooth off > endline > > area flowstone > l20-859--786 > l57-842--770 > endarea > > line ceiling-step -id l57-842--770 > 867.0 -762.0 > 850.5 -768.0 833.5 -772.75 807.0 -773.0 > smooth off > endline > > line ceiling-step -reverse on > 920.0 -714.0 > 952.5 -704.5 983.5 -579.5 995.0 -531.5 > 1014.75 -449.06 998.5 -333.5 998.5 -333.5 > smooth off > endline > > area flowstone > l17-558--678 > l59-500--232 > endarea > > area flowstone > l17-558--678 > l58-566--670 > endarea > > line wall -close on -outline in -subtype presumed > 646.25 -687.75 > 643.88 -687.92 646.17 -721.7 651.5 -735.5 > 655.75 -746.5 670.75 -778.59 673.5 -775.75 > 688.43 -760.32 679.52 -685.3 646.25 -687.75 > endline > > line wall -id l17-558--678 > 1297.0 -437.5 > 1248.0 -455.0 1243.26 -467.3 1241.5 -467.0 > 1218.25 -463.0 1153.0 -415.5 1078.75 -367.25 > 1074.97 -364.79 958.5 -320.75 950.0 -309.5 > 940.91 -297.47 939.04 -268.9 933.0 -270.5 > 919.75 -274.0 928.34 -306.17 922.0 -314.0 > 920.73 -315.57 886.25 -358.0 820.5 -353.0 > 780.12 -349.93 597.0 -276.0 524.75 -224.75 > 492.66 -201.98 467.96 -122.94 456.0 -129.75 > 437.84 -140.09 420.88 -144.41 429.5 -159.5 > 447.5 -191.0 461.5 -235.0 456.5 -274.5 > 451.26 -315.9 444.24 -318.15 481.0 -390.5 > 512.5 -452.5 532.5 -579.0 545.0 -606.5 > 551.66 -621.16 457.9 -642.39 452.0 -649.0 > 435.5 -667.5 444.2 -705.23 461.5 -711.0 > 467.5 -713.0 574.69 -663.83 577.75 -679.0 > 584.0 -710.0 645.06 -785.62 647.5 -786.75 > 652.16 -788.9 666.0 -788.75 676.25 -788.0 > smooth off > endline > > line wall > 1286.0 -488.0 > 1275.5 -480.0 1285.5 -455.5 1294.5 -452.0 > smooth off > endline > > point 1312.0 -574.0 archeo-material > > line wall -id l19-1314--500 -subtype presumed > 1273.0 -679.0 > 1301.0 -711.5 1386.64 -736.93 1412.0 -695.0 > 1428.85 -667.14 1396.2 -604.49 1373.5 -567.5 > 1360.0 -545.5 1334.85 -504.99 1286.0 -488.0 > smooth off > endline > > line wall -id l20-859--786 > 781.0 -754.0 > 845.76 -799.28 827.37 -779.93 851.0 -839.0 > 854.0 -846.5 864.0 -844.29 864.0 -833.5 > 864.0 -792.0 840.14 -787.93 892.5 -724.5 > 943.43 -662.8 940.5 -850.0 1073.5 -798.5 > 1193.86 -751.9 1167.39 -771.26 1196.5 -756.0 > 1237.5 -734.5 1235.79 -659.08 1273.0 -679.0 > smooth off > endline > > point 842.0 -535.75 passage-height -value 8 > > point 503.5 -288.0 stalagmite > > point 493.0 -313.0 stalagmite > > point 879.5 -791.5 wall-calcite -orientation 79.0 > > point 878.5 -819.5 wall-calcite -orientation 77.9 > > point 832.0 -827.5 wall-calcite -orientation 233.2 > > point 823.0 -802.5 wall-calcite -orientation 253.1 > > point 509.5 -651.5 stalagmite > > point 488.0 -694.0 stalagmite > > point 459.5 -692.0 stalagmite > > point 535.0 -667.5 stalagmite > > point 506.0 -677.0 stalactite > > point 458.0 -664.5 stalactite > > point 478.0 -646.5 stalactite > > point 610.0 -697.75 gradient -orientation 343.3 > > point 570.25 -583.5 gradient -orientation 343.3 > > point 701.25 -628.5 gradient -orientation 355.4 > > point 682.25 -558.75 gradient -orientation 356.4 > > point 785.25 -651.25 gradient -orientation 44.4 > > point 825.5 -716.5 gradient -orientation 65.8 > > point 900.0 -659.0 gradient -orientation 65.8 > > point 867.5 -583.5 gradient -orientation 53.8 > > point 775.75 -572.25 gradient -orientation 25.9 > > point 806.0 -484.75 gradient -orientation 25.9 > > point 666.5 -465.25 gradient -orientation 0.4 > > point 535.0 -472.0 gradient -orientation 351.4 > > point 1199.5 -666.0 gradient -orientation 289.9 > > point 1182.25 -603.75 gradient -orientation 283.2 > > point 1303.0 -647.25 gradient -orientation 292.2 > > point 1191.0 -504.25 gradient -orientation 274.2 > > point 1246.0 -514.25 gradient -orientation 266.6 > > point 1321.25 -579.0 gradient -orientation 296.3 > > point 773.0 -681.0 bones > > point 813.0 -576.0 bones > > point 727.0 -508.0 bones > > point 629.0 -595.0 bones > > point 630.0 -715.0 bones > > endscrap > > > > scrap scrap96 -scale [709.0 -992.25 1654.5 -991.6666666666666 0.0 0.0 40 0.0 m] > > point 737.0 -665.5 gradient -orientation 194.1 > > point 776.75 -709.75 gradient -orientation 259.7 > > point 694.0 -707.25 gradient -orientation 301.5 > > point 659.25 -771.75 gradient -orientation 306.6 > > point 728.0 -765.0 bones > > point 670.0 -739.0 bones > > line pit -close on -reverse on > 692.0 -690.0 > 703.63 -693.74 728.73 -712.75 735.0 -722.25 > 743.25 -734.75 766.36 -749.49 766.75 -756.75 > 767.75 -775.5 714.11 -811.84 671.0 -786.25 > 624.97 -758.92 678.0 -685.5 692.0 -690.0 > endline > > point 701.0 -732.0 archeo-material > > point 777.0 -782.0 height -value 33 > > line wall -close on -subtype pit > 764.75 -635.75 > 749.5 -630.5 686.83 -655.55 666.25 -678.75 > 650.5 -696.5 644.05 -759.5 663.25 -787.0 > 681.12 -812.59 734.6 -815.94 759.75 -784.5 > 789.12 -747.78 806.75 -721.75 796.75 -677.75 > 789.24 -644.69 773.95 -638.92 764.75 -635.75 > endline > > point 741.5 -822.75 station -name 20 > > point 714.0 -683.5 station -name 19 > > point 734.0 -721.5 station -name 17 > > endscrap > > > encoding utf-8 > source daves_hole.th > export map -projection plan -layout local -o daves_hole.pdf > > layout local > legend on > symbol-hide group cave-centreline > colour map-fg [90] > endlayout > *begin dh > *title "Dave's H?hle" > > *date 2017.09.17 > *team SB dx > *team OGHM/KIH notes > *instrument dx "Wookey DistoX1" > > ; BCRA Grade 5 specification file > ; tape error > ; 95.44% of readings are within 0.1m (2 S.D.) > *sd length backlength 0.05 metres > ; compass error > ; 95.44% of readings are within 1 degree (2 S.D.) > *sd bearing backbearing 0.5 degrees > ; clino error > ; 95.44% of readings are within 1 degree (2 S.D.) > *sd gradient backgradient 0.5 degrees > ; station position error > ; 95.44% of positions are within 0.1m (2 S.D.) > *sd position 0.05 metres > > *data normal from to compass clino tape > > ;from to compass clino tape ; remarks > 2 1 126.5 34.7 8.46 > 2 3 287.7 -3.2 8.59 > 4 3 262.4 -1.3 9.21 > 4 5 49.0 -21.4 2.53 > 6 3 323.9 0.6 11.17 > 7 3 158.1 12.6 9.27 > 7 8 194.0 16.4 20.60 > 7 .. 167.8 1.7 21.37 ; to far wall > 7 .. 183.8 5.7 16.82 ; to wall by rubble slope > 9 3 114.6 4.5 24.41 > 10 9 151.4 5.2 5.94 > 11 9 350.9 -13.7 16.80 > 11 12 254.7 9.3 4.74 > 11 .. 64.9 -1.7 19.54 ; to chamber wall > 13 3 81.6 5.8 7.64 > 13 . 172.6 88.1 13.52 ; into roof aven > 14 9 345.3 -17.1 19.46 > 14 15 159.6 44.2 5.65 > 15 16 52.6 2.2 4.54 > 16 . 298.2 -49.3 5.40 ; to Ade's bottom hole > 17 16 - down 18.3 ; was 19.74 to floor, less 16's D > 17 .. 231.9 46.4 5.83 ; leaf on far wall (was station 18) > 19 17 153.0 -77.6 8.52 > 20 19 348.5 -37.5 7.46 > *entrance 20 > *begin > *flags surface > 20 21 184.6 -10.6 11.41 > 21 22 134.6 -2.4 11.16 > *end > *fix 22 0 0 0 > > ;station details > ;name L R U D description > ;LRUDs taken relative to first leg using the station > ;vertical LRUDs use U and D for forwards and backwards > ;1 1.0 0.5 1.5 0.5 alcove up boulder slope > ;2 4.6 9.0 0.7 0.2 rock near small animal bones > ;3 10.5 6.5 0.0 2.8 flake in roof > ;4 8.5 0.6 0.6 0.2 entrance to descending rift > ;5 0.0 0.6 0.7 4.0 wall above rift > ;6 5.7 3.8 1.6 1.2 rock point above hole in floor > ;7 0.0 1.0 0.6 1.5 right wall of entrance to alcove > ;8 1.3 2.4 13.2 0.7 above entrance to small chamber > ;9 1.9 4.1 2.0 0.5 truncated stal, near wall > ;10 1.0 0.4 1.2 0.4 rear of cauliflower chamber > ;11 2.0 1.3 0.3 1.5 entrance to stal chamber > ;12 1.3 1.4 2.9 0.5 broken-off stal (vertical on floor) > ;13 7.7 4.8 7.5 0.4 rock near pitch-fork > ;14 1.2 1.4 0.2 0.5 lowest point of entrance arch > ;15 1.1 0.1 5.4 1.5 cross scratched on right wall (as exiting) > ;16 1.7 2.1 999 1.4 wall of pitch > ;17 3.2 2.4 3.9 0.0 rebelay bolt (lower) > ;18 3.5 2.8 0.0 3.9 leaf on wall (misplaced) > ;19 3.3 2.9 4.0 0.0 mossy knob > ;20 boulder on south rim of pitch (surface) > ;21 boulder on surface > ;22 top-corner of third quoin of barn wall > > *data passage station left right up down ignoreall > 1 0.5 1.0 1.5 0.5 alcove up boulder slope > 2 9.0 4.6 0.7 0.2 rock near small animal bones > 3 10.5 6.5 0.0 2.8 flake in roof > 13 7.7 4.8 7.5 0.4 rock near pitch-fork > 9 4.1 1.9 2.0 0.5 truncated stal, near wall > 14 1.4 1.2 0.2 0.5 lowest point of entrance arch > 15 1.1 0.1 5.4 1.5 cross scratched on right wall (as exiting) > 16 1.7 2.1 31 1.4 wall of pitch > 17 3.2 2.4 13 19.7 rebelay bolt (lower) > 19 2.9 3.3 5 1 mossy knob > 20 1 2 0 1 boulder on south rim of pitch (surface) > *data passage station left right up down ignoreall > 5 0.6 0.0 0.7 4.0 wall above rift > 4 2 0.6 0.6 0.2 entrance to descending rift > 3 12 7 0.0 2.8 flake in roof > *data passage station left right up down ignoreall > 6 5.7 3.8 1.6 1.2 rock point above hole in floor > 3 15 6 0.0 2.8 flake in roof > *data passage station left right up down ignoreall > 8 2.4 1.3 13.2 0.7 above entrance to small chamber > 7 0.0 1.0 0.6 1.5 right wall of entrance to alcove > 3 7 20 0.0 2.8 flake in roof > *data passage station left right up down ignoreall > 10 1.0 0.4 1.2 0.4 rear of cauliflower chamber > 9 2 2 2.0 0.5 truncated stal, near wall > *data passage station left right up down ignoreall > 12 1.4 1.3 2.9 0.5 broken-off stal (vertical on floor) > 11 2.0 1.3 0.3 1.5 entrance to stal chamber > 9 2 2 2.0 0.5 truncated stal, near wall > *data passage station left right up down ignoreall > 13 7.7 4.8 7.5 0.4 rock near pitch-fork > 11 2 15 0.3 1.5 entrance to stal chamber > *data passage station left right up down ignoreall > 16 0 2 0 2 wall of pitch > 11 1.3 2.0 0.3 1.5 entrance to stal chamber > > *end dh Wookey -- Principal hats: Linaro, Debian, Wookware, ARM http://wookware.org/

1 0

Is there any method of accuracy control for database outputs?
by Mykyta Kozlov 23 Mar '20

23 Mar '20

Hi, I am using therion (5.4.4 latest stable build for windows) in a following scenario: 1. Make triangulation-like survey with/without Geo fix. 2. Place 'visually-identifiable' markers exactly on a survey stations done on step 1. 3. Do a photogrammetric scanning, making photos in the way markers are clearly visible on obtained images. 4. Use a photogrammetry software to do a 3d reconstruction with a GCP fix, using markers from step 2 as ground control points. To obtain GCP coordinates I use therion-produced database output, with a sample line from .thconfig file "export database -o 350.sql" Produced .sql - file contains at its end series of SQL commands like following "insert into STATION values (9, '1', 33, 732175.84, 4728436.27, 2292.57);" for UTM-fixed survey and "insert into STATION values (9, '1', 33, 41.99, 8.51, 33.04);" for non-geo fixed survey. It is clearly seen that last 3 values are either UTM or local X, Y, Z coordinates. Both types of outputs are acceptable for my workflows, but the values produced with something like "%.2f" - 'printf' function parameter, or contain only 2 decimal digits after comma. Is there any way to control such behavior, without patching the therion source code, and get for example 3 digits after comma for database outputs? Workaround here is to produce .kml and then project it to desired coordinate system, but this requires a lot more work than simple dealing with .sql files. Both .sql files are attached

1 0

How to add a "navbox"-type box in plan and extend pdfs?
by Xavier Robert 16 Mar '20

16 Mar '20

Dear all, I do not know if this is a request for a new feature, or if this can easily be solved with the present-day options of Therion. With my caving club, I am working on relatively big caves (>10/20 km), and I am currently in charge of the survey synthesis. Almost each year, we add new explored passages to the general map, and we annually publish the crops on the passages newly explored/mapped in our caving club journal. To print the crops of the parts I am interesting for publishing, I am using selections with maps definitions. Nothing new until there. Recently, I had a request from some cavers: For these crops, they asked me to add to the map an inset with the general view of the cave (plan and/or extended elevation) and the location of the crop. Two Illustrator example are in attachement. With Therion I could do that (this is more or less what I have done for the attached Solitaire example): 1. by plotting the whole cave at very small scale (with the options symbol-hide group all / symbol-hide special north-arrow / symbol-hide special scale-bar / symbol-show line wall and all the statistics to off or empty) , 2. by adding a box manually on this first pdf with illustrator, where I want it and 3. by using the "map-image" command to add this tuned pdf on the final map of the crop. However, it will be a pain to do it manually each time I need to print a new part of the cave network. Thus, do you know if there is an easy way to do it with a semi-automatic method based on the map selection? I imagine that this should be possible as there are almost similar features for the Atlas mode (with the box \navbox). Can we transpose it to plan or extended views ? Otherwise a possible idea could be to add a new command for layout blocks like : map-box <x> <y> <n/s/e/w/ne/nw/se/sw/center> <scale/size> with for example: * <x> <y> : same definition as map-header or map-image * <n/s/e/w/ne/nw/se/sw/center> : same definition as map-header or map-image * <scale> : scale (in % of the page size? scale of the general map to use, like the base-scale or scale commands?) or size (in cm like for the width of the legend box?) of the box that contains the general map with the map-selection location In fact, that would be great! Infortunately, I am not a good coder... But do you thing this is easy to implement? Cheers, Xavier

1 0

Re: [Therion] New DEM data from NASA
by Benedikt Hallinger 07 Mar '20

07 Mar '20

here it comes :) It uses LIDAR data from austrian sourves, but should be able to be adapted accordingly. I hoe it gives some hints. Feel free to modify and share! >>>> Am 06.03.2020 um 12:26 schrieb Wookey <wookey(a)wookware.org>: >>>>> >>>>>> On 2020-03-06 09:02 +0100, Benedikt Hallinger wrote: >>>>>>> >>>>>>>> I have a (german commented) bash script doing this. >>>>>>>>> >>>>>>>>>> Only thing is that it is hatdcoded fir a specific case, but it shows the commands imvolved. >>>>>>>>>>> >>>>>>>>>>>> Should i post it to you? >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Post it here. I doubt if Paweł is the only one interested. >>>>>>>>>>>>> >>>>>>>>>>>>> Wookey >>>>>>>>>>>>> -- >>>>>>>>>>>>> Principal hats: Linaro, Debian, Wookware, ARM >>>>>>>>>>>>> http://wookware.org/ >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> Therion mailing list >>>>>>>>>>>>> Therion(a)speleo.sk >>>>>>>>>>>>> https://mailman.speleo.sk/listinfo/therion

2 4

New DEM data from NASA
by Martin Sluka 06 Mar '20

06 Mar '20

https://www.gislounge.com/updated-global-elevation-data-released-by-nasa/ Odesláno z iPhonu

4 6

Export EE as .3D and ignore "survey does not exist"
by Rhys Tyers 05 Mar '20

05 Mar '20

Hello, I have two questions: 1) Is it possible to export an extended elevation as a 3D file (like survex does)? For the purpose of 'debugging' the extends etc. 2) Is it possible to ignore "survey does not exist" errors? I.e. I have a file with all the extend commands in and I just want the relevant ones to be applied, even if I am just looking at a small section. Thanks for any help, Rhys

3 3

Metapost variable macro suffixes
by Tarquin Wilton-Jones 02 Mar '20

02 Mar '20

Hi folks, hoping someone who really understands Metapost can give me a suggestion since I cannot find it in any manuals. In Therion's Metapost, there are a couple of wildcard suffixed macros like this: vardef p_label@#(expr txt,pos,rot,mode) I have a need to call the different ones depending on the value of a pair like this: if A = (-1,1): p_label.ulft(thetext,P,R,style); elseif A = (0,1): p_label.top(thetext,P,R,style); ... more ... Based on the value of another variable, I need to run a different macro instead, which also has its own suffixes, which match the suffixes above: if A = (-1,1): if Foo = "a" thelabel.ulft(txt, pos); ... other stuff ... else: p_label.ulft(thetext,P,R,style); fi; elseif A = (0,1): if Foo = "b" thelabel.ulft(txt, pos); ... other stuff ... else: p_label.top(thetext,P,R,style); fi; ... more ... This quickly gets tedious, since the same code gets repeated over and over again, just with a different suffix each time. In Metapost, is it possible to store the suffix in a variable, then use it when calling the macro like so? if A = (-1,1): sfx:="ulft"; elseif A = (0,1): sfx:="top"; ... if Foo = "b" thelabel.<sfx>(txt, pos); ... other stuff ... else: p_label.<sfx>(thetext,P,R,style); fi; Thanks for any advice. Tarquin

2 2

World Magnetic Model
by kevin dixon 28 Feb '20

28 Feb '20

The last Therion release 5.4.3 is dated 01 Feb 2019. There has in recent years been a significant change of the Magnetic North Pole location, less so for the Geomagnetic South Pole: https://ngdc.noaa.gov/geomag/GeomagneticPoles.shtml Given the above, an out of cycle World Geomagnetic Model WMM2015v2 was released 04 Feb 2019. When will this update appear in Survex and Therion ? Thanks, Kevin Dixon

4 4

Re: [Therion] Need metapost wizard: new text label
by alastair gott 27 Feb '20

27 Feb '20

Sorry Beni you'll get this twice as I forgot to send to the list... The function def p_continuation (I know not the one you're using). has the line: if known(ATTR__text) and picture(ATTR__text): This seems to work, but not sure if it's because of the next few lines: % set labeling color to light orange push_label_fill_color(0.8, 0.8, 0.0); % draw filled label with text next to symbol ? p_label.urt(ATTR__text,(.5u,-.25u) transformed T,0.0,8); % restore original labeling color pop_label_fill_color; fi; It seems like the P_label.urt is fairly important, as this is what tells it where to place the label, in this case in the upper right (.urt) and then tells it to put the attr_text there. [cid:4b8816ef-abef-4e06-8047-3dee7b44eed9] https://books.google.co.uk/books?id=hh6rdgZ9m3MC&pg=PA65&lpg=PA65&dq=p_labe… Regards, Alastair Gott. AlastairGott(a)hotmail.com, M: 07931779380. ________________________________ From: Therion <therion-bounces(a)speleo.sk> on behalf of Benedikt Hallinger <beni(a)hallinger.org> Sent: 26 February 2020 22:47 To: therion(a)speleo.sk <therion(a)speleo.sk> Subject: Re: [Therion] Need metapost wizard: new text label Hello, meanwhile i tried to play more with this. I'm nearly there, however i still have no clue how to read out the text attribute i attached to the symbol in the th2. "txt := ATTR__text;" throws metapost out the window. The point is defined like this: point 234.0909090909091 626.3636363636364 u:mappe -attr text 1234 Layout i came up with so far (does not support scaling/alignment/rotation, but thats fine so far): --------------------- layout m # Symbol to denote assigned survey. # If option -attr text <string> is given, it will be used; otherwise current survey is shown. code metapost def p_u_mappe(expr pos, theta, sc, al) = T:=identity aligned al rotated theta scaled sc shifted pos; % GET LABEL TEXT: string txt; txt := "123"; %txt := ATTR__text; % does not work. How do i get the value from ' -attr text "345" '? if known(ATTR__text): txt := ATTR_text; % NEVER evaluates to TRUE!?!? else: txt := ATTR__survey; fi; % DRAW LABEL: lab:=thelabel(txt, pos); process_label(pos, 0.001); % BORDER: pickup PenA; % border thickness interim bboxmargin:=6.5bp; % padding border->text q:=((bbox lab) smoothed 4); % smoothness of corners draw q; enddef; initsymbol("p_u_mappe"); endcode endlayout --------------------- Am 2020-02-19 18:34, schrieb Benedikt Hallinger: > Hi there, > i need some new point symbol (text label). Its a simple text on white > color within a box with rounded corners, like the attached image. > > > My metapostskills are not good enough to get this to work... > > For now i would be happy to have such a user point symbol. > It would be important that it scales well and react to xtherions > direction setting. > > Optional it would be cool if the default symbol could show the current > survey identifier of the nearest station in the scrap and maybe also > the nearest next survey. > But this information could also be maintained manually for now. > > Is there someone here for my rescue? :) > Thanks in advance, > Beni _______________________________________________ Therion mailing list Therion(a)speleo.sk https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailman.s…

1 0

Possibly useful scrap creation script and VS Code extension
by Rhys Tyers 24 Feb '20

24 Feb '20

Hello everyone, **Scrap Bootstrap Script** I recently made a script that and it was suggested it might be useful for others. The context is that I am involved in a redrawing exercise where we have survex data for a large system and separately drawn surveys that we are now converting into Therion format. We have converted all the svx files to th and are now going through and redrawing them. To speed up the start of the drawing I made a script that takes the centreline data in the `.th` file and creates a `.th2` scrap file with all of the stations already in a scrap and a 'fake' centerline to draw around. Find it here: https://github.com/tr1813/migresurvey/blob/master/scripts/initiliase_map.py Yes, it is a bit hacky :P If there is a better way to do it, please let me know. We are using inkscape and the Inkscape therion extension so I don't know if this is useful for people drawing in the Therion editor. **VS Code Therion Extension** I also use VS Code to edit the files so I made a Therion VS Code extension that includes some basic syntax highlighting, formatting, and also a command that does the same thing as the aforementioned script. Find it here: https://marketplace.visualstudio.com/items?itemName=rhystyers.therion If anyone wants to use it I'm very happy to take suggestions on additions and improvements. I'm planning on trying to give it autocomplete next (for survey/scrap/map names). Rhys

1 0