<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=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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;}
/* Style Definitions */
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;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@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=MsoPlainText>Tarquin<o:p></o:p></p><p class=MsoPlainText>I don't have a solution to your particular question, but for what it is worth here is my map-connection journey so far.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><img width=153 height=158 style='width:1.5902in;height:1.6458in' id="Picture_x0020_1" src="cid:image003.png@01D893B7.C231EE20"><o:p></o:p></p><p class=MsoPlainText>The default point map-connection lines are all but invisible in large maps, and there is no orientation that shows clearly what is the offset and what is the main map.<o:p></o:p></p><p class=MsoPlainText><img width=259 height=51 style='width:2.7013in;height:.5347in' id="Picture_x0020_2" src="cid:image005.png@01D893B7.C231EE20"><o:p></o:p></p><p class=MsoPlainText>So I modified the l-arrow and l-map-connection metapost. These are clearly visible and have a clear orientation – dot in the main map and arrowhead at the offset position.<o:p></o:p></p><p class=MsoPlainText><img width=377 height=285 style='width:3.9236in;height:2.9652in' id="Picture_x0020_3" src="cid:image008.png@01D893B7.C231EE20"><o:p></o:p></p><p class=MsoPlainText>My convention is to place a map-connection point at every location where a caver could travel from the main map to the offset map. This makes an easy-to-follow map where there are just a few, but not so much when there are many.<o:p></o:p></p><p class=MsoPlainText><img width=318 height=375 style='width:3.3125in;height:3.9027in' id="Picture_x0020_4" src="cid:image011.png@01D893B7.C231EE20"><img width=525 height=501 style='width:5.4722in;height:5.2222in' id="Picture_x0020_5" src="cid:image013.png@01D893B7.C231EE20"><o:p></o:p></p><p class=MsoPlainText>Then I discovered the ICCaving Migovec project that uses a user-defined point u:connection. These are just coloured dots that must be manually placed in each offset map. There are no lines joining the dots. This approach avoids the noise associated with lots of connecting lines and has the advantages of working across various projections and being able to adjust the colour and size on a point-by-point basis. It is not so obvious which is the primary map and which is offset though. My work-in-progress example does not show it at its best.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>I haven’t settled on a favourite approach yet, it probably depends on the particular cave. Both approaches need further development.<o:p></o:p></p><p class=MsoPlainText>I like your suggestion that Therion be able to pass an object id and user defined attribute as it will add to the options available.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Bruce<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><span lang=EN-US>-----Original Message-----<br>From: Therion <therion-bounces@speleo.sk> On Behalf Of Tarquin Wilton-Jones via Therion<br>Sent: Friday, 8 July 2022 05:04<br>To: Therion <therion@speleo.sk><br>Cc: Tarquin Wilton-Jones <tarquin.wilton-jones@ntlworld.com><br>Subject: [Therion] Custom map connections</span></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Hi folks,<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>I have a challenge, presented to me by some users of one of our surveys.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>We have a cave with layers horribly stacked above each other (10 passages all crossing the same point!). Simple solution; use map offsets to put them all side by side. Use map connection arrows to show what connects to what.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>That's all good, but they find the default connection arrow hard to see.<o:p></o:p></p><p class=MsoPlainText>I can redefine l_mapconnection to create my own arrows. Great!<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>But here's the challenge; they want us to show the difference between an unimportant connection, and a major "follow this route" connection. Eg.<o:p></o:p></p><p class=MsoPlainText>minor ones in grey, major route in red.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>I have tried everything I can think of with the mapconnection point: id, scale, rotation, -attr etc., but Therion is not creating a p_mapconnection. it creates a l_mapconnection, and passes it a path to create the line. The attributes are all completely ignored.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Normally, I would use "-attr type major", but that cannot work here, because Therion just ignores it. In my opinion, this is a limitation that should be fixed.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The only solution I can think of, is to put *two* mapconnection points.<o:p></o:p></p><p class=MsoPlainText>The l_mapconnection code can then see if the current path matches the previous path, and if so, draw it in red. But this is such a horrible hack, and prone to failure in future if someone does not realise why there are two points, and why they have to follow on from each other.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Can anyone think of a better workaround?<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Cheers,<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Tarquin<o:p></o:p></p><p class=MsoPlainText>_______________________________________________<o:p></o:p></p><p class=MsoPlainText>Therion mailing list<o:p></o:p></p><p class=MsoPlainText><a href="mailto:Therion@speleo.sk"><span style='color:windowtext;text-decoration:none'>Therion@speleo.sk</span></a><o:p></o:p></p><p class=MsoPlainText><a href="https://mailman.speleo.sk/listinfo/therion"><span style='color:windowtext;text-decoration:none'>https://mailman.speleo.sk/listinfo/therion</span></a><o:p></o:p></p></div></body></html>