[Expo-tech] survex *ref and wallets "survex file" fields

Philip Sargent (Gmail) philip.sargent at gmail.com
Sun Apr 5 23:14:37 BST 2020


OK, initial webpage published to help find errors in *ref fields within
survex files, and also mistakes in the online wallet directories when the
wallet refers to the resulting survex file: 
http://expo.survex.com/x-svxvalid.html

A couple of days ago there were only 44 survex files where the *ref (or
;ref, or ;Ref.: or whatever) pointed to a wallet which also correctly
pointed back to the correct survex file. There are now 203 correct pairs.

Some of the errors are very obvious (now) but rather than fix them myself I
thought it better to get these tools out there so people can have better
visibility on what they are doing.

Yes this could all be done more cleanly by programming some more
troggle-generated reports, but these scripts catch errors before importing
files into troggle and not after.

1,004 wallet/svx pairs  (all of which have the correct 20NN#NN format) still
not checking out correctly. Mostly these are formatting problems in my
scripts rather than actual errors - I hope.

More than half the *ref in survex files are not online in our system at all,
e.g.
drawing on orange squared graph paper in AndyW's big yellow ringbinder -
caves-1623/115/cucc/commando.svx
Messbuch SMK 3 - caves-1623/115/nutzlos.svx
caves-1623/161/rhr/tblocks.svx - Can't find this in 1996 survey book (Minoan
Surprise survey is pp 116-117)

and many older survex files have multiple *ref fields:
caves-1623/161/france/adrian.svx AERW doesn't have the 1988 survey book (if
it exists ?)
caves-1623/161/france/adrian.svx 1990 survey book pp 1-2
caves-1623/161/france/adrian.svx 1990 survey book pp 5-7
caves-1623/161/france/adrian.svx 1990 survey book pp 39-42
caves-1623/161/france/adrian.svx 1990 survey book pp 63-65
caves-1623/161/france/adrian.svx 1990 survey book pp 66-68
caves-1623/161/france/adrian.svx 1990 survey book p 66 top right corner

But these are not checkable even in principle so I am ignoring them.

Apologies for the bash/awk coding. It should all be redone in python once I
have finished exploring the scope of the problems.

Philip




More information about the Expo-tech mailing list