- Therion - speleo.sk

Shane Fryer/SEKI/NPS is out of the office.
by Shane_Fryer＠nps.gov 16 Jan '09

16 Jan '09

I will be out of the office starting 01/16/2009 and will not return until 02/17/2009. I will respond to your message when I return.

1 0

Label Only the Grids You Choose
by Bruce Mutton 15 Jan '09

15 Jan '09

This morning's bright idea was a way of labelling only selected grids (or indeed any fixed point) in my finished plan view maps. I make a small dummy survey that contains fixed survey stations only at the grid co-ordinates that I wish to label. This is referenced in my CaveINDEX.th file using the input statement. Then a small scrap that contains the above roughly placed survey stations and on top of these a point label for each of the x and y co-ordinate labels. Advantages: Only get labels where you want them (a big advantage). Can format them as you see fit. Disadvantages: A little bit labour intensive. Subject to user error, as the co-ord text is manually input (maybe this is a contender for a new therion object along the lines of the existing 'point altitude' eg point x-coord and point y-co-ord) Survex, if installed points out that you have some disconnected stations - not really a problem. The number of survey stations reported by Therion is a few too many. The attached files illustrate. Note that each apparently single point is actually three points superposed on each other. Right-click each point to see definition of the underlying point(s). Enjoy Bruce

1 0

Pb with LRUD on null length and vertical shots
by Xavier Pennec 15 Jan '09

15 Jan '09

To specify the LRUD at the beginning of a leg (or when a is a sudden change) it is usual in toporobot to make a null (or very small) length shot (this is also usual in other survey softwares such as vtopo). The intended behavior is the one of shot E with the therion syntax. In therion, it seems that this does not work, since below a certain length the shot is ploted as a vertical: in the example join, shots A and B are ploted as shot F. The problem is that rewriting old surveys of type A as E is quite a work prone to errors, and putting a length sufficient to have it drawn horizontally (such as in shot D) is really changing the measurements. The second problem is that vertical shots are always oriented towards the north, even though one specifies a bearing to indicate where is the right and the left. This makes it difficult to draw directly on the xvi file. Is that behavior intentional or is that due to a division by zero which is not handles correctly? Xavier set XVIgrids {10.0 m} set XVIstations { { -491.54 -115.94 A0} { -491.54 -115.94 A1} { -480.51 -37.99 A2} { -297.05 -85.24 B0} { -297.05 -85.24 B1} { -286.02 -7.28 B2} { -102.56 -54.53 C0} { -102.56 -54.13 C1} { -91.54 23.82 C2} { 91.93 -23.43 D0} { 92.32 -19.49 D1} { 103.35 58.07 D2} { 286.02 7.28 E0} { 297.05 84.84 E2} { 480.51 37.99 F0} { 480.51 37.99 F1} { 491.54 115.94 F2} } set XVIshots { { -491.54 -115.94 -491.54 -115.94 -524.61 -167.13 -479.72 -167.13 -479.72 -72.64 -524.61 -72.64} { -491.54 -115.94 -480.51 -37.99 -524.28 -111.31 -498.05 -35.51 -459.07 -41.02 -479.84 -117.60} { -491.54 -115.94 -297.05 -85.24} { -297.05 -85.24 -297.05 -85.24 -330.12 -136.42 -285.24 -136.42 -285.24 -41.93 -330.12 -41.93} { -297.05 -85.24 -286.02 -7.28 -329.79 -80.61 -303.57 -4.80 -264.58 -10.32 -285.35 -86.89} { -297.05 -85.24 -102.56 -54.53} { -102.56 -54.53 -102.56 -54.13 -135.63 -54.53 -135.63 -54.13 -90.75 -54.13 -90.75 -54.53} { -102.56 -54.13 -91.54 23.82 -135.30 -49.50 -109.08 26.30 -70.10 20.79 -90.86 -55.79} { -102.56 -54.53 91.93 -23.43} { 91.93 -23.43 92.32 -19.49 59.02 -20.13 59.42 -16.20 104.08 -20.66 103.68 -24.60} { 92.32 -19.49 103.35 58.07 59.58 -14.83 85.81 60.56 124.78 55.02 104.02 -21.15} { 91.93 -23.43 286.02 7.28} { 286.02 7.28 297.05 84.84 253.28 11.94 279.51 87.34 318.49 81.80 297.72 5.62} { 286.02 7.28 480.51 37.99} { 480.51 37.99 480.51 37.99 447.44 -13.19 492.32 -13.19 492.32 81.30 447.44 81.30} { 480.51 37.99 491.54 115.94 447.77 42.62 473.99 118.43 512.98 112.91 492.21 36.34} } set XVIgrid {-885.236 -509.646 393.701 0.0 0.0 393.701 4 2} encoding utf-8 ## Gather all data togother survey Topocave -title "Cave 1" centerline date 1991 data normal from to length compass clino left right up down units compass grads units clino degrees A0 A1 0.0 9 4 0.84 0.30 1.10 1.30 A1 A2 2 9 4 0.45 0.55 0.97 1.30 A0 B0 5 90 0 - - - - B0 B1 0.001 9 4 0.84 0.30 1.10 1.30 B1 B2 2 9 4 0.45 0.55 0.97 1.30 B0 C0 5 90 0 - - - - C0 C1 0.01 9 4 0.84 0.30 1.10 1.30 C1 C2 2 9 4 0.45 0.55 0.97 1.30 C0 D0 5 90 0 - - - - D0 D1 0.1 9 4 0.84 0.30 1.10 1.30 D1 D2 2 9 4 0.45 0.55 0.97 1.30 D0 E0 5 90 0 - - - - E0 E2 2 9 4 [0.84 0.45] [0.30 0.55] [1.10 0.97] [1.30 1.30] E0 F0 5 90 0 - - - - F0 F1 2 90 -90 0.84 0.30 1.10 1.30 F1 F2 2 9 4 0.45 0.55 0.97 1.30 endcenterline endsurvey encoding utf-8 ##XTHERION## xth_me_area_adjust -127.994 -128.002 1309.109 521.699 ##XTHERION## xth_me_area_zoom_to 50 ##XTHERION## xth_me_image_insert {393.702 1 1.0} {393.704 A0} test_lg0.xvi 0 {} encoding utf-8 source test_lg0 layout map_layout symbol-show line survey symbol-show point station # debug on north true scale 1 100 units metric color map-fg 80 grid bottom grid-size 10 10 10 m grid-coords all transparency on opacity 80 surface bottom #surface-opacity 80 endlayout export map -o test_lg0.pdf -layout map_layout -fmt pdf export map -o test_lg0.xvi -layout map_layout -fmt xvi export model -o test_lg0.lox

3 5

How do I locate the object causing an error
by Bruce Mutton 15 Jan '09

15 Jan '09

Apologies for asking a question previously answered. Someone asked this about a year ago, and Stacho or Martin provided an answer, unfortunately I can not find it in the forum archives. The partial log file transcript below suggests to me that there is a minor problem with my wall drawing in or after [181] and a fatal problem with something in or after [186]. How do I locate the objects referred to by the numbers in square brackets? (This particular one is odd, 'cos it worked fine yesterday, and all my th-config files that compile individual components of this master file still compile perfectly - must be an inadvertent change I made somewhere.) Thanks Bruce [173] [174] [175] [176] [177] [178] [179] [180] [181] [Warning: scrap outline intersects itself in scrap Late08ROPlan_s2(a)Late08.Bulme r] [182] [183] [184] [185] [186] ! angle(0,0) is taken as zero. l_arrow_SKBB->....rotated(angle(thdir((EXPR0),0))+ 90)shifted(point0of(EXPR0)... l_mapconnection->....PenB);l_arrow_SKBB((EXPR0),3) ;thdrawoptions(); l.18855 ...ion(((229.38,96.96) -- (229.38,96.96))) ; The `angle' between two identical points is undefined. I'm zeroing this one. Proceed, with fingers crossed. ! angle(0,0) is taken as zero.

2 2

Problem with object types
by Xavier Pennec 15 Jan '09

15 Jan '09

I have a problem with object types in therion: it seems that it is not possible to have a survey and a station which have the same name (see example included which perfectly compiles if one changes the cave1 and cave 2 to Cave1 and Cave2 for either the station names or the survey names). Is that a normal behavior? It seems to me that a correct typing should allow having the same names for surveys, stations and maps. Xavier encoding utf-8 ## Gather all data togother survey cave1 -title "Cave 1" centerline date 1991 station cave1 "Cave 1" entrance equate cave1 0 data normal from to length compass clino ignoreall units compass grads units clino degrees 0 1 13.8 240 2 endcenterline endsurvey survey cave2 -title "Cave 2" centerline date 1991 station cave2 "Cave 2" entrance equate cave2 0 data normal from to length compass clino ignoreall units compass grads units clino degrees 0 1 45 140 0 endcenterline endsurvey survey surface -title "Surface measurements" centerline date 1991 equate cave1 0 equate cave2 1 data normal from to length compass clino ignoreall units compass grads units clino degrees 0 1 5 100 0 endcenterline endsurvey ## index all connection points to link them together equate cave1 cave1@cave1 equate cave2 cave2@cave2 equate cave1 cave1@surface equate cave2 cave2@surface encoding utf-8 source test source ## Rerefence file with all Fixed points centerline cs UTM31 fix cave1 391300 4891742 2160 10 10 20 # GPS accuracy is not so good endcentreline endsource layout map_layout symbol-show line survey symbol-show point station # debug on north true scale 1 100 units metric color map-fg altitude grid bottom grid-size 50 50 10 m cs EPSG:27572 ## Lambert II transparency on opacity 80 surface bottom #surface-opacity 80 endlayout export map -o test.pdf -layout map_layout -fmt pdf export model -fmt survex -o test.3d #!CAVE LIST EXPORT ## cs EPSG:27573 ## Lambert III export cave-list -o Coordonnees.html -location on

3 6

Map-list output wishlist request
by Bruce Mutton 12 Jan '09

12 Jan '09

Continuing the theme of list outputs. Does anyone see the need for a list output file that expands on and compliments the tree view of maps available in the Map Structure pane of the XTherion compiler window? I'm just noticing that I have 46 maps/sub-maps for a 3.5km cave (that is moderately complex) and it will have a reasonable number more before it's done. Generally my naming convention keeps them in order for me, but I can see that an output listing them will make management easier and more reliable. There is only so much information that can be encapsulated in an object name, and if too much is included it is prone to user error. My suggestion is (using the existing html list outputs as a basis) that the table be hierarchical/collapsible in the same way as the existing 'caves' and 'surveys' outputs. The column outputs could be; id projection [spec] title object type date author defined (ie survey/scrap/map) (in which object/file?) bulmer elev 270 deg Bulmer Cave map 2008-2009 BulmerINDEX.th late08 elev 270 deg Late08 Series map 2008 .\Late08\Late08INDEX.th rm elev 270 deg survey rm map 2008 .\Late08\SurveyRM.th Late08RMPlan_s1 elev 270 deg scrap 2008 RBM .\Late08\RMElev.th2 Late08RMPlan_s2 elev 270 deg scrap 2009 MB .\Late08\RMElev.th2 Similarly, perhaps an 'id' column could be added to the 'caves' and 'surveys' output lists, as I expect Therion requires an id, but the titles are probably optional; And while I'm at it, the 'surveys' output could also include a 'date' and 'author' column. Thoughts anyone? Bruce

1 0

therion 5.2.5
by Martin Sluka 09 Jan '09

09 Jan '09

Unstable version is 5.2.5, released on Jan 9, 2009 m.s.

1 0

russia
by Sau --- 08 Jan '09

08 Jan '09

Where i can found Russia Therion group? or any contacts with active members.

3 4

Re: [Therion] Therion Digest, Vol 38, Issue 1
by Dave Clucas 02 Jan '09

02 Jan '09

It would be better, I think, to have an attribute for the scale (Factor) with values of say 1-10 which could be passed to and evaluated by the definition. But first, I was checking to see if I was missing something in the way Stefan's def works. On 2 Jan 2009, at 19:00, therion-request(a)speleo.sk wrote: > Send Therion mailing list submissions to > therion(a)speleo.sk > > To subscribe or unsubscribe via the World Wide Web, visit > http://mailman.speleo.sk/mailman/listinfo/therion > or, via email, send a message with subject or body 'help' to > therion-request(a)speleo.sk > > You can reach the person managing the list at > therion-owner(a)speleo.sk > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Therion digest..." > > > Today's Topics: > > 1. Re: Using metapost code examples (Bruce Mutton) > 2. improved script for converting SVG to th2 (Thomas Holder) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 02 Jan 2009 11:58:05 +1300 > From: Bruce Mutton <bruce.mutton(a)paradise.net.nz> > Subject: Re: [Therion] Using metapost code examples > To: 'List for Therion users' <therion(a)speleo.sk> > Message-ID: <2A837C7D04834F3FA9928B5D91A18CF0@JUICEBRAIN> > Content-Type: text/plain; charset="us-ascii" > > "I'm afraid that's what I thought. We have the situation here in > Mulu where > the main passages are 50m wide with house sized boulders with side > passages > a mere 5m wide and small car size boulders so ideally we need a > mixture of > block sizes to play with. And of course chambers the size of football > fields." > > > > I have not tried this but surely the solution is just a matter of > creating a > number of similar metapost code definitions, that differ only by the > scale > factor as mentioned by Stefan, and named say blocks_xl, blocks_l, > blocks_s, > blocks_xs. Then add these additional definitions to the legend and > configuration file as in the bats example in the last few pages of the > Therion book. We would then have 5 different block scales that > could be > used at will in any drawing. > > > > I'm probably being naive again, but it looks in concept very simple, > as we > have a code example as a template. Any reason why not? > > > > Regards > > Bruce > > > > > > > > > > > >

1 0

improved script for converting SVG to th2
by Thomas Holder 02 Jan '09

02 Jan '09

Hi, there is a new SVG to th2 converter, implemented as an export plugin for inkscape. Check the wiki page: http://therion.speleo.sk/wiki/doku.php?id=inkscape Regards, Thomas

1 0