expoweb/handbook/survey/newsurvex.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.
    <!-- 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 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="../../documents/survex-guide.pdf">How to create a survex file</a> - PDF - Brendan;s guide.
<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">Entering the QM data</a></h3>
<p>
    QMs are the unexplored leads, they are Question Marks because we don't 
    know where they go to. There is a specific format for recording them in survex files.
</p>
<p>
    Read this <a href="qmentry.html">separate description</a> about 
    entering  the QM data into a survex file.
</p>

<h3><a id="tickingoff">Entering the cave description in the survex file</a></h3>
<p>The last part of the survex file is a description of the passage surveyed. Remember
    that this is intended to be read by people 
    <em>who have not been to that bit of the cave themselves</em>
    <code>
;------------<br />
;Cave description  ;(leave commented-out)<br />
; See 2017 description for details of GSH up to the 'p50'. 
Briefly, on the way to couldashouldawoulda a 22 m entrance crawl from the 
surface leads to a climb down and a junction. Left leads to easy c
rawling passage for a short distance, then another junction where 
traversing over a shallow hole and down a stooping-height sandy 
passage to a sharp left turn and a sandy, easy 'squeeze' leading to a 
straighforward p10. 
    </code>
[from <a href="../../"><em>couldashouldawoulda_to_bathdodgersbypass.svx</em></a>]
</p>
<p>
    Note that the description is often written as one long line. Use the word-wrap capability in your editor
    to make it easier for yourself.
</p>

<hr />
<p>Back to the previous page in this sequence 
    <a href="newwallet.html">Creating a new survey wallet</a>.
    <br />Now go the the next page in this sequence <a href="drawup.htm">Drawing up your survey</a>.


<hr />


</body>
</html>
New Cave data entry process: logbook entry, wallets, survex files, 2020-02-28 16:18:54 +00:00			`<!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.`
Brendan's PDF guides (original PPTX files - some - on expofiles/training-info) 2020-03-01 15:47:10 +00:00			`<!-- Yes we need some proper context-marking here, breadcrumb trails or something.`
			`Maybe a colour scheme for just this sequence of pages`
			`-->`
New Cave data entry process: logbook entry, wallets, survex files, 2020-02-28 16:18:54 +00:00			`</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>`
Brendan's PDF guides (original PPTX files - some - on expofiles/training-info) 2020-03-01 15:47:10 +00:00			`<li><a href="../../documents/survex-guide.pdf">How to create a survex file</a> - PDF - Brendan;s guide.`
New Cave data entry process: logbook entry, wallets, survex files, 2020-02-28 16:18:54 +00:00			`<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>.]`

Making the survey processing pipeline consistent and documented 2020-03-01 17:46:05 +00:00			`<h3><a id="tickingoff">Entering the QM data</a></h3>`
New Cave data entry process: logbook entry, wallets, survex files, 2020-02-28 16:18:54 +00:00			`<p>`
Making the survey processing pipeline consistent and documented 2020-03-01 17:46:05 +00:00			`QMs are the unexplored leads, they are Question Marks because we don't`
			`know where they go to. There is a specific format for recording them in survex files.`
			`</p>`
			`<p>`
			`Read this <a href="qmentry.html">separate description</a> about`
			`entering the QM data into a survex file.`
			`</p>`

			`<h3><a id="tickingoff">Entering the cave description in the survex file</a></h3>`
			`<p>The last part of the survex file is a description of the passage surveyed. Remember`
			`that this is intended to be read by people`
			`<em>who have not been to that bit of the cave themselves</em>`
			`<code>`
			`;------------<br />`
			`;Cave description ;(leave commented-out)<br />`
			`; See 2017 description for details of GSH up to the 'p50'.`
			`Briefly, on the way to couldashouldawoulda a 22 m entrance crawl from the`
			`surface leads to a climb down and a junction. Left leads to easy c`
			`rawling passage for a short distance, then another junction where`
			`traversing over a shallow hole and down a stooping-height sandy`
			`passage to a sharp left turn and a sandy, easy 'squeeze' leading to a`
			`straighforward p10.`
			`</code>`
			`[from <a href="../../"><em>couldashouldawoulda_to_bathdodgersbypass.svx</em></a>]`
			`</p>`
			`<p>`
			`Note that the description is often written as one long line. Use the word-wrap capability in your editor`
			`to make it easier for yourself.`
			`</p>`
New Cave data entry process: logbook entry, wallets, survex files, 2020-02-28 16:18:54 +00:00
Making the survey processing pipeline consistent and documented 2020-03-01 17:46:05 +00:00			`<hr />`
			`<p>Back to the previous page in this sequence`
			`<a href="newwallet.html">Creating a new survey wallet</a>.`
			`<br />Now go the the next page in this sequence <a href="drawup.htm">Drawing up your survey</a>.`
New Cave data entry process: logbook entry, wallets, survex files, 2020-02-28 16:18:54 +00:00


			`<hr />`


			`</body>`
			`</html>`