[Expo-tech] 2018#X01/2018#99 and svx --th file "link"

[Philip Sargent (Gmail)]

Since contents.json already has fields
"elev not required": false,
"plan not required": false,

it would be an obvious extension to add a
"notes not required": true,
or as you suggest
"notes sheets": 3,

But we do already have this field:
"electronic survey": true,


for TopoDroid surveyed passages.
But fiddling with the JSON  doesn't make it the right thing to do. 

Perhaps the *right* thing to do
would be to make the files in the ::drawings:: repo more like first-class
citizens in troggle?

At the moment we have a sort of semi-detached* link (forgive me if I am
misunderstanding it) between the drawings (therion, tunnel) and the svx
files - only via the surveyscans wallet and then not directly only by
proximity:
the tunnel file links to image files which (a) live in the same directory as
the .json file which references the svx file and
(b) might have a *file_begin link like this:

<pctext style="survey" nodeposxrel="-1.0"
nodeposyrel="-1.0">*file_begin&space;"
C:&backslash;REBECCA&backslash;Tunnel&backslash;CUCCAustria&backslash;loser&
backslash;
caves-1623&backslash;264&backslash;lower_balkon&backslash;
youdontknowyourebeautiful.svx"
&space;""

i.e.
C:\REBECCA\Tunnel\CUCCAustria\loser\caves-1623\264\lower_balkon\youdontknowy
ourebeautiful.svx

though I see that only about 15% mention an svx file like that, and many of
them seem to be local laptop links not useful expofiles links. See attached
file.


ALSO as mentioned already, contents.json only copes with one svx file 

though presumably simple to extend the 
"survex file": "surface/1623/cucc-2018-ms01/MISSING#01.svx", 
field to be, e.g.
"survex file": "[
 surface/1623/cucc-2018-ms01/bedknobs.svx, 
 surface/1623/cucc-2018-ms01/broomsticks.svx
]", 
What are the non-obvious gotchas with doing that ?

The main drawings report in troggle is pretty broken
http://expo.survex.com/tunneldata/ 
and there is no column for tunnel files in the "year report"
http://expo.survex.com/expedition/2014 which would be very useful indeed
when tracking down missing data.

-----Original Message-----
From: Wookey [mailto:wookey at wookware.org] 
Sent: 20 March 2020 12:39
To: Philip Sargent (Gmail)
Subject: Re: 2018#01X

On 2020-03-19 22:22 -0000, Philip Sargent (Gmail) wrote:
> On checking, it is unclear whether you were in favour of having a
different
> naming convention for topo drawings or not.

I'm not sure. It's useful to indicate 'this folder is expected to have
no notes'.

Just to clarify this point - it was primarily about the physical
wallets, not the way we store our data. It makes it obvious thet you
don't need to start scouring the table for the notes someone just left
lying around when they went off for a beer. Which was a very new idea
in 2014.

Now it's more normal we could just add a field to the label that says
something like: "number of notes sheets"?

The reason you still needed a wallet was to put drawn-up sheets in.,
or a printout of the pockettopo drawing. But if a digital survey is
done entirely digitally then it doesn't _need_ a wallet number at all.

So I think we can expect wallets to decline as we get more people like
George who do the entire process on a computer. Instead we get to
think about how the various survey outputs are stored, 'labelled', and
retrieved.

This cave data storage thing is a fascinating problem. :-)

Wookey
--
Principal hats:  Linaro, Debian, Wookware, ARM
http://wookware.org/
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: svx-files-mentioned-in-drawings-files.txt
URL: <http://lists.wookware.org/pipermail/expo-tech/attachments/20200320/adfbd36c/attachment.txt>