expoweb/handbook/survey/drawup.htm

<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 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="/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="newsurvex.html">
survex format</a> , run 

<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
can "invent" details like boulders in boulder-strewn passage, but otherwise,
draw only what was recorded faithfully in the cave. If this makes your
drawing look bad - record more next time! If things really are unclear,
consider taking a copy of this drawing back into the cave to clarify it.</p>

<h3>Preparing input into to Tunnel or Therion</h3>
[to be written] - See <a href="newcave.html#therion">
drawing around the centre-line</a> 
<p>The actual published cave-survey is produced by software these days.

<p>Make sure the drawing clearly shows the point of connection to previous
surveys (look at the relevant drawing in the old survey book to ensure the
sketches match and you really have connected where you think). Make sure you
note which Question Mark was addressed by this survey and show the location
of any new question marks, with an estimate of quality and any difficulties
which will be encountered (eg. if it is a climb, are bolts going to be
needed ? If a dig, is it a few loose boulders or a crawl over mud?)</p>

<h3>Archaic: hand-drawing the final survey</h3>

<p>Drawing a cave entirely by hand is not easy but anyone can learn to do it. 
Read the brief <a href="XI-2-11.pdf">Cave Mapping - Sketching the Detail"</a> 
5-page llustrated guide by Ken Grimes which makes everything clear. For preliminary exploration (Grade 1 surveys) this is still appropriate.


<p>CUCC use a set of symbols pretty close to the standard ones promulgated
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.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://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. But 
learning a good set of procedures for using survex is the way to go.</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.
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 />
<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>
[svn r5799] All XHTML 1.0 compliant and rather more up-to-date in content than they once were. 2004-04-22 21:43:17 +01:00			`<html>`
[svn r3779] Added HTML files. 2001-08-15 19:29:27 +01:00			`<head>`
[svn r5799] All XHTML 1.0 compliant and rather more up-to-date in content than they once were. 2004-04-22 21:43:17 +01:00			`<title>CUCC Expo Surveying Handbook: Drawing Up</title>`
[svn r5766] Added CSS stylesheet tags to everything in sight. 2004-04-21 10:35:34 +01:00			`<link rel="stylesheet" type="text/css" href="../../css/main2.css" />`
[svn r3779] Added HTML files. 2001-08-15 19:29:27 +01:00			`</head>`
			`<body>`
Making the survey processing pipeline consistent and documented 2020-03-01 17:46:05 +00:00			`<h2 id="tophead">CUCC Expedition Handbook - New Survex file</h2>`
[svn r5799] All XHTML 1.0 compliant and rather more up-to-date in content than they once were. 2004-04-22 21:43:17 +01:00			`<h1>Drawing up your survey</h1>`
[svn r3779] Added HTML files. 2001-08-15 19:29:27 +01:00
Making the survey processing pipeline consistent and documented 2020-03-01 17:46:05 +00:00			`<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`

fixing bad links 2018-08-09 21:09:16 +01:00			`<p>The original notes and sketches will be filed in a clearly marked`
Making the survey processing pipeline consistent and documented 2020-03-01 17:46:05 +00:00			`wallet - see <a href="/newwallet.html">"Starting a new wallet"</a>`
fixing bad links 2018-08-09 21:09:16 +01:00			`- don't take them out until you are ready to scan them, and put them`
[svn r3779] Added HTML files. 2001-08-15 19:29:27 +01:00			`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`
[svn r5799] All XHTML 1.0 compliant and rather more up-to-date in content than they once were. 2004-04-22 21:43:17 +01:00			`for reference if there is ever a problem.</p>`
[svn r3779] Added HTML files. 2001-08-15 19:29:27 +01:00
Making the survey processing pipeline consistent and documented 2020-03-01 17:46:05 +00:00			`<p>After typing in all the data in <a href="newsurvex.html">`
fixing bad links 2018-08-09 21:09:16 +01:00			`survex format</a> , run`
Making the survey processing pipeline consistent and documented 2020-03-01 17:46:05 +00:00
			`<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>`
fixing bad links 2018-08-09 21:09:16 +01:00
[svn r3779] Added HTML files. 2001-08-15 19:29:27 +01:00			`<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,`
			`draw only what was recorded faithfully in the cave. If this makes your`
[svn r5799] All XHTML 1.0 compliant and rather more up-to-date in content than they once were. 2004-04-22 21:43:17 +01:00			`drawing look bad - record more next time! If things really are unclear,`
			`consider taking a copy of this drawing back into the cave to clarify it.</p>`
[svn r3779] Added HTML files. 2001-08-15 19:29:27 +01:00
plumbing in the QMs page a bit more thoroughly 2020-01-05 18:31:14 +00:00			`<h3>Preparing input into to Tunnel or Therion</h3>`
			`[to be written] - See <a href="newcave.html#therion">`
			`drawing around the centre-line</a>`
			`<p>The actual published cave-survey is produced by software these days.`
Cave sketching guide found 2019-07-17 11:25:03 +01:00
[svn r3779] Added HTML files. 2001-08-15 19:29:27 +01:00			`<p>Make sure the drawing clearly shows the point of connection to previous`
			`surveys (look at the relevant drawing in the old survey book to ensure the`
			`sketches match and you really have connected where you think). Make sure you`
			`note which Question Mark was addressed by this survey and show the location`
			`of any new question marks, with an estimate of quality and any difficulties`
			`which will be encountered (eg. if it is a climb, are bolts going to be`
[svn r5799] All XHTML 1.0 compliant and rather more up-to-date in content than they once were. 2004-04-22 21:43:17 +01:00			`needed ? If a dig, is it a few loose boulders or a crawl over mud?)</p>`
[svn r3779] Added HTML files. 2001-08-15 19:29:27 +01:00
plumbing in the QMs page a bit more thoroughly 2020-01-05 18:31:14 +00:00			`<h3>Archaic: hand-drawing the final survey</h3>`

			`<p>Drawing a cave entirely by hand is not easy but anyone can learn to do it.`
			`Read the brief <a href="XI-2-11.pdf">Cave Mapping - Sketching the Detail"</a>`
			`5-page llustrated guide by Ken Grimes which makes everything clear. For preliminary exploration (Grade 1 surveys) this is still appropriate.`


[svn r3779] Added HTML files. 2001-08-15 19:29:27 +01:00			`<p>CUCC use a set of symbols pretty close to the standard ones promulgated`
			`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`
fixing bad links 2018-08-09 21:09:16 +01:00			`<a href="http://www.chaos.org.uk/survex/cp/CP14/CPoint14.htm">Häuselmann,`
[svn r3779] Added HTML files. 2001-08-15 19:29:27 +01:00			`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`
fixing bad links 2018-08-09 21:09:16 +01:00			`<a href="http://www.caves.org.au/resources/internal-resources/category/29-surveying">here</a>.</p>`
[svn r3779] Added HTML files. 2001-08-15 19:29:27 +01:00
			`<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`
fixing bad links 2018-08-09 21:09:16 +01:00			`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>`
[svn r3779] Added HTML files. 2001-08-15 19:29:27 +01:00

			`<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.`
[svn r5799] All XHTML 1.0 compliant and rather more up-to-date in content than they once were. 2004-04-22 21:43:17 +01:00			`(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>`
fixing bad links 2018-08-09 21:09:16 +01:00
[svn r5799] All XHTML 1.0 compliant and rather more up-to-date in content than they once were. 2004-04-22 21:43:17 +01:00			`<!-- 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.`
			`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 />`
Making the survey processing pipeline consistent and documented 2020-03-01 17:46:05 +00:00			`<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 />`
[svn r3779] Added HTML files. 2001-08-15 19:29:27 +01:00			`</body>`
			`</html>`