mirror of
https://expo.survex.com/repositories/expoweb/.git/
synced 2024-11-25 00:32:01 +00:00
138 lines
8.5 KiB
HTML
138 lines
8.5 KiB
HTML
<!DOCTYPE html>
|
|
<html>
|
|
<head>
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
|
<title>CUCC Expo Surveying Handbook: Drawing Up</title>
|
|
<link rel="stylesheet" type="text/css" href="../../css/main2.css" />
|
|
</head>
|
|
|
|
<style type="text/css">
|
|
|
|
#outer
|
|
|
|
}
|
|
</style>
|
|
|
|
<body>
|
|
<h2 id="tophead">CUCC Expedition Handbook - New rigging guide</h2>
|
|
<h1>New rigging guide</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.
|
|
|
|
<div style="width:100%;height:50px;background:#C8E1E2" align="center">
|
|
This page outlines step 5 of the survey production process. Each step is documented separately.<br />
|
|
<!-- Yes we need some proper context-marking here, breadcrumb trails or something.
|
|
Maybe a colour scheme for just this sequence of pages
|
|
-->
|
|
<a href="newcave.html">1</a>
|
|
- <a href="newwallet.html">2</a>
|
|
- <a href="newsurvex.html">3</a>
|
|
- <a href="drawup.htm">4</a>
|
|
- <a href="newrig.html">5</a>
|
|
- <a href="caveentry.html">6</a>
|
|
- <a href="ententry.html">7</a>
|
|
- <a href="cavedescription.html">8</a></div>
|
|
</ul>
|
|
<h2>Process</h2>
|
|
<p>
|
|
|
|
<h3>Interim rigging guide</h3>
|
|
<a href="/expofiles/rigging_topos/264/entrance_topo1_2016.jpeg"><img class="onright" src="264-thumb.jpg"></a>
|
|
The logbook is the place where we record the rigging of caves as soon as possible after we discover them. For a particularly fine example of rigging guides in a logbook, scroll through <a href="../../years/2015/logbook.html">the 2005 logbook</a>.
|
|
<p><strong>SAFETY:</strong> Sketched rigging guides are most intensively used during the few days after the pitch is first rigged, and this is also the time when accidents are most likely, so this is an occasion where hours count. <em>Sketch the rigging in the logbook as soon as possible</em> and make sure a copy is at both base camp and top camp.
|
|
<p>When a cave is derigged,
|
|
a good way of getting the rope lengths for your rigging guide is to
|
|
leave the knots in ropes removed so they can
|
|
be <b>measured</b>, but these days our caves are a bit deep
|
|
and complicated for this to be feasible.
|
|
Although a good survey and details of the belays
|
|
can be used to estimate the length of rope needed, this is no substitute for
|
|
measuring how much rope it actually took to rig. So please do this during the initial exploration and write it down in your survey notes.</p>
|
|
|
|
<h3>Preparation of rigging notes</h3>
|
|
<p>
|
|
You will already have an "Interim rigging guide" in the logbook entries of the trips, and also sketches on waterproof paper
|
|
which were made underground which were stored in the survey wallet and scanned to produce "notes-XXX.jpg" files in the online survey wallet for your trip. For small caves the logbook entry may be all you need.
|
|
<p>Collect together your notes for the rigging guide now, including all the pitch lengths. It is a good idea to copy these notes now and put them in the plastic survey wallet or to photograph them and put the files in the <a href="newwallet.html">online survey wallets</a>. The next step of doing the survey can take some time so get the rigging data in order now so that it doesn't get forgotten.
|
|
|
|
<h3>Final rigging guide</h3>
|
|
|
|
<p>A <b>Rigging Guide</b> of the vertical sections is published with the cave survey and the cave passage descriptions in the cave guide after surveying is complete.
|
|
|
|
This is usually easiest to do as a sketch, but must include notes to
|
|
ensure that all bolts can be found again and any deviations and natural belays recognised for re-rigging in future.
|
|
|
|
<p>You will enter the final rigging guide sketch as a scanned drawing within the
|
|
cave description when you edit the HTML pages for the online cave documentation.
|
|
This is done using the "New Cave" online form.
|
|
|
|
<p>Your initial rigging guide might be needed with some urgency during expo while exploration continues, so this is the place to put it.</p>
|
|
</p>
|
|
|
|
<p>See also the part of the <a href="../rig/rigit.html">bolting & rigging handbook</a> which discusses writing up your rigging attempts.
|
|
|
|
<h3>Filing and Finding rigging guides</h3>
|
|
<p>There are three different activities for rigging topos:
|
|
<ul>
|
|
<li>drawing them up (either scanning or re-drawing scrappy images out of logbooks),
|
|
<li>making them findable/appear in cave descriptions,
|
|
<li>(optionally) making prettier versions for important caves which have complex rigging.
|
|
</ul>
|
|
<p>The simple and nicest-looking way to make them findable is to add them to the HTML inline in cave descriptions. For a finished
|
|
example see the rigging topo for the "<a href="/1623/204/swings.html">Merry Go Round</a>" pitches in the Swings and Roundabouts area
|
|
in 204.
|
|
|
|
<a href="caveentry.html">Creating a new cave in the online system</a> is how you create the inline HTML. It is the next step in this
|
|
Survey Handbook sequence of pages. <br><em>[To Do - improve documentation for how to add in image files in cave descriptions]</em>
|
|
|
|
<p>You should produce a separate rigging guide file for each connected set of pitches which will initially live in<br>
|
|
<var>expofiles/rigging_topos/</var> e.g. see <br>
|
|
<a href="/expofiles/rigging_topos/264/entrance_topo_2016.pdf">expofiles/rigging_topos/264/entrance_topo_2016.pdf</a><br>
|
|
but also (to demonstrate that something is always better than nothing):<br>
|
|
<a href="/expofiles/rigging_topos/264/entrance_topo2_2016.jpeg">expofiles/rigging_topos/264/entrance_topo2_2016.jpeg</a>
|
|
|
|
<p>The format is important. Please <em>don't</em> use PDF: if you are scanning a hand-drawn sketch then JPEG is best for our purposes as it is compact and we reuse it easily elsewhere in the system.
|
|
<p>If you are using a drawing package then produce the file in SVG format.
|
|
<a href="https://www.theregister.com/2020/04/14/16_years_inkscape_v1/">Inkscape</a> is what most cavers use as it's free and stable. This will make it possible to edit and update your topo in future.
|
|
|
|
<h3>Uploading the topo files</h3>
|
|
<p>When you first produce a topo, don't upload it to the server. Copy it to the right folder on the <var>expo laptop</var> in the potato hut and
|
|
tell a nerd on expo that it is there. Or, if you are confident with Filezilla, copy it from the <var>expo laptop</var> to the server and then move the copy on the
|
|
<var>expo laptop</var> to e.g. <var>expofiles/rigging_topos/2022/copied-to-server/</var>
|
|
|
|
<p>If you draw up the topo after expo is over, then email them to a nerd who will upload them into the right place.
|
|
|
|
<p>If you have your own machine configured as a <a href="../computing/bulkupdatelaptop.html">expo bulk update laptop</a> then you can use
|
|
<a href="../computing/fzconfig.html">Filezilla</a> to upload the topo files directly to the server.
|
|
|
|
<h3>This may be a change from how you used to do it</h3>
|
|
<p>Discussions on Expo Slack after the 2019 expo resulting in us consolidating rigging topo files into
|
|
<var>expofiles/rigging_topos/</var> when previously they had had a number of different homes. So if you remember putting them
|
|
somewhere else in the past, don't do that now. Put them in <var>expofiles/rigging_topos/</var>.
|
|
|
|
<p>Eventually when the full cave description is written up, selected topos will be moved to the
|
|
<var>:expoweb:</var> verson-controlled repository
|
|
where they will be linked in to the HTML files for the cave descriptions, e.g.
|
|
<a href="/topos/204/kiwi.svg"><var>:expoweb:/topos/204/kiwi.svg</var></a>.
|
|
|
|
<p>[ We could dream up some fancy scheme for indexing the rigging for every pitch in the system and add that
|
|
into troggle but frankly we don't think it's worth the effort.]
|
|
|
|
<h3>Final editing of cave descriptions</h3>
|
|
<p>If you look in detail at the description of <a href="/1623/204/204.html">Steinbrückenhöhle</a> you will see rigging topos
|
|
inline as pixel images (not vector files) in the passage descriptions. These are stored with the passage HTML files, e.g.
|
|
in <a href="/1623/204/rigging/kiwi.png"><var>:expoweb:</var>/1623/204/rigging/kiwi.png</a>,
|
|
whereas the master copy of this rigging diagram is the vector file at
|
|
<a href="/topos/204/kiwi.svg"><var>:expoweb:</var>/topos/204/kiwi.svg</a>. We needed both because web browsers
|
|
used not to be able to display SVG files embedded in HTML.
|
|
<p>If you use a vector file format which is not SVG you may still need to do
|
|
this vector-to-pixel conversion when you write up the cave description. But we always keep the original vector file.
|
|
|
|
<hr />
|
|
<p>Back to the previous page in this sequence <a href="drawup.htm">Drawing up your survey</a>.
|
|
<br />Now go the the next page in this sequence <a href="caveentry.html">Creating a new cave in the online system</a>.
|
|
<hr />
|
|
</body>
|
|
</html>
|