<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.23588"></HEAD>
<BODY>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=671242920-19092014>We have been using multiple coordinate systems for a
number of years, and it seems to work perfectly.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=671242920-19092014>We mix and match at will between lat-long, NZMG and
NZTM (ie old and new datums) within the same cave survey and between cave
surveys.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=671242920-19092014>So, Footleg, unless you have other reasons to do so,
there is no need to convert your old datum coords to new datum
coords.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=671242920-19092014></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=671242920-19092014>There seem to be a couple of rules to keep things
working smoothly. Have a look at Therion Book pg 14 and 46-47 and
k</SPAN></FONT><FONT color=#0000ff size=2 face=Arial><SPAN
class=671242920-19092014>eep in mind the distinction between input and
output. </SPAN></FONT></DIV><SPAN class=671242920-19092014>
<OL dir=ltr>
<LI>
<DIV align=left><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=671242920-19092014>E</SPAN>ach centerline with fix statement(s) should
have a date and cs specification (prior to the fix I
think).</FONT></FONT></FONT></DIV>
<LI>
<DIV align=left><FONT color=#0000ff size=2 face=Arial>So that you can be sure
of the cs applied to the outputs, specify the output cs that you want in the
th-config (not in a layout).</FONT></DIV>
<LI>
<DIV align=left></SPAN><SPAN class=671242920-19092014><FONT color=#0000ff
size=2 face=Arial>I have avoided using cs in layout, as, even if Therion is
consistent in the way it applies it, in the situation where there are multiple
coordinate systems in use, it is not abundantly clear to a user which cs will
be used, for example where some centrelines have no explicit cs or for
the output. (Although reading Therion Book pg 47, maybe that is for
Atlas outputs - been a while, I forget).</FONT></SPAN></DIV></LI></OL>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=671242920-19092014>Now that we have output variables in 5.3.15 that echo
the cs that has been used for output, it will be possible to have this stamped
in the pdf header. I have a 'proof that it works' layout drafted up,
and one day I will make a modular set of layouts to make it readily
useable</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=671242920-19092014></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=671242920-19092014>The first file embedded on this page <A
href="http://therion.speleo.sk/wiki/doku.php/templates">http://therion.speleo.sk/wiki/doku.php/templates</A></SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=671242920-19092014>(ie </SPAN></FONT><FONT color=#0000ff size=2
face=Arial><SPAN class=671242920-19092014><A
href="http://therion.speleo.sk/wiki/lib/exe/fetch.php/templates:thconfig-templatesimple.txt">http://therion.speleo.sk/wiki/lib/exe/fetch.php/templates:thconfig-templatesimple.txt</A>)</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=671242920-19092014>shows how I use it in a th-config
file.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=671242920-19092014></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=671242920-19092014>Bruce</SPAN></FONT></DIV><FONT color=#0000ff size=2
face=Arial></FONT><BR>
<DIV dir=ltr lang=en-us class=OutlookMessageHeader align=left>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>From:</B> therion-bounces@speleo.sk
[mailto:therion-bounces@speleo.sk] <B>On Behalf Of </B>Footleg<BR><B>Sent:</B>
Saturday, 20 September 2014 4:13 a.m.<BR><B>To:</B> List for Therion
users<BR><B>Subject:</B> Re: [Therion] Combining caves using different
co-ordinate systems<BR></FONT><BR></DIV>
<DIV></DIV>
<P dir=ltr>I had put one cave using a cs and gps fix coordinates into one survey
block in a .th file. Then a second cave using a different cs and gps fix
coordinates in a second .th file.</P>
<P dir=ltr>My project then uses a <A href="http://master.th">master.th</A> file
which inputs both of these. If I run my config on either of the individual files
then they appear at the correct place on Google Earth from an output kml file.
If I include both caves then they appear in different places. The one I include
first is in the correct place. If I swap the order they appear in the <A
href="http://master.th">master.th</A> file then this confirms the first one is
alway put in the correct place, and the second is positioned using the cs of the
first one.</P>
<P dir=ltr>The same in a lox model file (except I cannot confirm which is
correct, but I see them in different places when I give them the same entrance
location to test this).</P>
<P dir=ltr>Footleg</P>
<DIV class=gmail_quote>On 19 Sep 2014 14:33, "Andrew Atkinson" <<A
href="mailto:andrew@wotcc.org.uk">andrew@wotcc.org.uk</A>> wrote:<BR
type="attribution">
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>
<P dir=ltr>You can use cs in config file, either inside layout, or outside
layout (most likely what you want to do) to control the output co-ordinate
system, which I think is what you are trying to do?</P>
<P dir=ltr>Andrew</P>
<DIV class=gmail_quote>On 19 Sep 2014 14:00, "Footleg" <<A
href="mailto:drfootleg@gmail.com" target=_blank>drfootleg@gmail.com</A>>
wrote:<BR type="attribution">
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>I have been converting a project from an old datum to a
more recent<BR>one following the issuing of new maps using the newer datum.
So all my<BR>entrance GPS coordinates changed. I updated the cs statements
in my<BR>survey data files and my KML output is still in the correct place.
So<BR>all was looking good. Then I discovered that if I include a survey
in<BR>the old cs with one using the new cs then Therion appears to
treat<BR>both caves as having the same cs. Whichever cs is used by the
first<BR>included cave is applied to subsequent caves too. Is there a way
to<BR>deal with
this?<BR><BR>Footleg<BR>_______________________________________________<BR>Therion
mailing list<BR><A href="mailto:Therion@speleo.sk"
target=_blank>Therion@speleo.sk</A><BR><A
href="http://mailman.speleo.sk/mailman/listinfo/therion"
target=_blank>http://mailman.speleo.sk/mailman/listinfo/therion</A><BR></BLOCKQUOTE></DIV><BR>_______________________________________________<BR>Therion
mailing list<BR><A href="mailto:Therion@speleo.sk">Therion@speleo.sk</A><BR><A
href="http://mailman.speleo.sk/mailman/listinfo/therion"
target=_blank>http://mailman.speleo.sk/mailman/listinfo/therion</A><BR><BR></BLOCKQUOTE></DIV></BODY></HTML>