<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" 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 11 (filtered medium)">
<style>
<!--
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=blue>
<div class=Section1>
<div>
<div>
<div>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>As below…<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>></span></font>I've always like the
idea of a "series" in bigger caves, i.e. a group of related passages
that help divide the cave into neighbourhoods. <font color=navy><span
style='color:navy'><o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'> Yes,
we do that for larger caves.<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 color=navy face="Times New Roman"><span
style='font-size:12.0pt;color:navy'>></span></font>I pictured it as a bunch
of building blocks (scraps and associated centrelines) that I could put
together hierarchically <font color=navy><span style='color:navy'><o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'> I
think it is.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 color=navy face="Times New Roman"><span
style='font-size:12.0pt;color:navy'>></span></font>and that I could easy
pass parameters from one level to the other or change parameters of one branch
or another. In Walls and On Station it was super easy to change the colour of
centreline for 2D or 3D display in a hierarchical manner, just right click on
the appropriate survey or folder (on Station) or Book (Walls). I used
this a lot to visualize the cave. Eg make all newly surveyed passage pink,
colour code passage by survey date<font color=navy><span style='color:navy'> </span></font><font
size=2 color=navy face=Arial><span style='font-size:10.0pt;font-family:Arial;
color:navy'>[cannot],</span></font> depth<font color=navy><span
style='color:navy'> </span></font><font size=2 color=navy face=Arial><span
style='font-size:10.0pt;font-family:Arial;color:navy'>[can, for maps, not
centreline]</span></font> etc. With my limited understanding of Therion,
I've not yet been able to do this. goes now it is hard to subdivide parameters
of a map. It seems like there should be some commands for this. e.g. if survey
= Arch then colour = blue, if team includes "Rob Countess" then
colour = yellow, if flag = lead then colour = pink, if flag = drafting in then
scrap/map = blue, elseif drafting out then scrap/map = red, elseif oscillating
then scrap = yellow, else if scrap = black. Actually that last one would be a
useful visualization, now I want to do that. It should be easy to set labels to
hide if font <7 pt, <font size=2 color=navy face=Arial><span
style='font-size:10.0pt;font-family:Arial;color:navy'>[can do this but it is a
hack]</span></font><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><font size=3 color=navy face="Times New Roman"><span
style='font-size:12.0pt;color:navy'> </span></font><font
size=2 color=navy face=Arial><span style='font-size:10.0pt;font-family:Arial;
color:navy'>Mostly I would say these are very hard to do with Therion, if not
impossible (but I would very much like some of them). Think of Therion as
‘still in development’. You might need to get into some serious
coding. I get around it in a very limited kind of way by using multiple output
formats at once. ie maps and models in pdf, lox and 3d (survex viewer).<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Therion output is produced by compiling
what is effectively a batch of files, so you have to expect that it won’t
have the immediacy of interactive software.</span></font><font color=navy><span
style='color:navy'><o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 color=navy face="Times New Roman"><span
style='font-size:12.0pt;color:navy'>></span></font>In answer to your
"why not walls": Well i really like some features of Walls. The
blunder detection system is awesome. <font color=navy><span style='color:navy'><o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'> From
your description I can now see why not Walls. However I read about the blunder
detection in Walls once, and was jealous.<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 color=navy face="Times New Roman"><span
style='font-size:12.0pt;color:navy'>></span></font>Plus I like being a
gatekeeper for my projects. You get to stay up to date and to on and to a
degree direct whats going on in your pet projects. When I used On Station
everybody knew how to use it. When I switched to walls only a few people knew
how to use it. <font color=navy><span style='color:navy'><o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'> Ooh!
A control freak. All the great ‘sole owner’ survey projects in NZ
stall eventually (20-30 yr timeframe) because of overload or lack of succession
planning. The main reason I use something like Therion is that it allows
simultaneous drawing by many people. Share the load! If you use
version control, you can keep up with what others have done without necessarily
doing any of the work.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
</div>
</div>
</div>
<div>
<p class=MsoNormal><font size=3 color=navy face="Times New Roman"><span
style='font-size:12.0pt;color:navy'>></span></font>So Therion is, so far,
absolutely the least user friendly cave mapping software around, <font
color=navy><span style='color:navy'><o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'> Probably
true I am afraid, but I am sure that could be solved if we get the right sort
of instructions and examples.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Bruce<o:p></o:p></span></font></p>
</div>
</div>
</body>
</html>