Hello Thanks a lot for your answers. It solved my problem. If I have a zero length leg at the beginning of each centerline, this is because i am importing all the data from visual topo files, and in vtopo, the first line is always a zero length leg to get the LRUD of the fist point. The strange thing is that I have that for normal and topofil data, and it is working very well. I do not understand why it create a metapost error when we use diving data. And last thing about diving data : when we do a survey in a sump, we have 2 ways to do it : 1) we use a tape, so the length is given between each station. 2) We use a line that is marked every 2 to 5 m, and the length that we read at each station is the length from the beginning of the sump/underwater survey. In that case, it works as a topofil/counter. However, it is not allowed in diving data declaration. It could be interesting to allow it this kind of data. Cheers, Xavier Le 19 oct. 2011 à 10:51, Andrew Atkinson a écrit :

Hello

So station 1_25 is the same as 4_1 and you have connected them together with a zero length leg. Not sure why this does not work, but if you replace

1_25 4_1 0.0 0.0 0.0 0.0 0.0 0.0 0.0

with

equate 1_25 4_1

it gets rid of the stream of errors, I also find equates easier to read than zero length legs, especially as you have a cross section of 0 which seems unlikely.

Andrew

On 19/10/11 09:13, Xavier Robert wrote:

...

Hi all,

I am currently trying to draw a map with diving data. But she I compile, I receive a metapost error. This probably because of the structure of my data, but even after reading The THbook and the Survex tutorial, I do not understand where/why. Can someone give me any advise ?

I attach to this emai a zip file that contain : - a simple part of my diving data, with its thconfig file - The associated log file.

Thanks a lot !

Xav

-- Xavier Robert Chercheur/Researcher CR2 - IRD ISTerre - Maison des Géosciences 1381 rue de la Piscine - BP 53 38041 Grenoble Cedex 09 France

Phone : Fax : 33 (0)4 76 51 40 58

xavier.robert01@gmail.com <mailto:xavier.robert01@gmail.com>

_______________________________________________ Therion mailing list Therion@speleo.sk http://mailman.speleo.sk/mailman/listinfo/therion

---

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

+++ Duncan Price [2011-10-19 10:48 +0000]:

My way of working is to record the cumulative distance, depth and forward bearing at every station either by using a tagged line or tape measure laid alongside the line. These data are then entered into a spreadsheet and used to claculate the distance between stations.

But the whole point of the fairly flexible survex 'enter it like it is in the book' format/philosophy is to save you that sort of faff and avoid the conseqent errors. Survex already has 'topofil-style' support with fromcount/tocount so you should just be able to enter the length readings as recorded with something like interleaved: *data diving station depth newline compass count or for non-interleaved: * data diving from fromdepth fromcount to todepth tocount compass Have you tried that and found problems (in either survex or therion)? Wookey -- Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM http://wookware.org/

+++ Xavier Robert [2011-10-19 14:10 +0200]:

Le 19 oct. 2011 13:17, Wookey a crit :

or for non-interleaved:

* data diving from fromdepth fromcount to todepth tocount compass

Have you tried that and found problems (in either survex or therion)?

Yes, I tried that with therion, and therion answer me that from count/tocount is not compatible with the declaration 'data diving'. That is why I made this remark !

OK. Check it works in survex. If it does we have an annoying incompatibility. I know therion can hand off the solving to survex, but I'm not sure if it always does its own data-parsing. I assume so, so there are likely to be minor differrences between the different parsers. That can no doubt be fixed. Wookey -- Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM http://wookware.org/

I will check this, there is no reason for incompatibility. Thanks, S. On 19 October 2011 14:10, Xavier Robert <xavier.robert01@gmail.com> wrote:

Hi, Yes, I tried that with therion, and therion answer me that from count/tocount is not compatible with the declaration 'data diving'. That is why I made this remark ! Xav Le 19 oct. 2011 à 13:17, Wookey a écrit :

or for non-interleaved:

* data diving from fromdepth fromcount to todepth tocount compass

Have you tried that and found problems (in either survex or therion)?

_______________________________________________ Therion mailing list Therion@speleo.sk http://mailman.speleo.sk/mailman/listinfo/therion

On Wed, Oct 19, 2011 at 02:54:13PM +0000, Duncan Price wrote:

Wookey wrote:

"Survex already has 'topofil-style' support with fromcount/tocount so you should just be able to enter the length readings as recorded with something like

interleaved:

*data diving station depth newline compass count"

this throws up an error:

Reading `count' must occur before NEWLINE

It's right too - you need one counter and depth reading per station, but one compass reading per leg (perhaps it would be more helpful if the error message explained it that way), so: *data diving station depth count newline compass Which would accept data like this: 1 0.00 0.0 000 2 12.34 -4.0 021 3 17.92 -6.0 Cheers, Olly