mirror of
https://expo.survex.com/repositories/expoweb/.git/
synced 2024-11-26 17:21:55 +00:00
239 lines
11 KiB
HTML
239 lines
11 KiB
HTML
<!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: Entering data</title>
|
||
<link rel="stylesheet" type="text/css" href="../../css/main2.css" />
|
||
</head>
|
||
<body>
|
||
|
||
<div style="float: left; margin: 10pt">
|
||
<a href="../../piclinks/typing.htm"> <img src="../../tinypix/typing.jpg"
|
||
width="176" height="115" alt="" /></a></div>
|
||
|
||
<h2 style="text-align: center">CUCC Expo Surveying Handbook</h2>
|
||
<h1>Base Camp: from muddy book to Survex plot</h1>
|
||
|
||
<p>The original notes and sketches should be filed in a clearly marked
|
||
envelope - don't take them caving again and don't leave them lying around to
|
||
be "Gössered"!</p>
|
||
|
||
<p>The notes (all of them, including dates, personnel, calibration, LRUD,
|
||
station details, etc.) should be filed away in a numbered wallet in the current
|
||
surveys file. You might have to include a transcription if they are illegible
|
||
(to other people; if you can't read them yourself, go back and do the survey
|
||
again!). Even if you do this, never throw away the original notes.</p>
|
||
|
||
<!-- Original text: ...copied onto a fresh page of the Survey Book
|
||
while everyone's memory is still fresh (this helps if something is only
|
||
marginally legible). This should be proof checked by someone else. Current
|
||
survey books are divided into "Kaninchenhöhle" (usually referred to as
|
||
"KH Survey book") and "surface stuff and other caves" (usually referred to as
|
||
"notKH survey book"). There should be an index page at the front, which you
|
||
should also fill in so that people can find your survey again.</p>-->
|
||
|
||
<p>The data should be typed into whichever computer is being used for the
|
||
survey, again including all the notes, including station details and passage
|
||
names (and make a backup copy to a floppy or another machine). It is
|
||
<b>absolutely essential</b> that you also fill in details of which survey
|
||
folder the notes are in, with index numbers.</p>
|
||
|
||
<p>Survex has its own documentation for the format of the data, though the
|
||
template file and a look at someone else's data will quickly make this
|
||
fairly clear. Survex has some very flexible data entry options, so there
|
||
are a few extra guidelines to try to get some consistency in the way
|
||
everyone uses it within this project.</p>
|
||
|
||
<ul>
|
||
<li>It will be easiest if you start from one of the existing template files,
|
||
as these have lines to remind you to add various details - make sure you
|
||
don't leave any blanks! Copy this to where you want to put your data
|
||
<em>before</em> editing it (with any luck, the template should be on CD-ROM, so
|
||
you can't trash it :-).</li>
|
||
|
||
<!-- I think we can dispense with this now - DL
|
||
<li>Filenames: Because Survex is used on different sorts of computer, it is
|
||
best to use filenames which won't get changed when the files are moved
|
||
between systems. On a PC this means using xxxxxxxx.SVX, where "xxxxxxxx" is a
|
||
name of letters, numbers and maybe the underscore character, with a maximum
|
||
length of eight. On an Acorn machine, the equivalent filename is
|
||
"xxxxxxxx/SVX", and should have a filetype of "Text". Note that this must be
|
||
kept in an image filing system such as SparkFS (.ZIP), X-files or DOSFS
|
||
(which is most logical) to avoid truncation. I know Windows lets you have
|
||
long meaningful names, but these tend to get lost on DOS floppies, or when
|
||
moved to other machines. For directories (=folders), use a maximum of eight
|
||
characters with no extension.-->
|
||
|
||
<li><p>Where to put your data: <b>If in doubt, ASK!</b> If it is a surface
|
||
survey, it goes in the "surface" directory; if it is a file of fixed points
|
||
(like GPS fixes, or map coordinates), it goes in the "fixedpts" directory; if
|
||
it is a new cave on the plateau, put it in a new directory under "caves".
|
||
Underground data for Steinbrückenhöhle goes in one of the
|
||
subdirectories under caves/204; it may well be clear which one from what it
|
||
links to, but if not, ask.</p>
|
||
</li>
|
||
|
||
<li>What to call your survey: all your data should be inside a begin/end pair
|
||
with a meaningful name. This need not be the same name as the file, but as a
|
||
general rule it should be so unless there is a really good reason not to. On
|
||
the other hand, if you have made two or three trips to the same cave,
|
||
it can be a good idea to nest surveys in one file:
|
||
<pre><i>File 2050-01.svx</i>
|
||
*begin 2050-01
|
||
*export pt1.1 pt2.5 [...]
|
||
*begin pt1
|
||
<i>[survey data from first trip]</i>
|
||
*end pt1
|
||
*begin pt2
|
||
<i>[survey data from second trip]</i>
|
||
*end pt2
|
||
*end 2050-01
|
||
</pre>
|
||
|
||
<p>There is no restriction on the length of these names, but as they can be
|
||
displayed in Aven, Tunnel and other such programs, it helps not to have
|
||
anything too elaborate. Older versions of Survex required each prefix to be
|
||
unique in its first eight characters, and this is not a bad guideline to
|
||
follow.</p></li>
|
||
|
||
<li>Every station should have a number <em>within your survey</em> even if it
|
||
is an existing station to which you have connected. Any survey stations which
|
||
you think can reliably be found again should be listed at the start of your
|
||
survey file. This includes the name (within your survey) of any existing points
|
||
you linked into. I have used lines like <tt>;*export mysurvey.pt1.0 ; 2nd bolt at
|
||
head of new pitch</tt> – this may or may not catch on as a standard.</li>
|
||
</ul>
|
||
|
||
<p>At this stage, you have done enough to get a centre line for drawing up.
|
||
If you aren't completely confident about the structure of the Austria data, or
|
||
the Survex syntax of <tt>*equate</tt> and <tt>*export</tt> which can be rather
|
||
cryptic for the uninitiated, it may be best not to try to link your survey to
|
||
everything else so skip the next bit and read on <a href="#concrete">from
|
||
here</a>.</p>
|
||
|
||
<p>However, if you need to see your survey in relation to the rest of the
|
||
dataset:</p>
|
||
|
||
<ul>
|
||
|
||
<li>Don't put any *equate directives to other surveys into your file (or any
|
||
survey legs which quote station names from other survey files). Instead, go to
|
||
the file which *includes the other files in the same area. For example, if you
|
||
have created a file Trivial.svx in the caves/204/deepsouth directory, go to the
|
||
file deepsouth/deepsouth.svx, where you will find *include lines for each of
|
||
the files, together with the *equate lines to connect them together. Add an
|
||
include for your file, and *equate lines for each of your survey stations which
|
||
is the same as one in another survey. If your survey connects to points in
|
||
surveys in files in more than one directory then the *equates should go in the
|
||
204/204.svx file, but at this stage it is probably worth enlisting the help of
|
||
someone who knows the structure of the data inside-out!</li>
|
||
<li>You should now find that if you run Survex on one of the master files
|
||
(all.svx, 204.svx, smk-system.svx, etc.) which includes the area of
|
||
your new survey, it is linked in and will show up when you use the resultant
|
||
.3d file in Aven. Using 204.svx should give info on how long and how
|
||
deep the cave is now.</li>
|
||
<li>Now you need to tell CVS to add your file to the master repository. This is
|
||
very deep magic, and you should probably ask someone to show you how if you are
|
||
not already familiar with CVS.</li>
|
||
</ul>
|
||
|
||
<p><a name="concrete">To make that</a> all a bit more concrete, here is a
|
||
fictitious example of a survey off Swings & Roundabouts in 204. Let's say
|
||
that you went to explore a lead from the QM list numbered 2002-99, that the
|
||
nearest survey station was listed as 204.allswings.swings5.2 and you found it
|
||
successfully, and numbered it within your own survey as station 0. Then you
|
||
might create the following file:</p>
|
||
<!-- Stolen, with apologies to Martin and Lucia, from
|
||
caves/204/swings/ermintrude.svx. -->
|
||
<pre><i>File wibble.svx</i>
|
||
*begin wibble
|
||
|
||
; Locn: Totes Gebirge, Austria - Loser/Augst-Eck Plateau (kataster group 1623)
|
||
; Cave: Steinbruckenh<6E>hle
|
||
*title "Wibbled by Goesser"
|
||
*date 2004.08.32 ;date the survey was done
|
||
*team Insts John Doe
|
||
*team Notes Jane Doe
|
||
*team Tape Jane Doe
|
||
|
||
; ref.: 2004 #999 ; the #number is on the clear pocket containing the original notes.
|
||
|
||
; ====== stations refindable to link to other surveys: ======
|
||
|
||
*export 0 ; list all exported survey points.
|
||
|
||
*calibrate tape 0 ; +ve if tape was too short, -ve if too long
|
||
;calibration data 148,+23,147,+23.5,148,+23,329,-23,328,-23.5,328.5,-23
|
||
|
||
;from to tape compass clino ; remarks
|
||
1 p5 5.48 181 -27
|
||
<i>[and the rest of your survey data]</i>
|
||
6 5 5.66 - DOWN
|
||
|
||
;stn L R U D Desc
|
||
;1 0.7 0.4 0.3 0.5 RP top of boulder
|
||
<i>[and the rest of the station details]</i>
|
||
*end wibble
|
||
</pre>
|
||
|
||
<p>That lot would be typed by copying caves/204/template.svx to
|
||
caves/204/swings/wibble.svx and then filling in the blanks and adding your
|
||
data. If you are linking to the rest of the survey then in the file
|
||
caves/204/swings/allswings.svx add the lines:</p>
|
||
|
||
<pre>
|
||
*include wibble
|
||
*equate wibble.0 swings5.2
|
||
</pre>
|
||
|
||
<p>Remember not to put surface data and underground data in the same file,
|
||
even if they are part of one continuous survey. You need to create two
|
||
files, with a defined station for the entrance, and a suitable equate in
|
||
the file which includes both surface stuff and underground stuff.</p>
|
||
<!-- Did whoever surveyed bogenhoehle read this? -->
|
||
|
||
<p>Once you have your data typed in and checked, it must be run through the
|
||
survey software (which on expo will be <a
|
||
href="http://www.survex.com/">Survex</a>) and a centre line printed, both for
|
||
plan and for extended elevation. Measure the print out to check that it really
|
||
has printed at the scale you wanted (typically 1:500), as this has sometimes
|
||
caused problems in the past.</p>
|
||
|
||
<p>Now see the "<a href="drawup.htm">Drawing it up</a>" page.</p>
|
||
|
||
<hr />
|
||
|
||
<ul id="links">
|
||
<li><b>Expedition Handbook:</b>
|
||
<ul>
|
||
<li>Expo Handbook <a href="../index.htm">Introduction</a></li>
|
||
<li><b>Surveying:</b>
|
||
<ul>
|
||
<li>Surveying <a href="index.htm">Overview</a> and index of
|
||
topics</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> to
|
||
make life easier</li>
|
||
<li>Methods: <a href="ontop.htm">surface</a></li>
|
||
<li>Base Camp: getting it in to the computer</li>
|
||
<li>Base Camp: <a href="drawup.htm">drawing it up</a>, writing
|
||
the description</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>
|
||
</ul>
|
||
</body>
|
||
</html>
|