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

fixing bad links

Browse Source
This commit is contained in:
Philip Sargent 2018-08-09 22:09:16 +02:00
parent cb8764004d
commit 38c7636f7f
2 changed files with 52 additions and 37 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

48
handbook/survey/drawup.htm
View File

@ -1,7 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<title>CUCC Expo Surveying Handbook: Drawing Up</title>
<link rel="stylesheet" type="text/css" href="../../css/main2.css" />
</head>
@ -10,12 +8,18 @@
<h2 id="tophead">CUCC Expo Surveying Handbook</h2>
<h1>Drawing up your survey</h1>
<p>The original notes and sketches should be filed in a clearly marked
envelope - don't take them out until you are ready to draw up, and put them
<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>
- 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">
survex format</a> , run
<a href="newcave.html#runsurvex">
aven</a> (the GUI interface to survex) and print out a centre-line plan.
<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
can "invent" details like boulders in boulder-strewn passage, but otherwise,
@ -36,41 +40,25 @@ by the BCRA, with occasional differences - such as large-enough boulders
which are sketched to scale using the US symbol. The current state of
standardisation for cave survey symbols (a useful guide to what we should
be using where possible) has been documented by
<a href="http://www.olsen.ch/~devon/uis/misc/praezis/">H&auml;uselmann,
<a href="http://www.chaos.org.uk/survex/cp/CP14/CPoint14.htm">H&auml;uselmann,
Weidmann and Ruder (1996)</a>, but this is up for discussion in 1997.
An alternative set of standards can be seen from the
Australian Speleological Federation
<a href="http://rubens.its.unimelb.edu.au/~pgm/asf/stdsurv.html">here</a>.</p>
<a href="http://www.caves.org.au/resources/internal-resources/category/29-surveying">here</a>.</p>
<p>Make sure that you draw both plan and elevation (the latter should be an
extended section, rather than a projected elevation) for horizontal passage.
For pitches, several plans at different levels may be easiest (rather like
the cross sections at each survey station used in horizontal passage). Also
projected elevations may be useful in addition to the extended section.</p>
projected elevations may be useful in addition to the extended section. But
learning a good set of procedures for using survex is the way to go.</p>
<p>Write a <b>passage description</b>. 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. It will be
regarded as helpful if you actually type this description into a computer
rather than writing in the log book - but make sure it can be found again! In
written descriptions, underline passage names the first time they are
mentioned, or when they are "defined".</p>
<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 all natural belays recognised.
Ideally, the knots should be left in ropes removed at derigging, so they can
be <b>measured</b> for the rigging guide. Remember to do this before undoing
the knots for rope-washing. 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!</p>
<p>If you did all that properly, there should be very little left to do in
the UK, unless you have volunteered to help with drawing up the final survey.
(Fool!) However, it is as well to check that you have done all you can before
BCRA conference, by reading the <a href="athome.htm">Back in the UK</a> page.</p>
<!-- This looks like a rather hollow joke in the context of the last year's
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.
@ -89,25 +77,23 @@ broke down last summer, so a number of surveys never got drawn up. -->
<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> to
make life easier</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>
<li>Base Camp: drawing it up, writing the description</li>
<li>Base Camp: drawing it up</li>
</ul></li>
<li><a href="../look4.htm">Prospecting guide</a></li>
<li><a href="../rescue.htm">Rescue guide</a></li>
<li><a href="../rigit.htm">Rigging guide</a></li>
<li><a href="../photo.htm">Photography guide</a></li>
</ul></li>
<li><a href="../../infodx.htm">Index to info/topics pages</a></li>
<li><a href="../../indxal.htm">Full Index to area 1623</a>
<ul>
<li><a href="../../areas.htm">Area/subarea descriptions</a></li>
</ul></li>
<li><a href="../../index.htm">Back to Expedition Intro page</a></li>
<li><a href="../../../index.htm">Back to CUCC Home page</a></li>
<li><a href="../../index.htm">Expedition Intro page</a></li>
<li><a href="../../../index.htm">CUCC Home page</a></li>
</ul>
</body>

41
handbook/survey/newcave.html
View File

@ -35,6 +35,7 @@ survey information in your waterproof notebook.
<li>Create a new folder in the file system for the wallet data
<li>Create a new folder in the file system for the survex data
<li>Create a "new cave entry" in the website
<li>Write the <b>full cave description</b> into the correct html files.
<li>Update the index tick boxes on paper: as your wallet progresses through this process
<li>Update the online record of those tick boxes
<li>Regenerate the <a href="/expofiles/surveyscans/2018/">list of outstanding survey tasks</a> for everyone
@ -44,7 +45,7 @@ a waterproof paper notebook. If instead you are using a PDA to record the surve
digitally for your first cave, don't. Use the paper process first, then when you are familair
the overall process, look at the <a href="pdanotes.html">PDA additional notes</a>.
<h3>Starting a new wallet</h3>
<h3 id="newwallet">Starting a new wallet</h3>
<ol>
<li>Put all your written notes into the next empty "wallet":
(a transparent folder/envelope) in this year's lever-arch file labelled
@ -68,7 +69,8 @@ photograph all the pages of survey notes with your phone.
Get one or more of the people also on the trip to do this too.
</ol>
<p>* As people spend longer and longer at top camp, we may establish a wallet file at top camp
<p>* As people spend longer and longer at top camp, we may establish
a wallet file at top camp
too, with pre-allocated numbers.
<p>The original notes and sketches should be filed in the clearly marked
@ -99,7 +101,8 @@ of what information is in the wallet and where the corresponding survey data is
<p>This is where the scanned copies of the survey notes are kept.
<p>If your initial backup photos of your notes were poor quality, use the
scanner in the potato hut to make better copies. Scan to JPEG format as .jpg files.
<p>Name the scanned pages "notes1.jpg", notes2.jpg" etc.
<p>Name the scanned pages "notes1.jpg", notes2.jpg" etc. This is important as a script detects whether these files exist
and if you name them something else it will hassle you unnecessarily.
<p>Scanned survey notes are voluminous and so are not kept in the version control system. Instead it is all kept
in the file bucket "expofiles" on the expo server in Cambridge.
@ -114,7 +117,7 @@ If you want to do this yourself, or are using your own laptop, then learn how to
- as <a href="../uploading.html">documented for uploading your expo photographs</a>. The correct folder
on the expo server is the same as that on the expo laptop- because we set up the expo laptop to be like that.
<h3>Typing in the survey data in survex format</h3>
<h3 id="survexformat">Typing in the survey data in survex format</h3>
<p>[This has been described in several places and we are in the process of consolidating
the documentation and getting rid of out of date notes.]
@ -140,11 +143,11 @@ ensure that it is <em>saved, committed, </em>and<em> pushed</em> appropriately.
<li><a href="/expofiles/presentations/cave_surveying_20130626.pdf">Training course slidepack</a>
</ul>
<h3>Running survex to create a centre-line</h3>
<h3 id="runsurvex">Running survex to create a centre-line</h3>
<p><em>to be documented</em>
<h3>Transcribing and re-scanning your sketches</h3>
<p><em>to be documented</em>
<p><em>to be documented</em> See <a href="survey/drawup.htm">drawing up the sketches</a>.
<h3>Using tunnel for final survey production</h3>
<p><em>to be documented</em>
@ -154,6 +157,32 @@ ensure that it is <em>saved, committed, </em>and<em> pushed</em> appropriately.
<p>Tunnel only produces plan surveys, but they are very pretty.
<h3>The cave description and rigging guide</h3>
<p>Write a <b>passage description</b>. 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
written descriptions, underline passage names the first time they are
mentioned, or when they are "defined".</p>
<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>
One way of getting the rope lengths for your rigging guide is to
leave the knots in ropes removed at derigging so they can
be <b>measured</b>, 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.</p>
<p><em>to be completed</em>
<hr />
<ul id="links">