expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2026-02-20 03:05:19 +00:00
Code Issues Packages Projects Releases Wiki Activity

[svn r5798] Heavily modified, in accordance with current practice, using examples from 204. This is inevitably going to be volatile information.

Browse Source
This commit is contained in:
dl267
2004-04-22 22:11:29 +02:00
parent 5fdd475073
commit 2bea567832
1 changed files with 157 additions and 205 deletions
Download Patch File Download Diff File Expand all files Collapse all files

360
handbook/survey/getin.htm
View File

@@ -1,50 +1,57 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0//EN"> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html lang="en"> <html>
<head> <head>
<title>CUCC Austria Cave Surveying Guide</title> <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" /> <link rel="stylesheet" type="text/css" href="../../css/main2.css" />
</head> </head>
<body> <body>
<h2 align=center>CUCC Expedition Handbook: Surveying<br> <div style="float: left; margin: 10pt">
<a href="../../piclinks/typing.htm"> <img src="../../tinypix/typing.jpg"
width="176" height="115" alt="" /></a></div>
Base Camp: from muddy book to Survex plot</h2> <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 <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 envelope - don't take them caving again and don't leave them lying around to
be "G&ouml;ssered" ! be "G&ouml;ssered"!</p>
<p>The notes (all of them, including dates, personnel, calibration, LRUD, <p>The notes (all of them, including dates, personnel, calibration, LRUD,
station details, etc.) should be copied onto a fresh page of the Survey Book 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 while everyone's memory is still fresh (this helps if something is only
marginally legible). This should be proof checked by someone else. Current marginally legible). This should be proof checked by someone else. Current
survey books are divided into "Kaninchenh&ouml;hle" (usually referred to as survey books are divided into "Kaninchenh&ouml;hle" (usually referred to as
"KH Survey book") and "surface stuff and other caves" (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 "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. 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 <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 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 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 <b>absolutely essential</b> that you also fill in details of which survey
book the notes are in, with page numbers. folder the notes are in, with index numbers.</p>
<p><center><a href="../../piclinks/typing.htm">
<img src="../../tinypix/typing.jpg" width=176 height=115></a></center>
<p>Survex has its own documentation for the format of the data, though the <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 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 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 are a few extra guidelines to try to get some consistency in the way
everyone uses it within this project. everyone uses it within this project.</p>
<ul> <ul>
<li>It will be easiest if you start from one of the existing template files, <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 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 don't leave any blanks! Copy this to where you want to put your data
<u>before</u> editing it (with any luck, the template should be on CD-ROM, so <em>before</em> editing it (with any luck, the template should be on CD-ROM, so
you can't trash it :-). 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 <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 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 between systems. On a PC this means using xxxxxxxx.SVX, where "xxxxxxxx" is a
@@ -55,236 +62,181 @@ 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 (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 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 moved to other machines. For directories (=folders), use a maximum of eight
characters with no extension. characters with no extension.-->
<li>Where to put your data: <b>If in doubt, ASK !</b> If it is a surface <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 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 (like GPS fixes, or map coordinates), it goes in the "fixedpts" directory; if
it is a new or minor cave on the plateau, it goes in "Plateau", if it is on it is a new cave on the plateau, put it in a new directory under "caves".
the Vorderer Schwarzmooskogel above the Stellerweg system, or it is somewhere Underground data for Steinbr&uuml;ckenh&ouml;hle goes in one of the
near 161 (but not connected to it), it goes in "VSKcaves". If it is downhill subdirectories under caves/204; it may well be clear which one from what it
from Stellerweg (near the Stogerweg path), it goes in "Stoger". If it is links to, but if not, ask.</p>
underground survey which connects to the Stellerweg system, then it goes in
"41.CUCC". There is a "41.Arge" folder for data we get from the Germans doing
resurvey and new stuff in this cave, and a "78" folder which is for their
Schwabenschacht stuff. "182" is for Puffball, and "161" is for the great mass
of Kaninchenh&ouml;hle data.
<p>The KH data is split into areas in directories "136" (all of 136 and the
Forbidden Land), "Chile" (everything from the start of 1999), "France" (all
the vertical France stuff, and flat France up to approx French Revolution),
"LHR" (all the left hand routes, and Ambidextrous), "North" (everything from
Carrefour north, including Siberia), "PHumour" (all Puerile Humour, Iceland
etc.), "RHR" (all the right hand routes, and through Knossos to Carrefour),
"Top" (just stuff near 161a entrance) and "Triassic" (Triassic Park and all
its side leads except Puerile Humour). If you really aren't sure where your
data should go, there is nothing to stop you using a "New" directory.
<p>There is a <a href="svindx.htm">complete index</a> to all the existing <p>There is a <a href="svindx.htm">complete index</a> to all the existing
surveys, which should enable you to find the data for any survey station, surveys, which should enable you to find the data for any survey station,
once you know its name. It's a fair bet that if your survey connects to a once you know its name. It's a fair bet that if your survey connects to a
station in one directory, your survey data should go in that same directory. station in one directory, your survey data should go in that same directory.</p></li>
<li>What to call your survey: all your data should be inside a begin/end <li>What to call your survey: all your data should be inside a begin/end pair
pair with a meaningful name. There is nothing to stop you nesting these, with a meaningful name. This need not be the same name as the file, but as a
so you might use the name "mysurvey" and put two lots of data from different general rule it should be so unless there is a really good reason not to. On
trips in as "mysurvey.pt1" and "mysurvey.pt2". There is no restriction on the other hand, if you have made two or three trips to the same cave,
the length of these names, but as they can be displayed in Caverot, it helps it can be a good idea to nest surveys in one file:
not to have anything too elaborate. Older versions of Survex required each <pre><i>File 2050-01.svx</i>
prefix to be unique in its first eight characters, and this is not a bad *begin 2050-01
guideline to follow. These names are <b>not the same as the filename</b> *export pt1.1 pt2.5 [...]
you used, since one file may contain a number of related surveys. *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>
<li>Every station should have a number <u>within your survey</u> even if it <p>There is no restriction on the length of these names, but as they can be
is an existing station to which you have connected. Any survey stations displayed in Aven, Tunnel and other such programs, it helps not to have
which you think can reliably be found again should be listed at the start of anything too elaborate. Older versions of Survex required each prefix to be
your survey file. This includes the name (within your survey) of any unique in its first eight characters, and this is not a bad guideline to
existing points you linked into. I have used lines like<br> follow.</p></li>
;*export mysurvey.pt1.0 ; 2nd bolt at head of new pitch<br>
this may or may not catch on as a standard.
<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> &ndash; this may or may not catch on as a standard.</li>
</ul> </ul>
<p>At this stage, you have done enough to get a centre line for drawing up. <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 If you aren't completely confident about the structure of the Austria data, or
data, it may be best not to try to link your survey to everything else the Survex syntax of <tt>*equate</tt> and <tt>*export</tt> which can be rather
so skip the next bit and read on <a href="#concrete">from here</a>. 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 <p>However, if you need to see your survey in relation to the rest of the
cave: dataset:</p>
<ul> <ul>
<li>Don't put any *equate directives to other surveys into your file (or <li>Don't put any *equate directives to other surveys into your file (or any
any survey legs which quote station names from other survey files). survey legs which quote station names from other survey files). Instead, go to
Instead, go to the file which *includes the other files in the same area. the file which *includes the other files in the same area. For example, if you
For example, if you have created a file Trivial.svx in the PHumour have created a file Trivial.svx in the caves/204/deepsouth directory, go to the
directory, go to the file AllPH/svx, where you will find *include lines file deepsouth/deepsouth.svx, where you will find *include lines for each of
for each of the files, together with the *equate lines to connect them the files, together with the *equate lines to connect them together. Add an
together. Add an include for your file, and *equate lines for each of include for your file, and *equate lines for each of your survey stations which
your survey stations which is the same as one in another survey. If is the same as one in another survey. If your survey connects to points in
your survey connects to points in surveys in files in more than one surveys in files in more than one directory then the *equates should go in the
directory then the *equates should go in the All161/svx file, but at 204/204.svx file, but at this stage it is probably worth enlisting the help of
this stage it is probably worth enlisting the help of someone who knows someone who knows the structure of the data inside-out!</li>
the structure of the data inside-out !
<li>Make a note in the history file of the changes you made to the
controlling file (in this case AllPH/svx), and the fact that you added
a new file.
<li>You should now find that if you run Survex on one of the master files <li>You should now find that if you run Survex on one of the master files
(Just161.svx, JustSurf.svx, AllCaves.svx, etc.) which includes the area of (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 your new survey, it is linked in and will show up when you use the resultant
.3d file in CaveRot. Using Just161.svx should give info on how long and how .3d file in Aven. Using 204.svx should give info on how long and how
deep the cave is now. 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> </ul>
<p><a name="concrete">To make that</a> all a bit more concrete, here is a <p><a name="concrete">To make that</a> all a bit more concrete, here is a
fictitious example of a survey off Triassic Park. Lets say that you went to fictitious example of a survey off Swings &amp; Roundabouts in 204. Let's say
explore a lead from the QM list numbered 98-23, that the nearest survey that you went to explore a lead from the QM list numbered 2002-99, that the
station was listed as Triassic.pt2.45 and you found it successfully. You nearest survey station was listed as 204.allswings.swings5.2 and you found it
surveyed back from a bolt at the end of your new passage where exploration successfully, and numbered it within your own survey as station 0. Then you
has stopped for the time being, and it took 37 survey legs to get back to might create the following file:</p>
Triassic Park: <!-- Stolen, with apologies to Martin and Lucia, from
caves/204/swings/ermintrude.svx. -->
<pre><i>File wibble.svx</i>
*begin wibble
<pre> ; Locn: Totes Gebirge, Austria - Loser/Augst-Eck Plateau (kataster group 1623)
; &gt; Triassic.Wibble : Wibbled by G&ouml;sser off Triassic Park ; Cave: Steinbruckenhö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.
*begin Wibble
; Locn: Loser Plateau, Austria, Kataster Gruppe 1623
; Cave: Kaninchenhohle, 1623/161
; ====== stations refindable to link to other surveys: ====== ; ====== stations refindable to link to other surveys: ======
;*export pt1.37 ; CM in Triassic Park II on L wall just past way to Wibble *export 0 ; list all exported survey points.
; ====== links between surveys making up the Wibble survey: ====== *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
*equate pt1.0 pt2.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
*begin pt1 ;stn L R U D Desc
;1 0.7 0.4 0.3 0.5 RP top of boulder
; Cave: Kaninchenhohle, 1623/161 <i>[and the rest of the station details]</i>
; Survey Name: Wibbled by G&ouml;sser - passage from QM 98-23 *end wibble
; Date: 2000.08.03
; By: Inst: M I Opic
; Notes: D S Lexic
; Pics: DSL
; Tape: Both
; Instruments: Compass # 873542, Clino # 923473, 30m fibron tape
; Calibration: at 161d
; A-&gt;B 214, -09
; B-&gt;A 035, +08
; ref.: 2000 KH survey book pp 21-26
; ====== stations refindable to link to other surveys: ======
;*export 0 ; 2nd bolt at head of new pitch
;*export 37 ; CM in Triassic Park II on L wall just past way to Wibble
; Tape was 20cm too short (snapped on first pitch on way down)-:
*calibrate tape +0.20
*calibrate clino -0.5
;From to Tape Compass Clino
0 1 16.35 007 -32
2 1 4.22 195 +03 ; legs from 1 to 13 are in Zipfer Rift
; etc.
36 37 3.12 037 -47
;station details
;name L R U D E details
;0 0 1.1 3.2 pitch ? 2nd bolt
;1 1.2 0.3 4.1 0.6 thread: start traverse line
; etc.
;36 0.2 0.2 1.0 2.5 in squeeze - widest point
;37 1.4 0.8 6.2 1.3 existing station in TP2
*end pt1
*begin pt2
; etc. for part two survey
*end pt2
*end Wibble
</pre> </pre>
<p>That lot would be typed by copying template/161.svx to <p>That lot would be typed by copying caves/204/template.svx to
161/triassic/wibble.svx and then filling in the blanks and adding your data. caves/204/swings/wibble.svx and then filling in the blanks and adding your
If you are linking to the rest of the survey then in the file data. If you are linking to the rest of the survey then in the file
161/triassic/alltri.svx add the lines: caves/204/swings/allswings.svx add the lines:</p>
<pre> <pre>
; 2000 surveys: *include wibble
*equate Wibble.pt1.37 Triassic.pt2.45 *equate wibble.0 swings5.2
*include Wibble
</pre> </pre>
<p>If you are entering a surface survey, copy from template/surf.svx and <p>Remember not to put surface data and underground data in the same file,
for underground survey other than Kaninchenh&ouml;hle, use template/ug.svx
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 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 files, with a defined station for the entrance, and a suitable equate in
the file which includes both surface stuff and underground stuff. 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 <p>Once you have your data typed in and checked, it must be run through the
survey software (which on expo will be survey software (which on expo will be <a
<a href="http://www.survex.com/">Survex</a>) and a href="http://www.survex.com/">Survex</a>) and a centre line printed, both for
centre line printed, both for plan and for extended elevation. Measure the plan and for extended elevation. Measure the print out to check that it really
print out to check that it really has printed at the scale you wanted has printed at the scale you wanted (typically 1:500), as this has sometimes
(typically 1:500), as this has sometimes caused problems in the past. caused problems in the past.</p>
<p>Now see the "<a href="drawup.htm">Drawing it up</a>" page. <p>Now see the "<a href="drawup.htm">Drawing it up</a>" page.</p>
<hr> <hr />
<!-- LINKS -->
<img alt="&gt;" src="../../../icons/lists/0.png">
<b>Expedition Handbook</b>:<br>
<img alt="---&gt;" src="../../../icons/lists/1.png">
<b>Surveying</b>:<br>
<img alt="------&gt;" src="../../../icons/lists/2.png">
<a href="index.htm">Back to overview</a> and index of topics<br>
<img alt="------&gt;" src="../../../icons/lists/2.png">
<a href="what.htm">What is a cave survey ?</a><br>
<img alt="------&gt;" src="../../../icons/lists/2.png">
<a href="why.htm">Why am I doing this ?</a><br>
<img alt="------&gt;" src="../../../icons/lists/2.png">
Methods: <a href="how.htm">underground</a><br>
<img alt="------&gt;" src="../../../icons/lists/2.png">
Pitfalls to avoid, <a href="hints.htm">hints'n'tips</a>
to make life easier<br>
<img alt="------&gt;" src="../../../icons/lists/2.png">
Methods: <a href="ontop.htm">surface</a><br>
<img alt="------&gt;" src="../../../icons/lists/2.png">
Getting a <a href="gps.htm">GPS fix</a><br>
<img alt="------&gt;" src="../../../icons/lists/2.png">
Base Camp: <a href="drawup.htm">drawing it up</a>,
writing the description<br>
<img alt="------&gt;" src="../../../icons/lists/2.png">
Back <a href="athome.htm">in the UK</a><br>
<img alt="---&gt;" src="../../../icons/lists/1.png">
Expo Handbook <a href="../index.htm">Introduction</a><br>
<img alt="---&gt;" src="../../../icons/lists/1.png">
<a href="../look4.htm">Prospecting guide</a><br>
<img alt="---&gt;" src="../../../icons/lists/1.png">
<a href="../rescue.htm">Rescue guide</a><br>
<img alt="---&gt;" src="../../../icons/lists/1.png">
<a href="../rigit.htm">Rigging guide</a><br>
<img alt="---&gt;" src="../../../icons/lists/1.png">
<a href="../photo.htm">Photography guide</a><br>
<img alt="&gt;" src="../../../icons/lists/0.png">
<a href="../../infodx.htm">Index to info/topics pages</a><br>
<img alt="&gt;" src="../../../icons/lists/0.png">
<a href="../../indxal.htm">Full Index to area 1623</a><br>
<img alt="---&gt;" src="../../../icons/lists/1.png">
<a href="../../areas.htm">Area/subarea descriptions</a><br>
<img alt="---&gt;" src="../../../icons/lists/1.png">
<a href="../../index.htm">Back to Expedition Intro page</a><br>
<img alt="&gt;" src="../../../icons/lists/0.png">
<a href="../../../index.htm">Back to CUCC Home page</a><br>
<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> </body>
</html> </html>