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

fixing bad link and extra bit

Browse Source
This commit is contained in:
Philip Sargent
2018-08-11 21:22:17 +02:00
parent c3e2817d8e
commit f37c2d8c02
1 changed files with 22 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

29
handbook/survey/newcave.html
View File

@@ -12,7 +12,7 @@
and you want to let the world know of your massive discovery.
<ul>
<li>If you have not yet learned how to record your prospecting and survey
your leads, read the <a href="look4.htm">prospecting introduction</a> and
your leads, read the <a href="../look4.htm">prospecting introduction</a> and
<a href="../survey/index.htm">survey handbook</a> which tells you how to record
survey information in your waterproof notebook.
<li>This page outlines the rest of the process. Each part of it is documented separately.
@@ -44,7 +44,7 @@ survey information in your waterproof notebook.
</ul>
<p>This documentation assumes that you have recorded your survey data in
a waterproof paper notebook. If instead you are using a PDA to record the survey readings
digitally for your first cave, don't. Use the paper process first, then when you are familair
digitally for your first cave, don't. Use the paper process first, then when you are familiar
the overall process, look at the <a href="pdanotes.html">PDA additional notes</a>.
<h3 id="newwallet">Starting a new wallet</h3>
@@ -168,9 +168,14 @@ ensure that it is <em>saved, committed, </em>and<em> pushed</em> appropriately.
<h3>Transcribing and re-scanning your sketches</h3>
<p><em>to be documented</em> See <a href="survey/drawup.htm">drawing up the sketches</a>.
<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:
<pre>
/home/expo/expofiles/surveyscans/2018/2018#19/
</pre>
<h3>Using tunnel for final survey production</h3>
<h3>Using tunnel (or therion) for final survey production</h3>
<p><em>to be documented</em>
<ul>
<li><a href="/expofiles/tunnelwiki/wiki/pages/Tunnel.html">Tunnel tutorial</a> - a wiki of examples and tutorials
@@ -178,18 +183,28 @@ ensure that it is <em>saved, committed, </em>and<em> pushed</em> appropriately.
<p>Tunnel only produces plan surveys, but they are very pretty.
<p>The tunnel (or therion) files should be stored in the same folder as the scanned notes.
<h3>The cave description and rigging guide</h3>
<p>Write a <b>passage description</b>. This should be detailed enough to be
<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.
You will type this description, and pass it on to someone more nerdy who
will file it in the right place. In
<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 troggle 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.