<html><HEAD><LINK rel=stylesheet type=text/css href="/webmail/static/deg/css/wysiwyg-3451203449.css" media=all>
<META name=GENERATOR content="MSHTML 8.00.6001.19154"></HEAD>
<BODY>
<DIV>This works - though Olly has depth/count mixed up.</DIV>
<DIV> </DIV>
<DIV>I like "*data station count depth newline compass" ordering as this is the way I record data. I'll incorporate this in my teaching as good way of data entry. Thus:</DIV>
<DIV> </DIV>
<DIV>*data diving station count depth newline compass <BR>0 0 0.0<BR> 067 <BR>1 8.5 -2.6<BR> 069 <BR>2 12.1 -3.8<BR> 068 <BR>3 13 -4.0<BR> 061 <BR>4 15.1 -4.5<BR> 062 <BR>5 16.8 -5.2</DIV>
<DIV>etc.</DIV>
<DIV> </DIV>
<DIV>Thanks.</DIV>
<DIV> </DIV>
<DIV>Oct 19, 2011 11:53:24 PM, <A class=parsedEmail href="mailto:olly@survex.com" target=_blank>olly@survex.com</A> wrote:<BR></DIV>
<BLOCKQUOTE style="BORDER-LEFT: rgb(102,153,204) 3px solid">On Wed, Oct 19, 2011 at 02:54:13PM +0000, Duncan Price wrote:<BR>> Wookey wrote:<BR>> <BR>> "Survex already has 'topofil-style' support with fromcount/tocount so you<BR>> should just be able to enter the length readings as recorded with<BR>> something like<BR>> <BR>> interleaved:<BR>> <BR>> *data diving station depth newline compass count"<BR>> <BR>> this throws up an error:<BR>> <BR>> Reading `count' must occur before NEWLINE<BR><BR>It's right too - you need one counter and depth reading per station, but<BR>one compass reading per leg (perhaps it would be more helpful if the<BR>error message explained it that way), so:<BR><BR>*data diving station depth count newline compass<BR><BR>Which would accept data like this:<BR><BR>1 0.00 0.0<BR>000<BR>2 12.34 -4.0<BR>021<BR>3 17.92 -6.0<BR><BR>Cheers,<BR>Olly<BR></BLOCKQUOTE></BODY></html>