November 2023 - 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

Turning LIDAR point clouds into cave maps
by Bill Gee 12 Dec '23

12 Dec '23

Hello everyone - This is probably more of a general practices question than something specific to Therion. Among the group there is likely to be some experience with this. I hope at minimum someone can guide me to a place for further learning. A few years ago Apple released a very high-end smartphone which has a LIDAR feature (iPhone 12 Pro). There are a few more models now which have it. I have heard of some people using this to create cave maps. There is much I do not understand. Has anyone in the group taken the point cloud from an Apple LIDAR scan and turned it into a Therion cave map? If so, I am very interested in the details of the process. The biggest issue I see is this: How does the iPhone know where it is? There is no GPS in a cave. GPS is not accurate enough even if it did work. Inertial navigation also has big problems dealing with a cave environment. There are many other issues, but I think that is the big one. Thanks! -- =============== Bill Gee

10 11

scale option for lines
by Rodrigo Severo 06 Nov '23

06 Nov '23

Hi, Understanding Therion, bit by bit... I can't see the effects of scale option in lines. Can someone describe a situation where the lines are affected by the scale option? Regards, Rodrigo Severo

3 4

anchors and rebelays line options
by Rodrigo Severo 06 Nov '23

06 Nov '23

Hi, I am trying to understand the effect of the anchors and rebelays line options. I can´t visually see any difference in the outputed map and looking in the code, I can´t find a place where the TT_LINE_TAG_ROPE_ANCHORS and TT_LINE_TAG_ROPE_REBELAYS flags are used. I can only find where they are set. Can someone explain to me how to use them and how to see their effects? Regards, Rodrigo Severo

2 2

Setting map border framethickness to zero (off) -layout call order inconsistent
by Bruce Mutton 05 Nov '23

05 Nov '23

And just noticed this https://github.com/therion/therion/issues/425 Maybe related? Sent: Sunday, 5 November 2023 18:52 To: 'List for Therion users' <therion(a)speleo.sk> Subject: Setting map border framethickness to zero (off) -layout call order inconsistent OK, there is some strange behaviour wrt the order of layout processing, or at least which layout statement prevails in the case of a conflict. I took the basic rabbit cave example, and modified the thconfig slightly to give one of the exports conflicting layout calls: #CODE TO PUT BORDER AROUND MAP #----------------------------- layout LayoutMapBorder code tex-map \framethickness=0.5mm endcode endlayout LayoutMapBorder #CODE TO REMOVE BORDER AROUND MAP #----------------------------- layout LayoutRemoveMapBorder code tex-map \framethickness=0mm endcode endlayout LayoutRemoveMapBorder export map -projection extended -output rabbit-xelev.pdf \ -layout water-blue -layout-map-header 0 0 s -layout-map-header 0 110 sw \ -layout LayoutRemoveMapBorder -layout LayoutMapBorder The above export produces a map with header top-left and no border (green arguments prevail). If I swap the grey and green layout calls, I get a header bottom-left and a border (grey arguments prevail). So why are these layouts treated differently? Is it that layouts that contain tex are treated differently to layouts that do not? Bruce Sent: Friday, 3 November 2023 08:17 To: 'List for Therion users' <therion(a)speleo.sk <mailto:therion@speleo.sk> > Subject: Setting map border framethickness to zero (off) I have just now solved this problem. The error status must have been some combination of setting \framethickness to 0mm and the order in which I was calling layouts, although I cannot pin down why this would be the case. Anyway, setting \framethickness to 0mm does now remove a frame that was previously set in my project. The key to solving the problem as to why \framethickness was not responsive to a second call was that I was mistaken in my belief as to the order of layout calls in export commands. I always assumed the second layout called would be the second layout processed. Alas it seems to be the other way around and layouts in export commands are processed in reverse order. eg like this: export map -projection plan \ -layout LayoutProcessedLast \ -layout LayoutProcessedFirst \ -output ../Output/CavePlan.pdf At least that is what I deduce from the behaviour where there are conflicting \framethickness statements. Except I think I have evidence that for some layout content it is the other way around. Anyone else have any insights as to the order of layout processing in export commands? Bruce Sent: Monday, 30 October 2023 12:15 To: 'List for Therion users' <therion(a)speleo.sk <mailto:therion@speleo.sk> > Subject: Setting map border framethickness to zero (off) Good morning Probably a simple tex question. I often use this code to create a border around an exported map: code tex-map \framethickness=0.5mm >From time to time (in the same compilation run) I insert one exported map into another using map-image and usually the inserted map should not have a border. To date I have always arranged my layouts so that \framethickness is undefined while the initial map is exported, THEN set to 0.5 mm for the second map export. It occurred to me that with my project arrangment it would be more convenient to set the border to 0.5 mm (in a global layout) and THEN reset it to zero or undefined in a layout specific to only one of the exports. I have tried these two options: code tex-map \framethickness={} code tex-map \framethickness=0mm The first causes error (pdftex exit code 1) and the second draws a 0.5 mm border around both maps. How should I 'turn off' a map border if \framethickness has already been set? Regards Bruce

1 0

Setting map border framethickness to zero (off) -layout call order inconsistent
by Bruce Mutton 05 Nov '23

05 Nov '23

OK, there is some strange behaviour wrt the order of layout processing, or at least which layout statement prevails in the case of a conflict. I took the basic rabbit cave example, and modified the thconfig slightly to give one of the exports conflicting layout calls: #CODE TO PUT BORDER AROUND MAP #----------------------------- layout LayoutMapBorder code tex-map \framethickness=0.5mm endcode endlayout LayoutMapBorder #CODE TO REMOVE BORDER AROUND MAP #----------------------------- layout LayoutRemoveMapBorder code tex-map \framethickness=0mm endcode endlayout LayoutRemoveMapBorder export map -projection extended -output rabbit-xelev.pdf \ -layout water-blue -layout-map-header 0 0 s -layout-map-header 0 110 sw \ -layout LayoutRemoveMapBorder -layout LayoutMapBorder The above export produces a map with header top-left and no border (green arguments prevail). If I swap the grey and green layout calls, I get a header bottom-left and a border (grey arguments prevail). So why are these layouts treated differently? Is it that layouts that contain tex are treated differently to layouts that do not? Bruce Sent: Friday, 3 November 2023 08:17 To: 'List for Therion users' <therion(a)speleo.sk> Subject: Setting map border framethickness to zero (off) I have just now solved this problem. The error status must have been some combination of setting \framethickness to 0mm and the order in which I was calling layouts, although I cannot pin down why this would be the case. Anyway, setting \framethickness to 0mm does now remove a frame that was previously set in my project. The key to solving the problem as to why \framethickness was not responsive to a second call was that I was mistaken in my belief as to the order of layout calls in export commands. I always assumed the second layout called would be the second layout processed. Alas it seems to be the other way around and layouts in export commands are processed in reverse order. eg like this: export map -projection plan \ -layout LayoutProcessedLast \ -layout LayoutProcessedFirst \ -output ../Output/CavePlan.pdf At least that is what I deduce from the behaviour where there are conflicting \framethickness statements. Except I think I have evidence that for some layout content it is the other way around. Anyone else have any insights as to the order of layout processing in export commands? Bruce Sent: Monday, 30 October 2023 12:15 To: 'List for Therion users' <therion(a)speleo.sk <mailto:therion@speleo.sk> > Subject: Setting map border framethickness to zero (off) Good morning Probably a simple tex question. I often use this code to create a border around an exported map: code tex-map \framethickness=0.5mm >From time to time (in the same compilation run) I insert one exported map into another using map-image and usually the inserted map should not have a border. To date I have always arranged my layouts so that \framethickness is undefined while the initial map is exported, THEN set to 0.5 mm for the second map export. It occurred to me that with my project arrangment it would be more convenient to set the border to 0.5 mm (in a global layout) and THEN reset it to zero or undefined in a layout specific to only one of the exports. I have tried these two options: code tex-map \framethickness={} code tex-map \framethickness=0mm The first causes error (pdftex exit code 1) and the second draws a 0.5 mm border around both maps. How should I 'turn off' a map border if \framethickness has already been set? Regards Bruce

1 0

Problems generating the sketch KML file
by Brauli Torres 02 Nov '23

02 Nov '23

Hello, I have a problem generating the KML file of the sketch of one of the cavities in my system. Xtherion does not calculate the coordinates of the sketch and places it incorrectly in Google Earth. What do I have to do to force Xtherion to correctly calculate the sketch coordinates in KML? Detail of a piece of the KML file of the incorrect sketch: .. Polygon> <outerBoundaryIs> <LinearRing> <coordinates> nan,nan,0.00000000000000 nan,nan,0.00000000000000 nan,nan,0.00000000000000 ...</coordinates> </LinearRing> </outerBoundaryIs> </Polygon> <Polygon> <outerBoundaryIs> <LinearRing> <coordinates> nan,nan,0.00000000000000 nan,nan,0.00000000000000 nan,nan,0.00000000000000 nan,nan,0.00000000000000 nan,nan,0.00000000000000 nan,nan,0.00000000000000 ...</coordinates> </LinearRing> </outerBou ... On the other hand, if it generates the traverse KML correctly, Detail of a piece of the correct traverse KML file: ... ...<name>T97-24</name> <styleUrl>#ThSurveyLine</styleUrl> <MultiGeometry> <LineString><coordinates> -0.15632552379485,42.67499752311521,2418.00000000000000 -0.15655344552491,42.67507855478213,2421.28999999999996 </coordinates></LineString> <LineString><coordinates> -0.15632552379485,42.67499752311521,2418.00000000000000 -0.15629671968055,42.67489064219563,2410.57999999999993 </coordinates></LineString> <LineString><coordinates> -0.15625526310203,42.67494337019725,2437.57999999999993 -0.15624481424440,42.67491294488270,2437.90999999999985 ... Thank you very much for your help Brauli Torres Milla GEB -Grup d'Espeleologia de Badalona

2 3

Setting map border framethickness to zero (off)
by Bruce Mutton 02 Nov '23

02 Nov '23

I have just now solved this problem. The error status must have been some combination of setting \framethickness to 0mm and the order in which I was calling layouts, although I cannot pin down why this would be the case. Anyway, setting \framethickness to 0mm does now remove a frame that was previously set in my project. The key to solving the problem as to why \framethickness was not responsive to a second call was that I was mistaken in my belief as to the order of layout calls in export commands. I always assumed the second layout called would be the second layout processed. Alas it seems to be the other way around and layouts in export commands are processed in reverse order. eg like this: export map -projection plan \ -layout LayoutProcessedLast \ -layout LayoutProcessedFirst \ -output ../Output/CavePlan.pdf At least that is what I deduce from the behaviour where there are conflicting \framethickness statements. Except I think I have evidence that for some layout content it is the other way around. Anyone else have any insights as to the order of layout processing in export commands? Bruce From: Bruce Mutton <bruce(a)tomo.co.nz> Sent: Monday, 30 October 2023 12:15 To: 'List for Therion users' <therion(a)speleo.sk> Subject: Setting map border framethickness to zero (off) Good morning Probably a simple tex question. I often use this code to create a border around an exported map: code tex-map \framethickness=0.5mm >From time to time (in the same compilation run) I insert one exported map into another using map-image and usually the inserted map should not have a border. To date I have always arranged my layouts so that \framethickness is undefined while the initial map is exported, THEN set to 0.5 mm for the second map export. It occurred to me that with my project arrangment it would be more convenient to set the border to 0.5 mm (in a global layout) and THEN reset it to zero or undefined in a layout specific to only one of the exports. I have tried these two options: code tex-map \framethickness={} code tex-map \framethickness=0mm The first causes error (pdftex exit code 1) and the second draws a 0.5 mm border around both maps. How should I 'turn off' a map border if \framethickness has already been set? Regards Bruce

1 0