expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2024-11-22 07:11:55 +00:00
Code Issues Packages Projects Releases Wiki Activity

Making the survey processing pipeline consistent and documented

Browse Source
This commit is contained in:
Philip Sargent 2020-03-01 17:46:05 +00:00
parent 7bdc1f5435
commit 4cac523ada
9 changed files with 177 additions and 97 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

0
handbook/exposerver.html → handbook/computing/exposerver.html
View File

0
handbook/getsurvex.html → handbook/computing/getsurvex.html
View File

0
handbook/caveentry.html → handbook/survey/caveentry.html
View File

110
handbook/survey/drawup.htm
View File

@ -4,21 +4,99 @@
<link rel="stylesheet" type="text/css" href="../../css/main2.css" /> <link rel="stylesheet" type="text/css" href="../../css/main2.css" />
</head> </head>
<body> <body>
<h2 id="tophead">CUCC Expedition Handbook - New Survex file</h2>
<h2 id="tophead">CUCC Expo Surveying Handbook</h2>
<h1>Drawing up your survey</h1> <h1>Drawing up your survey</h1>
<h2>Great, I have discovered a new cave...</h2>
<p>If you have not come to this page from the sequence starting at <a href="newcave.html">Starting a New Cave"</a> then go and read that first.
<li>This page outlines the next step of the process. Each part of it is documented separately.
<!-- Yes we need some proper context-marking here, breadcrumb trails or something.
Maybe a colour scheme for just this sequence of pages
-->
</ul>
<h2>Process</h2>
<p>
<h3>Drawing up your survey</h3
<p>The original notes and sketches will be filed in a clearly marked <p>The original notes and sketches will be filed in a clearly marked
wallet - see <a href="newcave.html#newwallet">"Creating a new cave"</a> wallet - see <a href="/newwallet.html">"Starting a new wallet"</a>
- don't take them out until you are ready to scan them, and put them - don't take them out until you are ready to scan them, and put them
away again as soon as you have finished. They may never be referred to again, away again as soon as you have finished. They may never be referred to again,
but ultimately they are the most valuable record of your survey and are kept but ultimately they are the most valuable record of your survey and are kept
for reference if there is ever a problem.</p> for reference if there is ever a problem.</p>
<p>After typing in all the data in <a href="newcave.html#survexformat"> <p>After typing in all the data in <a href="newsurvex.html">
survex format</a> , run survex format</a> , run
<a href="newcave.html#runsurvex">
aven</a> (the GUI interface to survex) and print out a centre-line plan. <a href="">aven</a> (the GUI interface to survex) and print out a centre-line plan.
<p>OK if this is your first time doing this, you need to go through the
<a href="usingsurvex.html">"How to use survex" training procedure</a>.
<h3 id="runsurvex">Running survex to create a centre-line</h3>
<p><em>to be documented</em>
<h3 id="rescan">Transcribing and re-scanning your sketches</h3>
<p><em>to be documented</em> See <a href="drawup.htm">drawing up the sketches</a>.
<p>The files of your scanned and re-scanned sketches should be stored in the same folder
as the scanned notes, i.e. (for wallet #19) you would put them in:
<tt>
/home/expo/expofiles/surveyscans/2018/2018#19/
</tt>
<h3 id="therion">Using tunnel or therion for final survey production</h3>
<p><em>to be documented</em>
<ul>
<li><a href="../../documents/tunnel-guide.pdf">How to use Tunnel</a> - PDF - Brendan's guide.
<li><a href="../../documents/tunnel-loefflerCP35-only.pdf">Guide to using Tunnel</a> - PDF - David Loeffler's documentation.
<li><a href="/expofiles/tunnelwiki/wiki/pages/Tunnel.html">Tunnel tutorial</a> - a wiki of examples and tutorials
</ul>
<p>Tunnel only produces plan surveys, but they are very pretty.
<p>The tunnel (or therion) files should NOT stored in the same folder as the scanned notes. They should
be uploaded to the version control repository <span style="font-family:monospace; size=x-small; background-color: lightgray"><a href="http://expo.survex.com/cgit/drawings/.git/log">drawings</a></span>,
<h3>Guidebook description and final rigging guide</h3>
<p>This is the last thing to do - typically after all exploration has been finished for the summer.
The rigging guide sections will have been written into the logbook, and the passage descriptions will
have been written into the survex files, with more lyrical descriptions written into the logbook for each trip.
<p><em>to be documented</em>
<p>Write a <b>passage descriptions</b> by copying and extending the descriptions
given in all the component .svx files.
<p>This should be detailed enough to be
followed by someone in the cave who hasn't been there before, and should
include all passage names, lengths of pitches and climbs, compass directions
when this makes left/right/ahead clearer. If your passage is a connection
it is worth while writing descriptions from both directions.
<p>In
written descriptions, underline passage names the first time they are
mentioned, or when they are "defined".</p>
<p>
You will type this description, and pass it on to someone more nerdy who
will file it in the right place. This will involve "creating a new cave" using the <a href="../computing/troggle-ish.html">troggle</a> system.
<p><em>to be documented</em>
<p>Complementing the passage description in vertical bits is a <b>Rigging
Guide</b>. This is usually easiest to do as a sketch, but include notes to
ensure that all bolts can be found again and any deviations and natural belays recognised.
<p><em>to be completed</em>
<h3>OLD BIT</h3>
<p>Take the printed centre lines and redraw the survey round it, working from <p>Take the printed centre lines and redraw the survey round it, working from
the original sketches as if this was to be the final published survey. You the original sketches as if this was to be the final published survey. You
@ -76,23 +154,9 @@ experience: it's now late April 2004, and the 204 survey is only just
approaching completion. This shows how easy it is for these things to go wrong. approaching completion. This shows how easy it is for these things to go wrong.
The chief problems were a change of software and the fact that the Expo printer The chief problems were a change of software and the fact that the Expo printer
broke down last summer, so a number of surveys never got drawn up. --> broke down last summer, so a number of surveys never got drawn up. -->
<hr /> <hr />
<ul id="links"> <p>Back to the previous page in this sequence <a href="newsurvex.html">Starting a new survex file"</a>.
<li><b>Survey Handbook:</b> <br />Now go the the next page in this sequence <a href="newrig.html">Creating a new rigging guide"</a>.
<hr />
<ul>
<li>Surveying <a href="index.htm">Overview</a></li>
<li><a href="what.htm">What is a cave survey?</a></li>
<li><a href="why.htm">Why am I doing this?</a></li>
<li>Methods: <a href="how.htm">underground</a></li>
<li>Pitfalls to avoid, <a href="hints.htm">hints'n'tips</a></li>
<li>Methods: <a href="ontop.htm">surface</a></li>
<li>Base Camp: <a href="getin.htm">getting it in</a> to the
computer</li>
</ul></li>
</body> </body>
</html> </html>

13
handbook/survey/index.htm
View File

@ -52,22 +52,21 @@ detailed topics.</p>
<li>Methods: <a href="ontop.htm">surface</a> <li>Methods: <a href="ontop.htm">surface</a>
<li>A new cave: <a href="gps.htm">Getting a GPS fix</a></li> <li>A new cave: <a href="gps.htm">Getting a GPS fix</a></li>
<li>Base Camp: <a href="getin.htm">getting it in</a> to the computer</li> <li>Base Camp: <a href="newcave.html.htm">getting it in</a> to the computer</li>
<li><a href="qmentry.html">QMs (Question Marks)</a> in the svx file - possible ways on</li> <li><a href="qmentry.html">QMs (Question Marks)</a> in the svx file - possible ways on</li>
<li><a href="newcave.html#rescan">Transcribing and re-scanning your sketches</a> <li><a href="newcave.html">Transcribing and re-scanning your sketches</a>
<li>Base Camp: <a href="drawup.htm">drawing it up</a>, writing the description</li> <li>Base Camp: <a href="drawup.htm">drawing it up</a>, writing the description</li>
<!-- need to add blurb on QM quality etc. --> <!-- need to add blurb on QM quality etc. -->
<li><a href="athome.htm">Back in the UK</a>: so you thought you'd finished?</li> <li><a href="athome.htm">Back in the UK</a>: so you thought you'd finished?</li>
<li>Current Expo survey <a href="../../survey.html">status</a>.</li> <li>Current Expo survey <a href="../../survey.html">status</a>.</li>
<!-- do we cover the full QM list here ? --> <!-- do we cover the full QM list here ? -->
</ul></li> </ul></li>
<li><a href="http://expo.survex.com/expofiles/presentations/cave_surveying_20130626.pdf">2013 Training Course</a> a slide-pack of a surveying course using Steinbruckhohle as the example</li>
<li><a href="how_to_make_a_survex_file.pdf">How to create a survex file</a></li>
<li><a href="more.htm">More resources</a> on surveying</li> <li><a href="more.htm">More resources</a> on surveying</li>
<li>Older methods: <li>More obscure methods:
<li>GPS for Surveying: <a href="coord.htm">Coordinate Systems</a> and how to convert between them</li> <li>GPS for Surveying: <a href="coord.htm">Austrian Coordinate Systems</a> and how to convert between them</li>
<ul> <ul>
<li>The <a href="lasers.htm">laser fixed points</a></li> <li>The <a href="lasers.htm">Loser plateau laser fixed points</a></li>
</ul></li> </ul></li>
</ul> </ul>

44
handbook/survey/newrig.html Normal file
View File

@ -0,0 +1,44 @@
<html>
<head>
<title>CUCC Expo Surveying Handbook: Drawing Up</title>
<link rel="stylesheet" type="text/css" href="../../css/main2.css" />
</head>
<body>
<h2 id="tophead">CUCC Expedition Handbook - New rigging guide</h2>
<h1>New rigging guide</h1>
<h2>Great, I have discovered a new cave...</h2>
<p>If you have not come to this page from the sequence starting at <a href="newcave.html">Starting a New Cave"</a> then go and read that first.
<li>This page outlines the next step of the process. Each part of it is documented separately.
<!-- Yes we need some proper context-marking here, breadcrumb trails or something.
Maybe a colour scheme for just this sequence of pages
-->
</ul>
<h2>Process</h2>
<p>
<h3>Interim rigging guide</h3>
The logbook is the place where we record the rigging of caves as we discover them.
When a cave is derigged, a good way of getting the rope lengths for your rigging guide is to leave the knots in ropes removed so they can be measured, but these days our caves are a bit deep and complicated for this to be feasible. Although a good survey and details of the belays can be used to estimate the length of rope needed, this is no substitute for measuring how much rope it actually took to rig.
<h3>Final rigging guide</h3>
<p>Complementing the passage description in vertical bits is a <b>Rigging
Guide</b>. This is usually easiest to do as a sketch, but include notes to
ensure that all bolts can be found again and any deviations and natural belays recognised.
<p>
You will already have an "Interim rigging guide" in the logbook entries of the trips, and also sketches on waterproof paper
which were made underground which were stored in the survey wallet and scanned to produce "notes-XXX.jpg" files in the online survey wallet for your trip. For small caves the logbook entry may be all you need.
<p>Collect together your notes for the rigging guide now, including all the pitch lengths. It is a good idea to copy these notes now and put them in the plastic survey wallet or to photograph them and put the files in the online survey wallets. The next step can take some time so get the rigging data in order now.
<p>You will enter the final rigging guide as part of the cave description when you edit the HTML pages for the online cave documentation. This is done using the "New Cave" online form..
<hr />
<p>Back to the previous page in this sequence <a href="drawup.htm">Drawing up your survey"</a>.
<br />Now go the the next page in this sequence <a href="newcaveform.html">Filling in the "New Cave" form</a>.
<hr />
</body>
</html>

92
handbook/survey/newsurvex.html
View File

@ -58,68 +58,42 @@ loser "caves-1623/264/mongolrally.svx". We are assuming that normal users have n
worked with an distributed version control system at this point which is why we are only worked with an distributed version control system at this point which is why we are only
telling them to use the <em>expo laptop</em>.] telling them to use the <em>expo laptop</em>.]
<h3><a id="tickingoff">Ticking off QMs</a></h3> <h3><a id="tickingoff">Entering the QM data</a></h3>
<p>To be written.</p>
<h3 id="runsurvex">Running survex to create a centre-line</h3>
<p><em>to be documented</em>
<h3 id="rescan">Transcribing and re-scanning your sketches</h3>
<p><em>to be documented</em> See <a href="drawup.htm">drawing up the sketches</a>.
<p>The files of your scanned and re-scanned sketches should be stored in the same folder
as the scanned notes, i.e. (for wallet #19) you would put them in:
<tt>
/home/expo/expofiles/surveyscans/2018/2018#19/
</tt>
<h3 id="therion">Using tunnel or therion for final survey production</h3>
<p><em>to be documented</em>
<ul>
<li><a href="../../documents/tunnel-guide.pdf">How to use Tunnel</a> - PDF - Brendan's guide.
<li><a href="../../documents/tunnel-loefflerCP35-only.pdf">Guide to using Tunnel</a> - PDF - David Loeffler's documentation.
<li><a href="/expofiles/tunnelwiki/wiki/pages/Tunnel.html">Tunnel tutorial</a> - a wiki of examples and tutorials
</ul>
<p>Tunnel only produces plan surveys, but they are very pretty.
<p>The tunnel (or therion) files should NOT stored in the same folder as the scanned notes. They should
be uploaded to the version control repository <span style="font-family:monospace; size=x-small; background-color: lightgray"><a href="http://expo.survex.com/cgit/drawings/.git/log">drawings</a></span>,
<h3>Guidebook description and final rigging guide</h3>
<p>This is the last thing to do - typically after all exploration has been finished for the summer.
The rigging guide sections will have been written into the logbook, and the passage descriptions will
have been written into the survex files, with more lyrical descriptions written into the logbook for each trip.
<p><em>to be documented</em>
<p>Write a <b>passage descriptions</b> by copying and extending the descriptions
given in all the component .svx files.
<p>This should be detailed enough to be
followed by someone in the cave who hasn't been there before, and should
include all passage names, lengths of pitches and climbs, compass directions
when this makes left/right/ahead clearer. If your passage is a connection
it is worth while writing descriptions from both directions.
<p>In
written descriptions, underline passage names the first time they are
mentioned, or when they are "defined".</p>
<p> <p>
You will type this description, and pass it on to someone more nerdy who QMs are the unexplored leads, they are Question Marks because we don't
will file it in the right place. This will involve "creating a new cave" using the <a href="../computing/troggle-ish.html">troggle</a> system. know where they go to. There is a specific format for recording them in survex files.
<p><em>to be documented</em> </p>
<p>
Read this <a href="qmentry.html">separate description</a> about
entering the QM data into a survex file.
</p>
<h3><a id="tickingoff">Entering the cave description in the survex file</a></h3>
<p>The last part of the survex file is a description of the passage surveyed. Remember
that this is intended to be read by people
<em>who have not been to that bit of the cave themselves</em>
<code>
;------------<br />
;Cave description ;(leave commented-out)<br />
; See 2017 description for details of GSH up to the 'p50'.
Briefly, on the way to couldashouldawoulda a 22 m entrance crawl from the
surface leads to a climb down and a junction. Left leads to easy c
rawling passage for a short distance, then another junction where
traversing over a shallow hole and down a stooping-height sandy
passage to a sharp left turn and a sandy, easy 'squeeze' leading to a
straighforward p10.
</code>
[from <a href="../../"><em>couldashouldawoulda_to_bathdodgersbypass.svx</em></a>]
</p>
<p>
Note that the description is often written as one long line. Use the word-wrap capability in your editor
to make it easier for yourself.
</p>
<p>Complementing the passage description in vertical bits is a <b>Rigging <hr />
Guide</b>. This is usually easiest to do as a sketch, but include notes to <p>Back to the previous page in this sequence
ensure that all bolts can be found again and any deviations and natural belays recognised. <a href="newwallet.html">Creating a new survey wallet</a>.
<br />Now go the the next page in this sequence <a href="drawup.htm">Drawing up your survey</a>.
<p><em>to be completed</em>

7
handbook/survey/newwallet.html
View File

@ -131,9 +131,12 @@ ensure that it is copied from the <em>expo laptop</em> to the expo server.
<p>If you are not in the potato hut then email all the .topo files <p>If you are not in the potato hut then email all the .topo files
to a friendly nerd (not necessarily on expo) who will upload them in the right place. to a friendly nerd (not necessarily on expo) who will upload them in the right place.
<hr />
<p>Back to the previous page in this sequence
<a href="newcave.html">Creating a new cave in the online system</a>.
<br />Now go the the next page in this sequence <a href="newsurvex.html">Starting a new survex file"</a>.
<p>Now go the the next page in this sequence <a href="newsurvex.html">Starting a new survex file"</a>.
<hr /> <hr />

8
handbook/survey/qmentry.html
View File

@ -7,7 +7,7 @@
</head> </head>
<body> <body>
<h2 id="tophead">CUCC Expedition Handbook - New Cave - QMs</h2> <h2 id="tophead">CUCC Expedition Handbook - New Cave - QMs</h2>
<h1>Adding QMs (Question Marks) and Cave Descriptions</h1> <h1>Adding QMs (Question Marks)</h1>
<h2>QM data and cave descriptions</h2> <h2>QM data and cave descriptions</h2>
@ -83,13 +83,9 @@ drawings correctly with this sort of thing.
<h3>Conclusion</h3> <h3>Conclusion</h3>
<p>Survey data recorded in .svx files is incomplete if there is no QM List data and <p>Survey data recorded in .svx files is incomplete if there is no QM List data and
cave description data! cave description data!
<p>Return to "<a href="newcave.html#survexformat">Survey handbook - survex format</a>".</p> <p>Return to "<a href="newsurvex.html">Survey handbook - survex format</a>".</p>
<hr /> <hr />
<ul id="links">
<li><a href="../index.htm">Expedition Handbook</a>
<li><a href="index.htm">Survey Handbook</a>
</ul>
</body> </body>
</html> </html>