Hi folks, some questions about the join command. We join scraps to make nice pdf-maps or other two-dimensional maps like svg, xhtml and kml. Of course, this is a very good reason. 1. But are there other reasons to do it? For instance, do joins have any influence on other exports, like the maps (walls) in aven or the models in loch? I did a simple preliminary test, and couldn't find any difference whether the scraps were joined or not. 2. Do you always joins the scraps? Are there some situations when its not necessary, or even wrong, to join scraps? Torstein Finnesand Norway
Martin, if scraps are in the same survey do they need joining to morph. -----Original Message----- From: therion-bounces@speleo.sk [mailto:therion-bounces@speleo.sk] On Behalf Of Martin Sluka Sent: 24 August 2015 17:59 To: List for Therion users Subject: Re: [Therion] The goal with joining scraps
24. 8. 2015 v 18:35, torstein finnesand <torstein.finnesand@gmail.com>:
2. Do you always joins the scraps? Are there some situations when its not necessary, or even wrong, to join scraps?
Only if morphing is necessary. m. _______________________________________________ Therion mailing list Therion@speleo.sk http://mailman.speleo.sk/mailman/listinfo/therion
24. 8. 2015 v 19:33, Nick Bairstow <Nick@pff.uk.com>:
Martin, if scraps are in the same survey do they need joining to morph.
Scraps are part of map, not a survey. These are two independent things in therion. If I’ll redraw old handmade map to therion I’ll don’t need morphing usually. When there are sketches from different sources usually there is needs of morphing. Another situation I use joins is complicated join of scraps in several levels ets. m.s.
I have found I only need to join scraps when they are not contiguous (ie each line entity, such as walls that continue across the 'join', are not 'snapped' together) within the same th2 file. ie if the scraps are not drawn touching each other in the same th2 file, a join is helpful, or if adjacent scraps are in different th2 files a join is helpful, or in any situation where there the drawing is not proportional to the survey network the morphing may cause walls to pull apart, and so a join will be helpful, or as Martin indicated, complicated multi-passage junctions. My recollection from my own datasets is that the join transformation acts equally on map and model outputs (I would be concerned if different export types gave different shapes). If the scraps give a clean join without any explicit join statement, then I do not use it, as that just results in unnecessary complexity, and no change in the output. If you make future changes to a 'joined' scrap, it is a good idea to comment out the join temporarily, otherwise the local morphing caused by join statement will mask you edits, making for a very confusing time. Bruce -----Original Message----- From: therion-bounces@speleo.sk [mailto:therion-bounces@speleo.sk] On Behalf Of torstein finnesand Sent: Tuesday, 25 August 2015 4:36 a.m. To: therion@speleo.sk Subject: [Therion] The goal with joining scraps Hi folks, some questions about the join command. We join scraps to make nice pdf-maps or other two-dimensional maps like svg, xhtml and kml. Of course, this is a very good reason. 1. But are there other reasons to do it? For instance, do joins have any influence on other exports, like the maps (walls) in aven or the models in loch? I did a simple preliminary test, and couldn't find any difference whether the scraps were joined or not. 2. Do you always joins the scraps? Are there some situations when its not necessary, or even wrong, to join scraps? Torstein Finnesand Norway _______________________________________________ Therion mailing list Therion@speleo.sk http://mailman.speleo.sk/mailman/listinfo/therion
24. 8. 2015 v 22:30, Bruce <bruce@tomo.co.nz>:
If you make future changes to a 'joined' scrap, it is a good idea to comment out the join temporarily, otherwise the local morphing caused by join statement will mask you edits, making for a very confusing time.
Anyway, you may add to your layout command: "debug on“ When exporting PDF, Therion generated three colour different overlaying maps with situation before joining and morphing, situation after first step of morphing and final situation. Yellow points and lines indicate the maximal movement of objects. m.
participants (4)
-
Bruce -
Martin Sluka -
Nick Bairstow -
torstein finnesand