<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Abadi Extra Light";}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-ligatures:standardcontextual;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-NZ link="#0563C1" vlink="#954F72" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal>Bill<o:p></o:p></p><p class=MsoNormal>I’ve looked back through projects where I have made non-trivial and multi-scrap joins of scraps.<o:p></o:p></p><p class=MsoNormal>My early attempts, prior to my understanding distilled in <a href="https://therion.speleo.sk/wiki/drawingchecklist#wall">https://therion.speleo.sk/wiki/drawingchecklist#wall</a> are characterised by brute strength manual joining of multiple points. Painful.<o:p></o:p></p><p class=MsoNormal>More recent attempts strategically using <span style='font-family:"Abadi Extra Light",sans-serif'>line wall -visibility off </span>and <span style='font-family:"Abadi Extra Light",sans-serif'>line wall -subtype invisible </span><span style='color:black'>have almost always enabled semi-automatic joins (see <a href="https://therion.speleo.sk/wiki/tips#joining_scraps_together">https://therion.speleo.sk/wiki/tips#joining_scraps_together</a> )<o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>However, it seems not to be an exact science, and I have cases where a manual join should be required, but semi-automatic has sufficed. Also cases where I have resorted to a manual join when I though semi-automatic should do it. I’d be really pleased if someone can identify what the rest of the puzzle might be, or suggest improvement to those wiki pages.<o:p></o:p></span></p><p class=MsoNormal><span style='color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:black'>What works best for a particular project will probably depend on whether it is structured such that scraps can easily span multiple surveys or not. My projects are predisposed towards collections of scraps that can only reference one survey with ease. That is probably why I join scraps in the middle of a void more often than some (by often I mean perhaps a dozen times in 60 -80 km and 15 years – usually when part of a large chamber is resurveyed some years later, or when a chamber is highly undulating and it is not possible to see walls, and is surveyed on multiple trips). However don’t think differences in survey scrap relationship structures will change how join methods behave.<o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>Rendering discontinuities should be expected where scrap joins are more complex than ‘straight between two open passage ends’. If these bother you, then opting for some combination of the easiest, simplest, and ‘least morphing required’ will probably give the best result.<o:p></o:p></span></p><p class=MsoNormal><span style='color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:black'>The attached sketch shows how I might arrange multiple scraps in a large void. A simple 1 leg, 2 station survey with a minimal scrap as part of a much larger void and field of scraps. Actual visible walls or pillars in a particular scrap should not be necessary, although I don’t think I’ve done one (with interior shading) without any visible wall at all.<o:p></o:p></span></p><p class=MsoNormal><span style='color:black'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='color:black'>Easiest option:<o:p></o:p></span></b></p><p class=MsoNormal><span style='color:black'>As much sketched cave as possible in one contiguous image in each th2 file. Each scrap (and line and point) join is achieved fully automatically by snapping the points on top of each other. The </span><span style='font-family:"Abadi Extra Light",sans-serif'>-visibility</span><span style='color:black'> and </span><span style='font-family:"Abadi Extra Light",sans-serif'>-subtype</span><span style='color:black'> properties of wall lines are likely to be less relevant to join behaviour, because the morphing induced by the co-incident points dominates.<o:p></o:p></span></p><p class=MsoNormal><b><span style='color:black'>Next option:<o:p></o:p></span></b></p><p class=MsoNormal><span style='color:black'>Non-contiguous sketches or sketches/scraps in different th2 files. Semi-automatic joins required and sufficient here, in most cases. Sometimes manual joins are required across </span><span style='font-family:"Abadi Extra Light",sans-serif'>wall -visibility off</span><span style='color:black'> boundaries.<o:p></o:p></span></p><p class=MsoNormal><b><span style='color:black'>Last resort:<o:p></o:p></span></b></p><p class=MsoNormal><span style='color:black'>Add manual joins only at specific locations where the above fails, or where you want to joint non-wall objects, such as passage feature objects.<o:p></o:p></span></p><p class=MsoNormal><span style='color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:black'>Bruce<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US>From:</span></b><span lang=EN-US> Therion <therion-bounces@speleo.sk> <b>On Behalf Of </b>Bruce Mutton<br><b>Sent:</b> Saturday, 7 December 2024 06:18<br><b>To:</b> 'List for Therion users' <therion@speleo.sk><br><b>Subject:</b> [Therion] Entering survey sketch without walls<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoPlainText>Bill<o:p></o:p></p><p class=MsoPlainText><span style='color:black'>I've been misleading you (and everyone). I should not multi-task quite so much. I will try to rectify the situation tomorrow with a sketch.<o:p></o:p></span></p><p class=MsoPlainText><span style='color:black'><o:p> </o:p></span></p><p class=MsoPlainText><span style='color:black'>In the meantime...<o:p></o:p></span></p><p class=MsoPlainText><span style='font-family:"Abadi Extra Light",sans-serif'>line wall -subtype invisible </span><span style='color:black'>is what should be used for the open ends of scraps in your example, and should allow semiautomatic joins.<o:p></o:p></span></p><p class=MsoPlainText><span style='font-family:"Abadi Extra Light",sans-serif;mso-ligatures:none'>line wall -visibility off</span><span style='mso-ligatures:none'> will preclude the possibility of semiautomatic<span style='color:black'> joins, but does have a use case in large open voids that need to have a scrap join where there are no (real) walls at all. Manual point joins will be required across those boundaries. A sketch tomorrow…<o:p></o:p></span></span></p><p class=MsoPlainText><span style='color:black'><o:p> </o:p></span></p><p class=MsoPlainText><span style='color:black'>Bruce<o:p></o:p></span></p></div></body></html>