expoweb/handbook/survey/newsurvex.html

126 lines
5.5 KiB
HTML

<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Handbook - Starting a new Survex file</title>
<link rel="stylesheet" type="text/css" href="../../css/main2.css" />
</head>
<body>
<h2 id="tophead">CUCC Expedition Handbook - New Survex file</h2>
<h1>Creating a new survex file</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.
</ul>
<h2>Process</h2>
<p>
<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.]
<p>The survey data typed up must include all the notes, including station details and passage
names. Make a backup copy to another machine or USB stick as soon as you have typed it in.
New users will be using the expo laptop to create the .svx file and
you will put it in the folder
<pre>
/home/expo/loser/caves-1623/264/mongolrally.svx
</pre>
and tell someone nerdy when you have finished and they will
ensure that it is <em>saved, committed, </em>and<em> pushed</em> appropriately.
<p>If you have several parts of the cave surveyed on one trip, create several distinct .svx files.
<ul>
<li><a href="how_to_make_a_survex_file.pdf">How to make a survex file</a> - PDF
<li><a href="getin.htm">From muddy book to survex plot</a> - the survex file format (to be revised)
<li><a href="qmentry.html">How to add QM data and cave descriptions</a> - and why this is vital
<li><font color=red>[survex software docm.]</font> <a href="https://survex.com/docs/manual/svxhowto.htm">Contents of .svx files</a> - How do I?
<li><font color=red>[survex software docm.]</font> <a href="https://survex.com/docs/manual/genhowto.htm">How do I Create a new survey</a> - example with several surveys joined
<li><font color=red>[survex software docm.]</font> <a href="https://survex.com/docs/manual/datafile.htm">Survex data files</a> - all the sections and keywords explained
</ul>
<p>Once you have created the .svx file you will run survex to generate a centre line, transcribe your sketches onto that paper, scan it again and then digitise into tunnel or therion.
<ul>
<li><a href="drawup.htm">Drawing up your survey</a> - incomplete and a bit out of date
<li><a href="athome.htm">Back in the UK</a> - not really part of the process
<li><a href="/expofiles/presentations/cave_surveying_20130626.pdf">Cave Surveying - training course slidepack</a>
</ul>
<p>[Nerds: survex cave data belongs in the repository "loser", e.g.
loser "caves-1623/264/mongolrally.svx". We are assuming that normal users have never
worked with an distributed version control system at this point which is why we are only
telling them to use the <em>expo laptop</em>.]
<h3><a id="tickingoff">Ticking off QMs</a></h3>
<p>To be written.</p>
<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="/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>
<hr />
</body>
</html>