expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2024-11-22 07:11:55 +00:00
Code Issues Packages Projects Releases Wiki Activity

knitting in docmn for writing logbook entries, fixing old survey methods

Browse Source
This commit is contained in:
Philip Sargent 2018-08-09 11:31:45 +02:00
parent e4e88a73d7
commit a3ff1cacc2
9 changed files with 92 additions and 66 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

74
handbook/geartape.html
View File

@ -79,6 +79,7 @@ Galaxy pattern</span>
</td>
<td>2018
</td></tr>
<tr>
<td><span style="border: thin solid black; color:#000; background:#ff0;"><span style="color:#000; background:#8f4;">E</span>a<span style="color:#000; background:#8f4;">r</span>t<span style="color:#000; background:#8f4;">h</span></span>
</td>
@ -86,6 +87,30 @@ Galaxy pattern</span>
</td>
<td>2018
</td></tr>
<tr>
<td><span style="border: thin solid black; padding: 0.3ex 0.5em; color:black; background:#ff0;">Yellow</span> toughtags
</td>
<td>Christopher Holt
</td>
<td>2018
</td></tr>
<tr>
<td><span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#808;">
Purple</span> toughtags
</td>
<td>Cat Henry
</td>
<td>2018
</td></tr>
<tr>
<td><span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#f00;">
Red</span> toughtags
</td>
<td>Adam Henry
</td>
<td>2018
</td></tr>
</table>
<br>
@ -121,15 +146,7 @@ Galaxy pattern</span>
<tr>
<td><span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#000;">
***</span>, <span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#000;">
***</span>
</td>
<td>Christopher Holt
</td>
<td>2018
</td></tr>
<tr>
<td><span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#000;">
***</span>, <span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#000;">
@ -172,26 +189,6 @@ Galaxy pattern</span>
<td><span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#999;">
Grey</span>, <span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#0c0;">Green</span>
</td>
<td> Manfred Wuits (Vienna)
</td>
<td>2018
</td></tr>
<tr>
<td><span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#999;">
Grey</span>, <span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#000;">
Black</span>
</td>
<td> Adam Aldridge (ULSA)
</td>
<td>2018
</td></tr>
<tr>
<td><span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#000;">
***</span>, <span style="border: thin solid black; padding: 0.3ex 0.5em; color:black; background:#000;">
@ -211,20 +208,23 @@ Black</span>
<td>2018
</td></tr>
<tr>
<td><span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#000;">
***</span>, <span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#000;">
***</span>
<td><span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#999;">
Grey</span>, <span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#0c0;">Green</span>
</td>
<td>Cat Henry
<td> Manfred Wuits (Vienna)
</td>
<td>2018
</td></tr>
<tr>
<td><span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#000;">
***</span>, <span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#000;">
***</span>
<td><span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#999;">
Grey</span>, <span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#000;">
Black</span>
</td>
<td>Adam Henry
<td> Adam Aldridge (ULSA)
</td>
<td>2018
</td></tr>

15
handbook/logbooks.html
View File

@ -10,7 +10,11 @@
the base camp logbook or the top camp logbook. All these logbook entries are then typed into a laptop (often the expo laptop)
which is then synchronised the version control system.
<h3>Where the logbook file is kept</h3>
<p>The logbook writeup is the oldest and most basic way of recording your trip but it must not be neglected. This is also where you put
your speculations and ideas for what looks promising and what is obvious but doesn't go: things that are vital to future expoers. And please, please
do lots of sketches in the logbook.
<h3>Where the logbook computer file is kept</h3>
<p>If you are using the <em>expo laptop</em> just edit this file:
<pre>
/home/expoweb/years/2018/logbook.html
@ -22,10 +26,13 @@ and other people will take care of synchronising it with the version control sys
copy it by email or USB stick to another laptop, edit it there and then copy it back. That will
<em>delete other people's work</em>.
<p>If you are using your own laptop then you will need to
<a href="update.htm#manual">install and learn how to use</a> the version control software.
<p>If you are using your own laptop then you will need to either:
<ul>
<li>Just type up your trip as a separate file, or just write it in an email, and send it to someone nerdish, or
<li><a href="update.htm#manual">install and learn how to use</a> the version control software.
And you will need to synchronise regularly (every day) to
ensure that the updates from all the people entering trip data are OK and don't get overwritten by ignorant use of this software.
</ul>
<p>Logbooks are typed up and kept in the [expoweb]/years/[nnnn]/ directory as 'logbook.html'.</p>
@ -41,7 +48,7 @@ ensure that the updates from all the people entering trip data are OK and don't
</pre>
<p>Note that the ID's must be unique, so are generated from 't' plus the trip date plus a,b,c etc.
when there is more than one trip on a day.</p>
<p>T/U stands for "Time Underground" in hours <em>or</em> minutes.
<p>T/U stands for "Time Underground" in hours (6 minutes would be "0.1 hours").
<hr />
<h3>Historical logbooks</h3>

1
handbook/survey/newcave.html
View File

@ -21,6 +21,7 @@ survey information in your waterproof notebook.
<p>After 40 years or so, we have a well-defined process which you will need to learn.
<ul>
<li>Write up your trip in the <a href="../logbooks.html">logbook</a><br><br>
<li>Put notes in a new wallet
<li>Scan the notes
<li>Type in survey data (in the right place in the file system)

49
handbook/survey/ontop.htm
View File

@ -1,7 +1,5 @@
<!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: Surface surveys</title>
<link rel="stylesheet" type="text/css" href="../../css/main2.css" />
</head>
@ -10,18 +8,9 @@
<h2 id="tophead">CUCC Expo Surveying Handbook</h2>
<h1>Surface surveys</h1>
<p>All features of speleological interest should be recorded with a minimum
of two bearings on fixed landmarks (see <a href="../findit.htm">separate
document</a> for pictures of the various peaks we use). However, anything
which gets a number should eventually be linked into an existing Surface
Survey. The number (on a metal tag) will eventually be attached to the cave
entrance with a bolt, so it is useful to drill a hole for this (and place the
spit if possible) early on, so you can use that point as the start of the
underground or surface surveys. If possible, it helps to fix new stuff with a
GPS (use waypoint averaging for a couple of hours whilst you explore it).
There is a separate manual document for <a href="gps.htm">using GPS on
expo</a>.</p>
<h3>Surface surveying is different</h3>
<p>
<a href="../../piclinks/ssvypl.htm"><img src="../../tinypix/ssvypl.jpg"
width="122" height="122" alt="" class="onleft" /></a>
@ -33,8 +22,9 @@ photographic tripod which is handy. Make sure not to place a compass too near
anything made of steel! An aluminium pole (old tent pole, ski stick or any
odd bit of tube or angle) is light and effective. Making it a useful length
(eg. 1m or 1.5m) means it can double as a ruler for measuring features.
<p>
Surface survey legs tend to be longer than underground ones, so errors from
poor compass/clino readings are bigger. In good light you may find it easier
poor compass/clino/distoX angle readings are bigger. In good light you may find it easier
or get more consistent results by sighting the compass with <b>one</b> eye
rather than two. Remember to do this consistently, and use the same method
when doing your calibration. For better accuracy, you should really keep the
@ -42,13 +32,16 @@ survey legs short (6m gives a compass/clino error comparable with a 5cm
station position error). This makes the survey take much longer, and maybe
more prone to recording errors, so a good compromise is to keep legs down to
15m or less, which also makes sketching a little easier.</p>
<p>Using a distoX above ground does make it hard to see the laser spot in bright
sunlight of course, which limits the length of legs (except at dusk).
<p><b>Don't neglect sketching!</b> Cold, exhaustion and call-out times should
not be such a restriction on surface surveys, so don't do a rush job (it is
best <b>not</b> to do surface surveys when the weather is awful:-). A good
surface sketch makes caves easier to find, possibly saving future cavers from
repeating your bearings to find the entrance. Eventually such sketches will
build to a map of the area, showing which bits have really been looked at. It
build to a map of the area, showing which bits have really been looked at.
<p>It
is conventional to survey to the cave marker tag, where there is one (and you
could always drill a spit for one, and survey to it). Failing that, the centre
of the painted number or middle of the "+" sign, or the first bolt of the
@ -62,6 +55,32 @@ readily be found again, for example a drilled hole in a prominent boulder
easier to find end point - better to lose one or two legs than have to redo
the whole survey!</p>
<h3>Entrances and holes</h3>
<p>All features of speleological interest should have their position recorded exactly.
These days (2018) a long-average (200+ readings) GPS location is fine (see <a href="gps.htm">GPS for entrances</a>) in most parts of our caving area.
This usually means using a handheld GPS device rather than a phone unless you have a particularly
good GPS app which provides an averaging function.
<p>If you are close to a big cliff, or almost inside an overhang, then an averaged-GPS will be good (~ 2m accuracy)
for latitude/longitude but appallingly misleading for altitude. In some parts of our area, such as the steep cliffs of
the Weisse Wand near Schnellzugh&ouml;hle (as seen in <a href="../../piclinks/ssvypl.htm">the photo at the top of this page</a>),
altitude is important for route-finding so GPS becomes surprisingly much less useful for re-finding locations. Before you use
GPS you really should read <a href="gps.htm">GPS for entrances</a>.
There is more about GPS altitudes in <a href="coord.htm">Olaf's article on GPS in Austria</a>.
<p>Without GPS we need an old-fashioned survey location using fixed points
with a minimum
of two bearings on fixed landmarks (see <a href="../findit.htm">taking bearings
</a> page for how to do this and for pictures of the various peaks we use).
<p>Anything
which gets a number (e.g. 2018-ad-01) should eventually be linked into an existing surface
survey. The number (on a metal tag) will be attached to the cave
entrance with a bolt, so it is useful to drill a hole for this (and place the
spit if possible) early on, so you can use that point as the start of the
underground or surface surveys. Always fix new stuff with a
GPS (use waypoint averaging) as even if this is not full survey-quality it does prevent things getting lost.
There is a separate manual page for <a href="gps.htm">using GPS for entrances</a>.</p>
<h3>Finding a starting point</h3>
<p>If your new cave is near a well-documented one, then a short connecting

4
handbook/survey/why.htm
View File

@ -1,14 +1,12 @@
<!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: Rationale</title>
<link rel="stylesheet" type="text/css" href="../../css/main2.css" />
</head>
<body>
<h2 id="tophead">CUCC Expo Surveying Handbook</h2>
<h1>Why am I doing this? The rationale for surveying what you find</h1>
<h1>Why am I doing this?</h1>
<p>The main aim of the expedition is to explore new passages - to boldly

4
piclinks/ssvypl.htm
View File

@ -1,7 +1,5 @@
<!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>
Surface Survey - Stellerweg area
</title>
@ -12,7 +10,7 @@ Surface Survey - Stellerweg area
<p>Pete Lancaster surface surveying on the SE slopes of the Vorderer
Schwarzmooskogel, above the Stellerwegh&ouml;hle system.</p>
<p class="caption">Photo &copy; Chas. Butcher, 1982?</p>
<p class="caption">Photo &copy; Chas. Butcher, 1983. lookfutile.svx</p>
<!-- Photo 195, Photo-CD 6121 1651 2353 img 35 -->
<hr />
<!-- LINKS -->

5
primer.htm
View File

@ -73,9 +73,10 @@ clearly places a lot more wear and tear on the ropes, which also tend to get
muddier, so quality rigging is essential. Of course, some of this rigging is
new exploration, not just "follow the P-hangers", so it is an exciting and
challenging activity. Also, unlike a Yorkshire tourist trip, you must survey
and describe what you find &ndash; logbook write-ups form part of a long-term record
and describe what you find &ndash; <a href="handbook/logbooks.html">logbooks write-ups</a>
form part of a long-term record
of what has been done so are rather more important than on weekend meets at
home. Surveying may be an entirely new activity for first-time expo members,
home. <a href="handbook/survey/why.htm">Surveying may be an entirely new activity</a> for first-time expo members,
but it is also a very important one, and one which it is worth making the
effort to get right from the start.</p>

5
tcamps.htm
View File

@ -105,7 +105,7 @@ climbable shaft a short way beyond
<span lang="de-at">Schwarzmoossattel</span> ("The Col").
As this was adjacent to one of the very few flat areas of grass, and right
next to the path as well, this has made an ideal camp site, and was the normal
Top Camp from 1988 to 2001. Logbooks and Journal accounts at the time
Top Camp from 1988 to 2001. <a href="handbook/logbooks.html">Logbooks</a> and Journal accounts at the time
referred to this as "Camp I", despite its not being the first high
camp. A few references are to "Camp 3", which tried to reflect the
chronology. Later it was known just as "Top Camp". In
@ -123,7 +123,8 @@ limestone on which the permanent survey station "VD1" is located, on the normal
walk up to the 161 entrances on the col between the <span
lang="de-at">Vorderer</span> and <span lang="de-at">Hinterer
Schwarzmooskogels.</span> This was variously known as 'far campsite' or 'Camp
2', in the logbooks. A lack of water, sanitation, space and comfort led to this
2', in the <a href="handbook/logbooks.html">logbooks</a>.
A lack of water, sanitation, space and comfort led to this
camp being abandoned.</p>
<h3>Scarface Camp</h3>

1
years/2018/logbook.html
View File

@ -347,6 +347,7 @@ Continues deeper but I was in t-shirt and shorts. Slight cold outwards draft.
<p>Using Garmin eTrex Venture Cx GPS (WGS84)
<p>"lookfutile.svx" was surveyed by Chas and Planc in 1983 following the discovery of the futility series in 1982.
<p>This entry includes recent emails which don't otherwise have a good place to record.
<p>[Discovered a photo on the website of <a href="/piclinks/ssvypl.htm">Planc doing this survey</a>.]
<p>Much bunde going directly down from the p115x entrance. <u>Don't do that</u>,go back along the route to
Stoger Weg and go down gully at the tree with the small cairn on it (see 115 route 18th July 2018).