Re: [Therion] Dive data, newline required

2022-07-13 Thread Olly Betts
On Wed, Jul 13, 2022 at 12:04:52PM +0200, Martin Sluka via Therion wrote:
> 
> 
> > 13. 7. 2022 v 11:14, A.M. van Rosmalen :
> > 
> >  data diving station depth length bearing
> 
> There is missing from station to station information:
> From Survey manual:

Martin seems to be quoting the Surve*x* manual here, so while I can't
really speak for what Therion supports here, it seems to follow Survex
here so I guess I should respond about what Survex supports and why.

The problem with the example given is that the supported interleaved
style looks like this (with the first and last being station specific):

  
  
  
  
  
  
  

In the original example given in this thread, "station" and "depth" are
specific to a station, while "length" and "bearing" are measured between
stations, so it would need to be rewritten - this works in Survex format
(therion you probably just need to drop the "*"):

*data diving station depth newline length bearing
GTENC000136.3
0.45257.6
GTENC000236.2
0.26248.6
GTENC000336.2
; commented out because incomplete: 0.52233.3

Note the final length and bearing can't be processed without a
corresponding final station and its depth to make a complete set of
data for the final leg.

As to why the newline is required, the supported style was based on
examples I'd seen of this style, and note taking in this style seems to
naturally lead people to grouping the readings like this, e.g. from a
random web search result:

https://southerncaliforniagrotto.com/graphics/resmap2.jpg

I don't think it's ever come up before that someone wanted interleaved
data but with the station and inter-station data all on a single line.
It could probably be supported (though I think it would need to be
limited to still requiring all inter-station readings after the station
specific ones because the final line has only station specific
readings), but you said your data is computer generated so tweaking the
code which generates the data to write a newline after the depth would
get you there much quicker.

Cheers,
Olly
___
Therion mailing list
Therion@speleo.sk
https://mailman.speleo.sk/listinfo/therion


Re: [Therion] Dive data, newline required

2022-07-13 Thread Martin Sluka via Therion


> 13. 7. 2022 v 11:14, A.M. van Rosmalen :
> 
>  data diving station depth length bearing

There is missing from station to station information:
From Survey manual:

 DIVING
An underwater survey where the vertical information is from a diver’s depth 
gauge. This style
can also be also used for an above-water survey where the altitude is measured 
with an
altimeter. DEPTH is defined as the altitude (Z) so increases upwards by 
default. So for a
diver’s depth gauge, you’ll need to use *CALIBRATE with a negative scale factor 
(e.g.
*calibrate depth 0 -1).
 For non-interleaved data the allowed readings are: FROM TO TAPE COMPASS CLINO
BACKCOMPASS BACKCLINO FROMDEPTH TODEPTH DEPTHCHANGE (the vertical
can be given as readings at each station, (FROMDEPTH/TODEPTH) or as a change 
along the
leg (DEPTHCHANGE)).
Survex 1.2.20 and later allow an optional CLINO and/or BACKCLINO reading in 
DIVING
style. At present these extra readings are checked for syntactic validity, but 
are otherwise
ignored. The intention is that a future version will check them against the 
other readings to flag
up likely blunders, and average with the slope data from the depth gauge and 
tape reading.
For interleaved data the allowed readings are: STATION DIRECTION TAPE COMPASS
BACKCOMPASS DEPTH DEPTHCHANGE. (the vertical change can be given as a reading at
the station (DEPTH) or as a change along the leg (DEPTHCHANGE)).
*data diving from to tape compass fromdepth todepth
1 2 14.7 250 -20.7 -22.4
*data diving station depth newline tape compass
1 -20.7
14.7 250
2 -22.4
*data diving from to tape compass depthchange
1 2 14.7 250 -1.7

M.


___
Therion mailing list
Therion@speleo.sk
https://mailman.speleo.sk/listinfo/therion


Re: [Therion] Dive data, newline required

2022-07-13 Thread Torsten Schnitter
Hi Anton

I'm using following format for diving surveys and don't get this 
"non-interleaved" message.
 
data diving from to length compass backcompass fromdepth todepth left right up 
down
1   2   5.37   308   -   0.0   1.5 [ 1.0 1.0] [ 1.0 1.0] [ 1.0 1.0] [ 1.0 1.0]

I'm using LRUD like above with data at from-station and to-station.
For me it gives a better looking xvi file with side messurements.
 
cheers,
Torsten

> A.M. van Rosmalen  hat am 13.07.2022 11:14 CEST 
> geschrieben:
>  
>  
>  
> Dear Therionners,
> 
> This is a sample of my centerline data:
> 
>  data diving station depth length bearing
> 
> GTENC000136.30.45257.6
> GTENC000236.20.26248.6
> GTENC000336.20.52233.3
> 
> Simple and straightforward as this may seem, Therion just spits it
> back into my face saying:
> 
> -- non-interleaved data before newline -- length
> 
> 
> 
> The following works (this is the format I use when processing a
> limited amount of survey data), but obviously this sucks balls when
> processing large amounts of data (I have 1000 lines of computer
> generated survey data in this centerline)
> 
> data diving station depth left right up down ignore newline \
> length bearing ignoreall
> 
> GdB09  30.0  -   -   2.7 0  [T, White arrow #4]
>10204
> GdB08  30.6  3   0   2   0.5 [T, White arrow #3]
>17265
> 
> It seems I'm too stupid to understand why there needs to be a newline
> before length.
> 
> Can anyone tell me what I'm not understanding / what I'm doing wrong /
> how to work around this apparently useless newline requirement?
> 
> Cheers,
> 
> Anton
> ___
> Therion mailing list
> Therion@speleo.sk
> https://mailman.speleo.sk/listinfo/therion
> 
___
Therion mailing list
Therion@speleo.sk
https://mailman.speleo.sk/listinfo/therion


[Therion] Dive data, newline required

2022-07-13 Thread A.M. van Rosmalen
Dear Therionners,

This is a sample of my centerline data:

 data diving station depth length bearing

GTENC000136.30.45257.6
GTENC000236.20.26248.6
GTENC000336.20.52233.3

Simple and straightforward as this may seem, Therion just spits it
back into my face saying:

-- non-interleaved data before newline -- length



The following works (this is the format I use when processing a
limited amount of survey data), but obviously this sucks balls when
processing large amounts of data (I have 1000 lines of computer
generated survey data in this centerline)

data diving station depth left right up down ignore newline \
length bearing ignoreall

GdB09  30.0  -   -   2.7 0  [T, White arrow #4]
   10204
GdB08  30.6  3   0   2   0.5 [T, White arrow #3]
   17265

It seems I'm too stupid to understand why there needs to be a newline
before length.

Can anyone tell me what I'm not understanding / what I'm doing wrong /
how to work around this apparently useless newline requirement?

Cheers,

Anton
___
Therion mailing list
Therion@speleo.sk
https://mailman.speleo.sk/listinfo/therion