expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2025-12-08 14:54:28 +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
Download Patch File Download Diff File Expand all files Collapse all files

110
handbook/survey/drawup.htm
View File

@@ -4,21 +4,99 @@
<link rel="stylesheet" type="text/css" href="../../css/main2.css" />
</head>
<body>
<h2 id="tophead">CUCC Expo Surveying Handbook</h2>
<h2 id="tophead">CUCC Expedition Handbook - New Survex file</h2>
<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
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
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
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
<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
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.
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. -->
<hr />
<ul id="links">
<li><b>Survey Handbook:</b>
<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>
<p>Back to the previous page in this sequence <a href="newsurvex.html">Starting a new survex file"</a>.
<br />Now go the the next page in this sequence <a href="newrig.html">Creating a new rigging guide"</a>.
<hr />
</body>
</html>