December 2008 - Therion

Cave Sketches don't offset
by Bruce Mutton 23 Jan '09

23 Jan '09

And Again; To get a quick preview of what my finished map will look like I've added some survey stations and cave sketches to my scraps. These plot nicely until I want to offset the map in which the scrap and sketch is contained. When the map is offset, the survey stations plot in the correctly offset location, but the sketch plots (incorrectly) in it's original location. Am I doing something wrong or is this a bug? Bruce

3 3

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

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

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 37, Issue 15
by Dave Clucas 01 Jan '09

01 Jan '09

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. On 31 Dec 2008, 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 (Stefan Oswald) > 2. Re: Using metapost code examples (Martin Budaj) > 3. Re: Using metapost code examples (Wookey) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 30 Dec 2008 13:01:17 +0100 > From: "Stefan Oswald" <stefan_oswald(a)gmx.at> > Subject: Re: [Therion] Using metapost code examples > To: therion(a)speleo.sk > Message-ID: <20081230120117.233970(a)gmx.net> > Content-Type: text/plain; charset="iso-8859-1" > > Hi, > > The size is controlled by the factor before the u. > (symbolsize:=1.0u; %Factor*u; Factor=size of the blocks change 1.0 > as you want) >> Does this apply to each instance of a block or is it a >> global definition. > This overrules the point_block sizes in the whole plan compiled. > Size canging/definition of a single block is, as far as i know, not > possible and not projected? > > The problem was (with other symbols it is still the case, a solution > could be, for example an layout command for small symbols) that with > small caves in small scales the normative symbol size is too large, > so it might happen that you only see a small part of the symbol in a > narrow passage on small scale. > You can handle this problem with block_points and block_area in UIS > as in described in wiki by changing the factor before the "u". > > Gl?ck Tief, Stefan > > -------- Original-Nachricht -------- >> Datum: Tue, 30 Dec 2008 12:00:01 +0100 >> Von: therion-request(a)speleo.sk >> An: therion(a)speleo.sk >> Betreff: Therion Digest, Vol 37, Issue 14 > >> 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. Using metapost code examples (Dave Clucas) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Tue, 30 Dec 2008 19:00:56 +0800 >> From: Dave Clucas <dave(a)daveclucas.com> >> Subject: [Therion] Using metapost code examples >> To: therion(a)speleo.sk >> Message-ID: <2CDC217E-E91E-4780-A35C-F6B719CC9D32(a)daveclucas.com> >> Content-Type: text/plain; charset="us-ascii"; Format="flowed"; >> DelSp="yes" >> >> Looking at the metapost examples in the Wiki it appears that a block >> symbol can be defined or redefined which allows the size of the block >> to be changed. Does this apply to each instance of a block or is it a >> global definition. How do you specify the size of the block when you >> place it in the drawing? >> >> code metapost >> def p_blocks_UIS (expr pos,theta,sc,al)= >> symbolsize:=1.0u; %Factor*u; Factor=size of the blocks >> U:=(.5u,.5u); >> T:=identity aligned al rotated theta scaled sc shifted pos; >> pickup PenC; >> thdraw (.0symbolsize,.0symbolsize)--(1.0symbolsize,-. >> 5symbolsize)--(0.0symbolsize,-1.5symbolsize)-- >> (-1.0symbolsize,-1.0symbolsize)--cycle; >> thdraw (.5symbolsize,-.25symbolsize)--(1.0symbolsize,. >> 5symbolsize)--(0.0symbolsize,1.5symbolsize)--(-0.5symbolsize,. >> 5symbolsize); >> thdraw (.0symbolsize,.0symbolsize)--(.0symbolsize,.5symbolsize)-- >> (-1.5symbolsize,.5symbolsize)--(-1.5symbolsize,-0.5symbolsize)-- >> (-0.5symbolsize,-0.5symbolsize); >> enddef; >> endcode >> >> >> >> Dave Clucas >> email:dave@daveclucas.com >> Website: http://daveclucas.com >> http://mycaves.org >> Skype: daveclucas >> >> >> >> >>

2 1

Re: [Therion] Using metapost code examples
by Stefan Oswald 30 Dec '08

30 Dec '08

Hi, The size is controlled by the factor before the u. (symbolsize:=1.0u; %Factor*u; Factor=size of the blocks change 1.0 as you want) >Does this apply to each instance of a block or is it a >global definition. This overrules the point_block sizes in the whole plan compiled. Size canging/definition of a single block is, as far as i know, not possible and not projected? The problem was (with other symbols it is still the case, a solution could be, for example an layout command for small symbols) that with small caves in small scales the normative symbol size is too large, so it might happen that you only see a small part of the symbol in a narrow passage on small scale. You can handle this problem with block_points and block_area in UIS as in described in wiki by changing the factor before the "u". Glück Tief, Stefan -------- Original-Nachricht -------- > Datum: Tue, 30 Dec 2008 12:00:01 +0100 > Von: therion-request(a)speleo.sk > An: therion(a)speleo.sk > Betreff: Therion Digest, Vol 37, Issue 14 > 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. Using metapost code examples (Dave Clucas) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 30 Dec 2008 19:00:56 +0800 > From: Dave Clucas <dave(a)daveclucas.com> > Subject: [Therion] Using metapost code examples > To: therion(a)speleo.sk > Message-ID: <2CDC217E-E91E-4780-A35C-F6B719CC9D32(a)daveclucas.com> > Content-Type: text/plain; charset="us-ascii"; Format="flowed"; > DelSp="yes" > > Looking at the metapost examples in the Wiki it appears that a block > symbol can be defined or redefined which allows the size of the block > to be changed. Does this apply to each instance of a block or is it a > global definition. How do you specify the size of the block when you > place it in the drawing? > > code metapost > def p_blocks_UIS (expr pos,theta,sc,al)= > symbolsize:=1.0u; %Factor*u; Factor=size of the blocks > U:=(.5u,.5u); > T:=identity aligned al rotated theta scaled sc shifted pos; > pickup PenC; > thdraw (.0symbolsize,.0symbolsize)--(1.0symbolsize,-. > 5symbolsize)--(0.0symbolsize,-1.5symbolsize)-- > (-1.0symbolsize,-1.0symbolsize)--cycle; > thdraw (.5symbolsize,-.25symbolsize)--(1.0symbolsize,. > 5symbolsize)--(0.0symbolsize,1.5symbolsize)--(-0.5symbolsize,. > 5symbolsize); > thdraw (.0symbolsize,.0symbolsize)--(.0symbolsize,.5symbolsize)-- > (-1.5symbolsize,.5symbolsize)--(-1.5symbolsize,-0.5symbolsize)-- > (-0.5symbolsize,-0.5symbolsize); > enddef; > endcode > > > > Dave Clucas > email:dave@daveclucas.com > Website: http://daveclucas.com > http://mycaves.org > Skype: daveclucas > > > > >

3 2

Using metapost code examples
by Dave Clucas 30 Dec '08

30 Dec '08

Looking at the metapost examples in the Wiki it appears that a block symbol can be defined or redefined which allows the size of the block to be changed. Does this apply to each instance of a block or is it a global definition. How do you specify the size of the block when you place it in the drawing? code metapost def p_blocks_UIS (expr pos,theta,sc,al)= symbolsize:=1.0u; %Factor*u; Factor=size of the blocks U:=(.5u,.5u); T:=identity aligned al rotated theta scaled sc shifted pos; pickup PenC; thdraw (.0symbolsize,.0symbolsize)--(1.0symbolsize,-. 5symbolsize)--(0.0symbolsize,-1.5symbolsize)-- (-1.0symbolsize,-1.0symbolsize)--cycle; thdraw (.5symbolsize,-.25symbolsize)--(1.0symbolsize,. 5symbolsize)--(0.0symbolsize,1.5symbolsize)--(-0.5symbolsize,. 5symbolsize); thdraw (.0symbolsize,.0symbolsize)--(.0symbolsize,.5symbolsize)-- (-1.5symbolsize,.5symbolsize)--(-1.5symbolsize,-0.5symbolsize)-- (-0.5symbolsize,-0.5symbolsize); enddef; endcode Dave Clucas email:dave@daveclucas.com Website: http://daveclucas.com http://mycaves.org Skype: daveclucas

1 0

Preview from other map-levels
by Bruce Mutton 28 Dec '08

28 Dec '08

Hi all Just when I thought I was getting comfortable with hierarchies of maps with various combinations of previews and offsets. I can no longer put off the realisation that I don't understand how to display a preview if Therion decides it will not do it with the default behaviour. I suspect the solution lies with the revise command; but how to make it work? The following text from the therion book makes reasonable sense, and generally works just fine. "_ preview <above/below> <other map id> will put the outline of the other map in the specified preview position relative to the current map. Preview is displayed only if the map is in the map-level level as specified by the select command. Use the revise command if you want to add maps from higher levels to the preview." However the following does not seem to give enough information to proceed. "`revise' Description: This command is used to set or change properties of an already existing object. Syntax: The syntax of this command for object created with \single line" command is revise id [-option1 value1 -option2 value2 ...] For objects created with \multi line" commands is syntax following revise id [-option1 value1 -option2 value2 ...] ... optionX valueX data ... endrevise Context: all Arguments: The id stands for object identifier (the id of an object you want to revise must always be specified)." Tips on how to refer to a previously defined map (easy?) and which options need to be changed to which values(not so easy?)? A small example anyone? Thanks Bruce

1 0

Context point air-draught example from Therion Book fails
by Bruce Mutton 27 Dec '08

27 Dec '08

Seasons Greetings! In one of my scraps, the line; point 517.0 -483.0 label -text "15 Dec 2008" -scale xs -context point air-draught produces an error, D:\Program Files\Therion\therion.exe: error -- Late08RPElev_02.th2 [10] -- object context not allowed -- point air-draught This example is taken almost exactly from footnote 20, page 24 of the therion book. Is there something I'm doing wrong? (Still using 5.2.3) Bruce

1 0

Two scraps, one river...
by Fabio Kok Geribello 24 Dec '08

24 Dec '08

Hi all, We´re using Therion to produce maps for many caves in Brazil but I´m having some poor results wen I have to join scraps with intersecting areas. I know that Therion is only able to join lines so how do I represent a river, for exemple that spreads between two or more scraps? Usualy there is a gap appearing due to the scraps adjustments Is there any trick to solve that? Thank you, Fabio

3 5