Merge server changes and ropes list

1623/264/trident to little boy

@@ -0,0 +1,40 @@
+Cave: Balcony (Far Side to Deep Balcony)
+
+Trident is a four way junction- take the left fork to an alcove on the left with an obscure mud floored crawl. This is followed for 10m, improving to walking height. Follow past two bat skeletons then right turn to another bat; continue ~20m. A mud floored junction, turn right to the head of a traverse then pitch after 10m. Straight on would have led you to a noteworthy drippy pitch (Kathedral Chasm). 
+
+----Honeycomb----
+The traverse to pitch is the beginning of Honeycomb (50m of pitches). This swings to a window, following the rope to a ledge 10m above the floor. From here there's a narrow popcorn-lined climb to the head of a 7m pitch. At the bottom, climb the slope and follow obvious continuation (draught) to the head of 12m pitch. This pitch lands at the top of Hangman (p30), on account of the huge hanging boulder. (The near side of the boulder descends to the way on to the top of Mongol Rally, whereas the far side of the boulder is rigged to swing into a window half way down, Myopia. This is a passage heading north, traversing around a large pit, leading to another pitch which could be traversed around, ?a.)
+
+----Nature Calls----
+At the bottom, follow the traverse round to a mudslope. At the top of the mudslope there is an awkward crawl for 10m, soon improves to walking. Follow this passage for 30m. There's a p5, follow the rope to the head of the Mongol Rally (p200). 
+
+----Mongol Rally and Little Boy----
+Descending this rope lands into a roomy boulder chamber. Walking down the slope between boulders (distinguished path in the mud), leads to a blind pit and big aven. A right turn takes you to stooping height passage, for 50m to the head of Little Boy pitch (20m). There is a significant draught here; follow this. The camp is currently at the base of the pitch (August 2018). 
+
+----Water collection----
+There are three exits to the chamber. 
+1. a short crawl 
+2. a climb down on the far side. 
+Both lead to the same place and draught. 
+
+Leave on the far side of the chamber, via a climb down and turn right, climbing down a boulder into pleasent walking passage, very straight and heading north. The floor is soft wet mud. After ~100m a stream trench enters on the right, followed round a corner into a drippy aven. Collect water here, scoop (mug) advisable. 
+
+
+
+
+(Currently unconnected from Grand Prix)
+
+----One direction----
+A little further on from the right turn towards the water cllection, is a muddy ledge on the left hand side (1m from ground). Low crawl continues for 100m in straight line, over three puddles. Stal, but largely unnoteworthy. Ends at the Tsection into clean washed tall rift with sounds of water. Downhill leads to promising a lead, in clean washed rock, sketchy c6, requires rope, heads into rifty stuff. Uphill, includes split (meander) to scoopy loopy junction.
+
+----Scoopy Loopy----
+Scoop it until you loop it. Junction has small a lead on right hand wall, to sound of wet rift. Obvious way on cuts left, walking passage heading upwards until low crawl into breakdown chamber. A climb on the right links into Grand Prix.
+
+----Nothing to do with you traverse---- (ntdwyt)
+The passage towards the water collection is followed, beyond the turning for water. This leads to a pitch down (Indy Rally) or a traverse left. The traverse left goes ~10m, before muddy walking passage ~30m until it chokes.
+
+----Little boy beneath the boulders----
+A short 2m climb through a boulder choke leads to break down chamber directly below grand prix. Qmc at station 8, p10, probably drops level with station 6 (lbbeneaththeboulders).
+
+----Little boy bolt climbs----
+From the grand prix, left from little boy beneath the boulders is a large hanging boulder. Traverse along massive choked boulder on left hand side of grand prix. Not derigged. Climbs up steep mud slope into rift that shortly forks (station 4). P15 qmc down from here, leads probably to lbbeneaththeboulders. Sketchy rift climb qmc from here, dispute about seeing a human sized passage beyond here. 

1623/264/trident_to_little_boy

@@ -0,0 +1,21 @@
+Cave: Balcony (Far Side to Deep Balcony)
+
+Trident is a four way junction- take the left fork to an alcove on the left with an obscure mud floored crawl. This is followed for 10m, improving to walking height. Follow past two bat skeletons then right turn to another bat; continue ~20m. A mud floored junction, turn right to the head of a traverse then pitch after 10m. Straight on would have led you to a noteworthy drippy pitch (Kathedral Chasm). 
+
+----Honeycomb----
+The traverse to pitch is the beginning of Honeycomb (50m of pitches). This swings to a window, following the rope to a ledge 10m above the floor. From here there's a narrow popcorn-lined climb to the head of a 7m pitch. At the bottom, climb the slope and follow obvious continuation (draught) to the head of 12m pitch. This pitch lands at the top of Hangman (p30), on account of the huge hanging boulder. (The near side of the boulder descends to the way on to the top of Mongol Rally, whereas the far side of the boulder is rigged to swing into a window half way down, Myopia. This is a passage heading north, traversing around a large pit, leading to another pitch which could be traversed around, ?a.)
+
+----Nature Calls----
+At the bottom, follow the traverse round to a mudslope. At the top of the mudslope there is an awkward crawl for 10m, soon improves to walking. Follow this passage for 30m. There's a p5, follow the rope to the head of the Mongol Rally (p200). 
+
+----Mongol Rally and Little Boy----
+Descending this rope lands into a roomy boulder chamber. Walking down the slope between boulders (distinguished path in the mud), leads to a blind pit and big aven. A right turn takes you to stooping height passage, for 50m to the head of Little Boy pitch (20m). There is a significant draught here; follow this. The camp is currently at the base of the pitch (August 2018). 
+
+----Water collection----
+There are three exits to the chamber. 
+1. a short crawl 
+2. a climb down on the far side. 
+Both lead to the same place and draught. 
+
+Leave on the far side of the chamber, via a climb down and turn right, climbing down a boulder into pleasent walking passage, very straight and heading north. The floor is soft wet mud. After ~100m a stream trench enters on the right, followed round a corner into a drippy aven. Collect water here, scoop (mug) advisable. 
+

1623/others/l/87-1.htm

@@ -1,14 +1,12 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0//EN">
 <html>
 <head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
 <title>
 1623/87: second pitch
 </title>
 <link rel="stylesheet" type="text/css" href="../../../css/main2.css" />
 </head>
 <body>
-<img src="../i/87a.jpg" width=400 height=600 align=left hspace=20 vspace=10>
+<img src="../i/87-1.jpg" width=400 height=600 align=left hspace=20 vspace=10>
 <p>The second pitch of 1623/87 starts as a small hole following a
 steeply dipping roof tube where the floor of the entrance chamber is
 almost choked by boulders. Nick Thorne is seen here emerging from the

1623/others/l/87-2.htm

@@ -1,14 +1,12 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0//EN">
 <html>
 <head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
 <title>
 1623/87: second pitch
 </title>
 <link rel="stylesheet" type="text/css" href="../../../css/main2.css" />
 </head>
 <body>
-<img src="../i/87b.jpg" width=400 height=600 align=left hspace=20 vspace=10>
+<img src="../i/87-2.jpg" width=400 height=600 align=left hspace=20 vspace=10>
 <p>The second pitch of 1623/87 starts as a small hole following a
 steeply dipping roof tube where the floor of the entrance chamber is
 almost choked by boulders. The second bolt is just before the pitch starts

fixaid.htm

@@ -9,6 +9,8 @@
 
 <h1>Fixed aids in CUCC caves</h1>
 
+<h2 style="text-align:center; color:red">NONE of this is up to date !</h2>
+
 <p>At various points of the cave, passages have been reached by climbs up
 which would have to be repeated unless a rope was left on from year to year.
 A few pitches were explored from the top, but form potentially important

handbook/baseops.html

@@ -83,16 +83,56 @@ in the coming days.
 <h2>Other stuff</h2>
 
 <h3>Washing machine</h3>
-<p>The Gasthof has a washing machine in the lobby of the gents toilet/washroom area (down the side of the building). 
-<p>You pay &euro;3 (2018) cash at the reception (access from the front of the building) to get the key. The key turns on the power to the machine. 
+<img src="i/aa22408_01.jpeg" align=right width=30%>
+<p>The Gasthof has an A+++ "<a href="constructa-cwf14b21.pdf">Constructa energy</a>" washing machine 
+in the lobby of the gents toilet/washroom area (down the side of the building). 
+<p>You pay &euro;3 (2018) cash at the reception (access from the front of the building) 
+to get the key. The key turns on the power to the machine. 
 Return key to reception when you are done.
 <p>Expo buys washing liquid (for washing things by hand) and Ariel washing-balls (for machine washing). These are kept in the potato hut.
-<p>The washing machine has many complicated options and is labelled almost entirely in German. You probably want "Speed" (30 minutes) or "Hygiene" (2 hours 40 minutes).
+
+<p>The washing machine has many complicated options and is labelled almost entirely in German. 
+
+<p>
+Each programme has a different combination of time, temperature, spin etc. which is 
+described in the display panel on the right as you turn the knob to select the programme:
+ 
+<ul>
+<li>Mischw&auml;sche-Programm</li>
+<li>Pflegeleicht-Programm</li>
+<li>Fein-Programm</li>
+<li>Handwasch-Programm f&uuml;r Wolle</li>
+<li>Outdoor-/ Sport-Programm</li>
+<li>Kurz-Programm</li>
+<li>Blusen/Hemden-Programm</li>
+<li>Hygiene-Programm</li>
+<li>Kaltwaschen-Programm</li>
+</ul>
+<p>You probably want "Kurz" (30 minutes) wash or the "Hygiene" (2 hours 40 minutes) wash.
 
 <h3>Base camp bike</h3>
 <p>We also have <a href=bike.html>a bike</a> which we use for shopping when all the cars are up the toll road and there are only
 a handful of people at base.
 
+<h2>Buses and local travel, hitching to/from the plateau</h2>
+
+<p>See the <a href="travel.html#lastbit">How to get to Expo</a> page for details of travel 
+around Grundlsee and Bad Aussee.
+<p>Also relevant for expoers is how to get from base camp up to the plateau and back. 
+The Loser Panorama Strasse toll road leaves from the "Losermaut Skiarena" close to Bla Alm, 
+which is up a dead-end road from Alt Aussee. This is relevant because if you hitch and get a lift
+from the Loser Alm car park at the top of the toll road, you will almost certainly be going through Alt Aussee.
+<p>There are buses between Alt Aussee and Bad Aussee: route 955. See the <a href="684400_NEU.pdf">955 timetable here</a>. 
+Note that some of these are anonymous minibuses not full-sized Post buses with "955" on the front. 
+While frequent over lunchtime, there is a 2-hour gap in the late afternoon.
+<p>Here is <a href="684000_NEU.pdf">the timetable for bus 956</a> which goes to base camp and then on to Grundlesee. 
+This also may be replaced by an anonymous 
+white minibus with a taxi company logo. Don't get caught out by not getting onto it.
+<h3>Other buses from Bad Aussee</h3>
+<p>Here is the link 
+<a href="https://www.postbus.at/de/Fahrplanauskunft/Fahrplandownload/index.jsp?search=true&land=STEIERMARK&fahrplanabfrage=bad+aussee">
+to all the bus services and timetables for buses from Bad Aussee</a>. 
+If you want to go to Salzburg, you will change at Bad Ischl. 
 
 <h2>Recycling</h2>
 <h3>Glass and glass bottles</h3>

handbook/bierbook.html

@@ -42,6 +42,9 @@ This also records the number of nights spent at the bivvy and underground camp.
 </ul>
 Getting infomation on the number of people attending dinner is always difficult. Try to get this filled in a week in advance.
 
+<h3 id="sesh">Scanned copies of Bier and Sesh Books</h3>
+<p>The 2016 expo bierbook and seshbook were scanned and can be downloaded (13MB and 5 MB) from here: 
+<a href="http://expo.survex.com/expofiles/writeups/2016/">expofiles/writeups/2016/</a>
 <h3>Expenses and money owed</h3>
 <p>As well as writing the amounts of money in the books, printed receipts for expo expenses need to be put in the envelope in the potato hut. 
 <p>Each receipt needs the name of the person paying and a sequence number if you have more than one receipt.

handbook/bike.html

@@ -15,10 +15,9 @@ hitched up from there. It's still hard work - especially from Alt Aussee to Bla
 
 <h2>Bike Lock</h2>
 <pre>
-Lock code: 1241
+Lock code: 161
 </pre>
-<p>This is easily remembered if you just recall that this is the year that the Mongols invaded 
-Poland.
+
 <h2>Lights and basket</h2>
 <p>There are no bike lights (use a couple of head-torches, one with red LEDs facing backwards) and no basket or paniers. Use a rucksack.
 <h2>History</h2>

handbook/datamgt.html

@@ -8,6 +8,13 @@
 
 <h1>Why cavers need effective data management</h1>
 
+<div style="text-align:left">
+<!-- Comment 
+Justified text is hard to read:
+https://designshack.net/articles/mobile/the-importance-of-designing-for-readability/
+https://designforhackers.com/blog/justify-text-html-css/
+-->
+
 <p>
 Cave exploration is more data-intensive than any other sport. The only way to "win" at this
 sport is to bring back large quantities of interesting survey, and possibly photos or scientific 
@@ -41,6 +48,7 @@ the realm of the frivolous, an expedition might store mugshots and biographies o
 or even useful recipes for locally available food. The more of this information the expedition 
 wishes to keep, the more valuable an effective and user-friendly system of data management.
 
+</div>
 <p><em>From "<a href="../../troggle/docsEtc/troggle_paper.odt" download>
 Troggle: a novel system for cave exploration information management</a>", by Aaron Curtis, CUCC.</em>
 <hr />

handbook/essentials.gpx

@@ -0,0 +1 @@
+/home/expo/loser/gpx/essentials.gpx

handbook/essentials.html

@@ -1,7 +1,7 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-<title>Handbook placeholder page</title>
+<title>Essential GPS information</title>
 <link rel="stylesheet" type="text/css" href="../css/main2.css" />
 </head>
 <body>

handbook/exposerver.html

@@ -0,0 +1,19 @@
+<html>
+<head>
+<title>Expo server</title>
+<link rel="stylesheet" type="text/css" href="../css/main2.css" />
+</head>
+<body>
+<h2 id="tophead">CUCC Expedition Handbook - Expo server in Cambridge</h2>
+<h1>Expo server in Cambridg</h1>
+<p>This is not the page you are looking for.
+<p>This will be replaced with the information you want as soon as someone gets around to writing it. Why not find out how to do this yourself ?
+
+
+<hr />
+
+<ul id="links">
+<li><a href="index.htm">Expedition Handbook</a>
+</ul>
+</body>
+</html>

handbook/fzconfig.html

@@ -15,8 +15,27 @@
 <li>Open Filezilla and start it running.
 <li>Click on the "File" menu item, and select the "Import..." command, this will open a file browser on your local machine
 <li>Navigate to your default downloads folder and select the <b>zilla-uploads.xml</b> file.
-<li>Now select the "Bookmarks" menu item: at the bottom of the drop-down menu you will see "Expo-uploads". Click on it.
+<li>Now select the "Bookmarks" menu item: 
+<ul>
+<li>At the bottom of the "Bookmarks" drop-down menu you may see "Expo-uploads"; 
+if so, click on it.
+<li>If you can't see "Expo-uploads" in that menu 
+(because this is temporarily broken in version 3.28 of Filezilla), 
+click on the "File" menu item and select "Site Manager...". 
+This will display a tree-structured menu in a sub-window and one of the items will be "Expo-uploads". Highlight it 
+and then click on the "Connect" button at the bottom of the sub-window.
+</ul>
 <li>You will now be prompted for the password for the expo server. This is the "cavey:beery" one which we never write down or write in emails. Get it verbally or by phone or secure text message from another expoer.
+<li>Now check that these Filezilla settings are set correctly:
+<ul>
+<li>In the "Transfer" menu, ensure that "Preserve timestamps of transferred files" is <em>ticked</em>. Yes,you want to keep the timestamps.
+<li>In the "View" menu,ensure that "Synchronized browsing" is <em>NOT ticked</em>. 
+(This will be greyed-out if you are not actually connected to the remote fileserver.)<br>
+It is vital that this is un-ticked because you don't have a complete copy of the entire server website on your laptop, and Filezilla
+may try to delete things on the server which you don't have on your laptop, i.e.most of it. 
+This setting should be fixed automatically in <b>zilla-uploads.xml</b> but we have seen occasions where it 
+seems to have been re-set somehow.
+</ul>
 <li>Now you are in and can copy and move files anywhere. But please don't: stick to copying files from your machine (the left window) to the server (the right window):<br><br>
 
 <a href="fzexample.png" border=2><img src="fzexample.png" align=center width=65%></a><br>(Click to enlarge).

handbook/geartape.html

@@ -0,0 +1,468 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<title>Expo Handbook gear tape colours</title>
+<link rel="stylesheet" type="text/css" href="../css/main2.css" />
+</head>
+<body>
+<h2 id="tophead">CUCC Expedition Handbook - Gear Tape</h2>
+<h1>Gear tape colours for Expo 2018</h1>
+<p>Selected from <a href="https://www.srcf.ucam.org/caving/wiki/Gear_Tape_Colours">CUCC Gear Tape</a> for just those on expo with non-CUCC invitees added.
+<p>
+
+<table border="1" cellspacing="0" cellpadding="5" align="center">
+<tr>
+<td><b>Colour - 1</b>
+</td>
+<td><b>Name</b>
+</td>
+<td><b>Expo?</b>
+</td></tr>
+<tr>
+<td><span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#808;">
+Purple</span>
+</td>
+<td> <b>EXPO  communal property</b>
+</td>
+<td>2018
+</td></tr>
+<tr>
+<td><span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#808;">
+Purple</span>
+</td>
+<td>George Breley (SUSS)
+</td>
+<td>2018
+</td></tr>
+<tr>
+<td><span style="border: thin solid black; padding: 0.3ex 0.5em; color:black; background:#ccc;">
+<em>none</em></span>
+</td>
+<td> Typhon King  (ULSA)
+</td>
+<td>2018
+</td></tr>
+
+<tr>
+<td><span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#999;">
+Grey</span> duct tape
+</td>
+<td> Ryan Boultbee (NUCC)
+</td>
+<td>2018
+</td></tr>
+
+
+<tr>
+<td><span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#0c0;">Green</span>
+</td>
+<td> Rachel Turnbull  (ULSA) 
+</td>
+<td>2018
+</td></tr>
+<tr>
+<td><span style="border: thin solid black; padding: 0.3ex 0.5em; color:black; background:#FF1493;">
+Fairies pattern</span>
+</td>
+<td>  Adelaide de Diesbach (SUSS)   
+</td>
+<td>2018
+</td></tr>
+<tr>
+<td><span style="border: thin solid black; padding: 0.3ex 0.5em; color:black; background:#ccc;">
+Galaxy pattern</span>
+</td>
+<td> Michael Holliday (SUSS) 
+</td>
+<td>2018
+</td></tr>
+<tr>
+<td><span style="border: thin solid black; padding: 0.3ex 0.5em; color:black; background:#40E0D0;">Turquoise</span>
+</td>
+<td> Rachel Turnbull  (ULSA) 
+</td>
+<td>2018
+</td></tr>
+<tr>
+<td><span style="border: thin solid black; padding: 0.3ex 0.5em; color:black; background:#fff;">White</span>
+</td>
+<td>Philip Sargent
+</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>
+<td>Frank Tully
+</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>
+
+<table border="1" cellspacing="0" cellpadding="5" align="center">
+<tr>
+<td><b>Colour - 2</b>
+</td>
+<td><b>Name</b>
+</td>
+<td><b>Expo?</b>
+</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>
+<td> Jim Blackford  (UBSS)
+</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>
+<td> Lisa Smith (UBSS)
+</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>
+<td> Dickon Hood (UBSS)
+</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>
+<td> Olly Hall (SUSS) 
+</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>
+<td>Todd Rye (MUSC)
+</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>
+<td>Philip Withnall 
+</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:#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;">Black</span>, <span style="border: thin solid black; padding: 0.3ex 0.5em; color:black; background:#ff0;">Yellow</span>
+</td>
+<td>Anthony Day
+</td>
+<td>2018
+</td></tr>
+<tr>
+<td><span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#000;">Black</span>, <span style="border: thin solid black; padding: 0.3ex 0.5em; color:black; background:#ff0;">Yellow</span>
+</td>
+<td>Nadia Raeburn-Cherradi (ULSA)
+</td>
+<td>2018
+</td></tr>
+
+
+<tr>
+<td> 
+<span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#000;">Black</span>,
+<span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#0c0;">Green</span>
+</td>
+<td>Jon Arne Toft
+</td>
+<td>2018
+</td></tr>
+
+
+<tr>
+<td><span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#000;">
+Black</span>, <span style="border: thin solid black; padding: 0.3ex 0.5em; color:black; background:#f00;">
+Red</span>
+</td>
+<td>Luke Stangroom (ULSA)
+</td>
+<td>2018
+</td></tr>
+<tr>
+<td><span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#000;">Black</span>, <span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#00f;">Blue</span>
+</td>
+<td>Chris Densham
+</td>
+<td>2018
+</td></tr>
+
+
+
+<tr>
+<td> 
+<span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#840;">Brown</span>,
+<span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#00f;">Blue</span>
+</td>
+<td>Ruairidh Macleod
+</td>
+<td>2018
+</td></tr>
+
+<tr>
+<td><span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#840;">Brown</span>, 
+<span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#0c0;">Green</span>
+</td>
+<td>Wookey 
+</td>
+<td>2018
+</td></tr>
+
+
+
+<tr>
+<td><span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#808;">Purple</span>, 
+<span style="border: thin solid black; padding: 0.3ex 0.5em; color:black; background:#ff0;">Yellow</span>
+</td>
+<td>Mark Shinwell
+</td>
+<td>2018
+</td></tr>
+<tr>
+<td> 
+<span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#808;">Purple</span>,
+<span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#00f;">Blue</span>
+</td>
+<td>Lydia-Clare Leather (NUCC)
+</td>
+<td>2018
+</td></tr>
+<tr>
+<td><span style="border: thin solid black; padding: 0.3ex 0.5em; color:black; background:#fff;">White</span>, 
+<span style="border: thin solid black; padding: 0.3ex 0.5em; color:black; background:#f00;">Red</span>
+</td>
+<td>Mike Butcher (ULSA)
+</td>
+<td>2018
+</td></tr>
+<tr>
+<tr>
+<td><span style="border: thin solid black; padding: 0.3ex 0.5em; color:black; background:#fff;">White</span>, 
+<span style="border: thin solid black; padding: 0.3ex 0.5em; color:black; background:#f00;">Red</span>
+</td>
+<td>Philip Sargent
+</td>
+<td>2018
+</td></tr>
+<tr>
+<td><span style="border: thin solid black; padding: 0.3ex 0.5em; color:black; background:#fff;">White</span>,
+<span style="border: thin solid black; padding: 0.3ex 0.5em; color:black; background:#f00;">Red</span> 
+
+</td>
+<td>Michael Sargent
+</td>
+<td>2018
+</td></tr>
+<tr>
+<td><span style="border: thin solid black; padding: 0.3ex 0.5em; color:black; background:#fff;">White</span>, <span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#00f;">Blue</span>
+</td>
+<td>Haydon Saunders
+</td>
+<td>2018
+</td></tr>
+<tr>
+<td><span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#00f;">Blue</span>, <span style="border: thin solid black; padding: 0.3ex 0.5em; color:black; background:#ff0;">Yellow</span>
+</td>
+<td>Becka Lawson
+</td>
+<td>2018
+</td></tr>
+
+
+
+
+<tr>
+<td><span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#00f;">Blue</span>,
+<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>
+</span>
+</td>
+<td> Natalie (from Expo2008) 
+</td>
+<td>2018
+</td></tr>
+
+<tr>
+<td>
+<span style="border: thin solid black; padding: 0.3ex 0.5em; color:black; background:#FFA500;">Orange</span>,
+<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>
+</span>
+</td>
+<td> Ryan Boultbee (NUCC)
+</td>
+<td>2018
+</td></tr>
+</table>
+
+<br>
+
+<table border="1" cellspacing="0" cellpadding="5" align="center">
+<tr>
+<td><b>Colour - 3</b>
+</td>
+<td><b>Name</b>
+</td>
+<td><b>Expo?</b>
+</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>,
+<span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#00f;">Blue</span>, 
+<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>
+earth is thin</td>
+<td>Max Weiser (ULSA) 
+</td>
+<td>2018
+</td></tr>
+<tr>
+<td><span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#00f;">Blue</span>, <span style="border: thin solid black; padding: 0.3ex 0.5em; color:black; background:#fff;">White</span>, <span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#00f;">Blue</span> White is thin
+</td>
+<td>Radost Waszkiewicz
+</td>
+<td>2018
+</td></tr>
+
+<tr>
+<td><span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#000;">Black</span>, <span style="border: thin solid black; padding: 0.3ex 0.5em; color:black; background:#f00;">Red</span>, <span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#000;">Black</span> Red is thin
+</td>
+<td>Paul Fox
+</td>
+<td>2018
+</td></tr><tr>
+<td><span style="border: thin solid black; padding: 0.3ex 0.5em; color:black; background:#ff0;">Yellow</span>, <span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#000;">Black</span>, <span style="border: thin solid black; padding: 0.3ex 0.5em; color:black; background:#ff0;">Yellow</span>
+</td>
+<td>Tom Crossley
+</td>
+<td>2018
+</td></tr>
+<tr>
+<td><span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#0c0;">Green</span>,
+ <span style="border: thin solid black; padding: 0.3ex 0.5em; color:black; background:#f00;">Red</span>,
+<span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#0c0;">Green</span>
+</td>
+<td>Alex Sterling (NUCC) 
+</td>
+<td>2018
+</td></tr>
+<tr>
+<td>
+ <span style="border: thin solid black; padding: 0.3ex 0.5em; color:black; background:#f00;">Red</span>,
+<span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#0c0;">Green</span>,
+<span style="border: thin solid black; padding: 0.3ex 0.5em; color:black; background:#f00;">Red</span>
+</td>
+<td>Alex Sterling (NUCC) 
+</td>
+<td>2018
+</td></tr>
+<tr>
+<td><span style="border: thin solid black; padding: 0.3ex 0.5em; color:black; background:#ff0;">Yellow</span>,
+<span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#00f;">Blue</span>, 
+<span style="border: thin solid black; padding: 0.3ex 0.5em; color:white; background:#0c0;">Green</span>
+</td>
+<td> Jacob Puhalo-Smith (NUCC) 
+</td>
+<td>2018
+</td></tr>
+</table>
+<br>
+<h3>Gear-tape - labelling</h3>
+<p>It is almost essential (for caving generally, but particularly for Expo) to settle
+on a particular combination of colours of electrical insulation tape, and label
+<em>absolutely everything</em> you own with the stuff. The table above shows combinations already taken. 
+
+For other CUCC colour combinations already in use see <a
+href="http://www.srcf.ucam.org/caving/wiki/Gear_Tape_Colours">CUCC gear tape</a>. 
+
+
+<p> Tape
+<em>everything</em>, not just your caving gear; while one karabiner looks much
+like another, it's equally true that one karrimat looks much like
+another. And especially your phone, phone cable, charger, charger-cable, laptop, mouse, mug/plate/cutlery -
+essentially anything you want to be reasonably sure to get back.</p> 
+
+<hr />
+
+
+</ul>
+</body>
+</html>

handbook/getsurvex.html

@@ -1,7 +1,7 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-<title>Handbook placeholder page</title>
+<title>CUCC Expedition Handboo - Survey software</title>
 <link rel="stylesheet" type="text/css" href="../css/main2.css" />
 </head>
 <body>
@@ -30,9 +30,35 @@ convert your sketches into actual plan and elevation presentation-quality survey
 
 <h2>Therion</h2>
 <p>
-<a href="https://therion.speleo.sk/">Therion<a/>
+<a href="https://therion.speleo.sk/">Therion</a>
 
+<h2>GPS stuff</h2>
+<p>GPS is increasingly important for all the surface work.
 
+<p>
+<a href="https://wiki.openstreetmap.org/wiki/GpsPrune">GPS Prune</a> is a vitally useful utility.
+
+<h2>Other old stuff</h2>
+<p>
+<a href="https://code.google.com/archive/p/loch/">Loch</a> This is fork off of Therion's loch program. 
+The goal is to model Cave systems in 3d and have a high degree 
+of interaction between the user and the information. 
+There is currently no working version and is under very heavy development.
+
+<p>
+<a href="https://code.google.com/archive/p/topolinux/">TopoLinux</a> 
+ consists of cave surveying applications for Linux PC and Android devices. 
+TopoDroid is an Open Source Android app to make cave surveys with the DistoX.
+
+<p>
+<a href="https://code.google.com/archive/p/psurvex/">psurvex</a>  
+My task  was to write a new program which could read the data from an external file, 
+ideally one which resembled a .svx file as much as possible.
+Psurvex supports 
+only a subset of the .svx file format but the same file should process in Survex 
+without any problems. You need to write a .svx file and save it somewhere on your machine. 
+This program will then process the file and create a second file containing a list of 
+points for plotting on graph paper and some statistics about your survey. 
 <hr />
 
 

handbook/index.htm

@@ -31,17 +31,26 @@
   <li><a href="paperwork.html">Arrange to come on expo</a> - Things you have to do.</li>
   <li><a href="baseops.html">Learn what I need to do</a> - Base camp operations.</li>
 
+  <li><a href="geartape.html">Label my gear and stuff</a> - the gear-tape colours in use.</li>
   <li><a href="lights.html">Charge my light</a> - at top camp and at base camp.</li><br>
   <li><a href="phone.htm">Send a message to top camp</a> - or base camp.</li><br>
+  <li><a href="logbooks.html">Type up my trip </a> - in the logbook</li>
   <li><a href="uploading.html">Upload my photos</a> - of people, landscape and cave entrances.</li>
   <li><a href="essentials.html">Download GPS data to my device</a> - to find caves and to not get lost.</li>
-  <li><a href="gpxupload.html">Upload GPS data from my phone (or device)</a> -  where I found a new cave.</li><br>
+  <li><a href="gpxupload.html">Upload GPS data from my phone (or device)</a> -  where I found a new cave.</li>
+  <li><a href="survey/newcave.html">Record my new cave discovery</a> -  on paper and online</li>
+<br>
+  <li><a href="survey/status.html">Discover whether my trip notes have been scanned</a> -  what is the current status of all expo cave surveying?</li>
+
+
+
+<br>
   <li><a href="stool.htm">Perform bodily functions up the mountain</a> - on a matter of stooling.</li>
   <li><a href="charging.html">Charge a drill battery up the mountain</a> - cave exploration.</li><br>
   <li><a href="bierbook.html">Record how much beer I've drunk</a> - from the base camp fridge.</li><br>
   <li><a href="paperwork.html#nok">Record who my next of kin is</a> - & emergency medical details.</li><br>
   <li><a href="getsurvex.html">Set up my laptop for looking at cave surveys</a> - Survex, aven etc.</li>
-  <li><a href="nerd.html">Set up my laptop for everything</a> - surveying, website management etc.</li>
+  <li><a href="nerd.html">Set up my laptop for everything</a> - surveying, data management, version control etc.</li>
  </ul>
 
 <h2>Where and How</h2>
@@ -59,14 +68,23 @@
 <dd>Unpredictable in the mountains. Local thunderstoms with rapid run-off are the biggest danger.</dd>
 
 <dt><a href="datamgt.html">Cave data management</a></dt>
-<dd>The biggest surprise for new people on expo are the intense efforts on recording and managing cave data. This tells you why.</dd>
+<dd>The biggest surprise for new people on expo are the intense efforts on recording and 
+managing cave data. This tells you why.<br><br>
+The most basic data we keep is the record of your trip in the logbook and then 
+<a href="logbooks.html">typing that in online</a>.<br><br>
+When you discover and survey a new cave we have <a href="survey/newcave.html">a good process</a> for recording the discovery and the cave data.</dd>
 
-<dt><a href="look4.htm">Prospecting</a></dt>
+<dt><a href="look4.htm">Prospecting Issues </a></dt>
 <dd>The printable  <a href="/prospecting_guide/">new prospecting guide (slow to load)</a> is a list of all known cave entrances and is essential reading before you wander the plateau stumbling across holes of potential interest. <br><br>
-Do now read <a href="look4.htm">how to do plateau prospecting</a>.<br><br>
-Vast amounts of work have been wasted in the past through inadequate recording. It isn't very much extra work, 	but ensures that your hard work gains some recognition in the future rather than making lots of tedious work and the cursing of your name... <br><br>
-There is also a graphical <a href="prospecting_guide_short.html">prospecting map guide</a> which shows the caves and cave entrances we know about (This is currently broken in that it is not showing a map background so is rather incomprehensible unless you already know the plateau quite well.)<br><br>
-There is a separate page with pictures of surface landmarks for <a href="findit.htm">taking bearings</a>, and a new guide to getting a <a href="survey/gps.htm">GPS fix</a>.</dd>
+Do now read <a href="look4.htm">plateau prospecting: issues and explanations</a>.<br><br>
+Vast amounts of work have been wasted in the past through inadequate recording. It isn't very much extra work, 	
+but ensures that your hard work gains some recognition in the future rather than making lots of tedious work 
+and the cursing of your name... <br><br>
+There is also a graphical <a href="prospecting_guide_short.html">prospecting map guide</a> which shows 
+the caves and cave entrances we know about (This is currently broken in that it is not showing 
+a map background so is rather incomprehensible unless you already know the plateau quite well.)<br><br>
+There is a separate page with pictures of surface landmarks for <a href="findit.htm">
+taking bearings</a>, and a new guide to getting a <a href="survey/gps.htm">GPS fix</a>.</dd>
 
 <dt><a href="survey/index.htm">Surveying</a></dt>
 <dd>Once the cave starts to get significant (ie. anything which requires getting changed or rigging), it needs good documentation. This is mostly a matter of <br><br>
@@ -97,8 +115,16 @@ The first time you go to explore a poorly documented question mark ("QM"), you
 
 <dt><a href="photo.htm">Photography </a></dt>
 <dd>- embryonic photography handbook.</dd>
-<dt><a href="rigit.htm">SRT Rigging</a></dt> <dd>This one's also minimal &ndash; but links to useful info on another site. 	There is (Jan 2000), however, in addition to the rudimentary page above, a few 	pages towards a full Austria-specific guide. The <a href="rig/index.htm">contents page</a> links to an <a href="rig/intro.htm">Introduction</a> and a useful section on <a href="rig/boltin.htm">placing bolts</a> and it may be useful to refer to the 	expedition <a href="../fixaid.htm">Fixed Aids</a> list to see what gear has 	been left in place from previous years. See also Sherry's <a href="http://www.cavepage.magna.com.au/cave/SRTrig.html">Alpine Rigging guide</a> (beta release)</li> <!--<br>... of which there may be a <a href="handbook/3rdparty/sherry/srtrig.htm">local copy</a> if you are
-  browsing from disc--></dd>
+<dt><a href="rigit.htm">SRT Rigging</a></dt> <dd>This one's also minimal &ndash; but links to useful info on another site. 	
+There is (Jan 2000), however, in addition to the rudimentary page above, a few 	pages towards a full 
+Austria-specific guide. The <a href="rig/index.htm">contents page</a> links to an <a href="rig/intro.htm">Introduction</a> 
+and a useful section on <a href="rig/boltin.htm">placing bolts</a> and it may be useful to refer to the 	
+expedition <a href="../fixaid.htm">Fixed Aids</a> list to see what gear has 	been left in place from 
+previous years. See also Sherry's <a href="http://www.cavepage.magna.com.au/cave/SRTrig.html">Alpine Rigging guide</a>
+ (beta release)</li> 
+<!--... of which there may be a <a href="handbook/3rdparty/sherry/srtrig.htm">local copy</a> if you are
+  browsing from disc-->
+</dd>
 
 <dt><a href="vocab.htm">Useful vocabulary</a></dt>
 <dd>This is hardly a "section", but contains a possibly useful table of 	translations of climbing (mainly) and caving (some) terms into German, Spanish 	and French. It's here mainly because I had the material to hand and it would be 	silly not to make it available.</dd> 
@@ -112,14 +138,19 @@ The first time you go to explore a poorly documented question mark ("QM"), you
 
 </dl> 
 <hr />
-<h2>Computing stuff</h2>
+<h2>Computing and data stuff</h2>
 <dl>
 <dt><a href="computer.html">Expo Computer</a></dt>
 <dd>Details on how the expo computer and network is set up and administered.</dd>
 
+<dt><a href="exposerver.html">Expo Server</a></dt>
+<dd>The current location of the expo server which holds the master archives and
+serves the web pages.</dd>
 
-<dt><a href="update.htm">Website and Data Manual - Experts only</a></dt>
-<dd>This tells you how the website and cave data are arranged, accessed and used, including entering new cave data.</dd>
+
+<dt><a href="update.htm">Online Systems and Data  - Manual</a></dt>
+<dd>This reminds the expert administrator nerds how the cave survey data, trip reports, rigging guides, 
+handbook pages and cave guidebook descriptions are arranged, accessed and updated.</dd>
 
 </dl>
 

handbook/kitlist.html

@@ -13,22 +13,27 @@ the simplistic approach, and no responsibility is accepted for errors or
 omissions ;-) Make sure you have at least the Essentials; consider taking the
 Extras for a more pleasant time, but don't fret if you can't get them.  The
 Excessive sections are for the gearists...</p>
-
-<p>It's a good idea (for caving generally, but particularly for Expo) to settle
-on a particular combination of colours of electrical insulation tape, and label
-absolutely everything you own with the stuff. To see which combinations are
-available, have a look <a
-href="http://www.srcf.ucam.org/caving/wiki/Gear_Tape_Colours">here</a>.  Tape
-<em>everything</em>, not just your caving gear; while one karabiner looks much
-like another, it's equally true that one karrimat looks much like
-another. (And your phone/chargers/laptop/mug/plate/cutlery -
-essentially anything you want to be reasonably sure to get back)</p> 
-
 <p>Lightweight stuff is good so as it makes carrying all your caving and camping 
 gear to top camp significantly less epic/tedious. Two of everything
 (pit, karrimat, utensils, clothes) reduces the amount of stuff you have 
 to keep carrying up and down the mountain.</p>
 
+<h3>Gear-tape - labelling</h3>
+<p>It is almost essential (for caving generally, but particularly for Expo) to settle
+on a particular combination of colours of electrical insulation tape, and label
+<em>absolutely everything</em> you own with the stuff. To see which combinations are
+available, have a look those already used at <a href="geartape.html">2018 gear tape colours</a>. 
+
+(For other CUCC colour combinations in use see <a
+href="http://www.srcf.ucam.org/caving/wiki/Gear_Tape_Colours">CUCC gear tape</a>). 
+<p> Tape
+<em>everything</em>, not just your caving gear; while one karabiner looks much
+like another, it's equally true that one karrimat looks much like
+another. And especially your phone, phone cable, charger, charger-cable, laptop, mouse, mug/plate/cutlery -
+essentially anything you want to be reasonably sure to get back.</p> 
+
+
+
 <h3>Clothes</h3>
 
 <p>Expo can be hot, cold, wet or dry, or (more usually) all of
@@ -73,7 +78,7 @@ these in rapid succession and combination! It can be really chilly
   <li>Head torch.</li>
   <li>Mug, spoon, mess tin for bivi</li>
   <li>Batteries and/or charger for above.</li>
-  <li>Bivi Bag - the bivi can be quite drippy (and cold).</li>
+  <li>Bivi Bag - breathable - the bivi can be quite drippy (and cold).</li>
  </ul></li>
  <li>Extras
  <ul>
@@ -163,7 +168,7 @@ these in rapid succession and combination! It can be really chilly
   <li>Flannel &amp; towel.</li>
   <li>Glasses &amp; spares if you need them.</li>
   <li>Contact lenses - get enough daily use-once ones. The upper caves are very dusty.</li>
-  <li>Bivvy bag - emergency shelter anywhere. The plateau can become
+  <li>Bivvy bag (very lightweight, non-breathable) - emergency shelter anywhere. The plateau can become
 	unfriendly very quickly. Erin and Earl had to resort to bivvy bags when
 	caught by a storm on the Hinter in 1999. You could use the one from
 	your caving gear, or get a proper camping one too. (Warning - fancy ones can be
@@ -201,7 +206,7 @@ one as two get in the way on the scrambly bits. </li>
 </ul>
 
 <p><em>Original by Earl Merson (1999); edited and updated David
-Loeffler (2003), Edvin, Duncan, OllyM (2008) and Wookey (2014)</em></p>
+Loeffler (2003), Edvin, Duncan, OllyM (2008) and Wookey (2014) and Philip (2018)</em></p>
 <hr />
 
 </body>

handbook/leader.htm

@@ -108,6 +108,14 @@ jeapordises the whole expedition.</note>
 <dd>Deadline: <strong>last day of Feb</strong>. <a
 href="http://www.apps.gharparau.org.uk/login">Applications are done
 online</a>.</dd>
+
+
+<dt>Check expo VfH&Ouml; members are paying subscriptions</dt>
+<dd>Deadline: end of <strong>December</strong>. In 2018 we had 9 people paying &euro;30 to 
+be <a href="paperwork.html#insurance">members of this local cave club</a>. This is for very basic underground insurance cover.
+This is life membership with annual renewal, so an additional &euro;30 each is due in January. If this is not paid by the individual then
+expo will almost certainly have to pay it to maintain goodwill.So in early December these people need to decide if they want to cancel
+their membership and do that by the end of December.</dd>
 </dl>
 
 <h4>General Preparation</h4>

handbook/logbooks.html

@@ -6,15 +6,59 @@
 <body>
 <h2 id="tophead">CUCC Expedition Handbook</h2>
 <h1>Logbooks</h1>
-<p>As soon as possible after a trip finishes, a hand-written write-up of the trip is made in the nearest logbook: 
+<p>As soon as possible after a trip finishes, a <b>hand-written write-up</b> of the trip is made in the nearest logbook: 
 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.
+
+<p>If you are at basecamp, then it is an excellent idea to 
+<b>type your logbook trip report</b> instead of writing it by hand - see <a href=#type">below</a>.
+
+
+<p>The contents of both the topcamp logbook and the basecamp logbook are typed into the same  
+"logbook.html" file for archiving. The drawings are scanned and stored in the same place, and hand-edited
+into the logbook.html file after expo finished.
+
+<p>If this is all new to you, please now read <a href="datamgt.html">Cave data management</a>, 
+and <a href="survey/why.htm">why we make surveys</a> and then the 
+<a href="survey/index.htm">Survey Handbook</a>
+
+<h3 =id="type">Typing just your trip report</h3>
+<p>If you are at basecamp, then it is an excellent idea to type up your logbook trip report.
+You can then print this and stick it in the logbook, adding any sketches by hand. 
+This will save someone (probably you) deciphering your handwriting and typing it up later.
+
+<p>These instructions assume that (a) you are sitting at the <em>expo laptop</em> and that someone who knows 
+the password has logged in for you (as user "expo"), and (b) that you know nothing about the software
+systems used by expo.
+<ul>
+<li>You will type your trip report as plain text using a text editor.
+<li>You will be typing into a file called something like "logbook-mynewtrip.txt" in the folder "Downloads"
+<li>You will be asking someone nerdy to take this trip report and to edit it into the proper place later.
+</ul>
+
+<p>The first challenge is to find how to start up the text editor. The <em>expo laptop</em> is running debian Linux
+with the Gnome 3.2 desktop manager, so click on "Activities" in the top left corner. 
+This will bring down a vertical menu of icons down the left hand side of the screen. Hovering 
+over the icons brings up a label, and the one you want is at (or near) the bottom with the label "Text editor". Click on it.
+<p>If you are lucky this will bring up an empty window for a new file. 
+<br>If you are unlucky it will bring up the previous person's file.
+<p>If it is a new file, save it to the Downloads folder (/home/expo/Downloads) using the "File->Save" menu 
+item and give it a sensible name such as "logbook-mynewtrip.txt".
+<p>If it was someone else's file, save it using the "File->Save" menu. Then close the text editor ("File->Close"). 
+Then start it up again from the vertical icon menu as before.
+<p>Now type in your trip report using whatever format you like, but please leave a blank line between paragraphs.
+
+
+<h3>Adding your trip to the logbook online file</h3>
 <p>If you are using the <em>expo laptop</em> just edit this file:
 <pre>
 /home/expoweb/years/2018/logbook.html
 </pre>
+copy the format you can see other people have used; 
 and other people will take care of synchronising it with the version control system.
 
 <p>
@@ -22,13 +66,26 @@ 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 e.g. "logbook-mynewtrip.txt", 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>
 
+<h3>Recommended procedure</a></h3>
+<p>
+Rather than editing logbook.html when you type up your trip, it is a much better 
+idea to type up your trip(s) in a separate file, e.g. "logbook-mynewtrip.txt", and store it in the same 
+place on the <em>expo laptop</em>, i.e.
+<pre>
+/home/expoweb/years/2018/
+</pre>
+<p>or email it to a nerd if you are sitting at a different laptop.
+
 <h3>Format of the online logbooks</a></h3>
 
 
@@ -41,7 +98,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>

handbook/look4.htm

@@ -3,13 +3,13 @@
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
 <title>
-CUCC Expo Prospecting Handbook
+CUCC Expo Prospecting Handbook Issues
 </title>
 <link rel="stylesheet" type="text/css" href="../css/main2.css" />
 </head>
 <body>
 <h2 id="tophead">CUCC Expedition Handbook</h2>
-<h1>Prospecting</h1>
+<h1>Prospecting - issues</h1>
 
 <p>Much of the area of the Loser Augst-Eck plateau is rough limestone
 pavement (<b>karren</b>), liberally covered with dense areas of dwarf pine,

handbook/manual.html

@@ -0,0 +1,322 @@
+<html>
+<head>
+<title>CUCC Expedition Handbook: Online system manual</title>
+<link rel="stylesheet" type="text/css" href="../css/main2.css" />
+</head>
+<body>
+<h2 id="tophead">CUCC Expedition Handbook - Online systems</h2>
+<h1>Expo Online Systems Manual</h1>
+
+<h2><a id="manual">Expo data management systems manual</a></h2>
+
+<p>Editing the expo data management system is an adventure. Until 2007, there was no
+guide which explained the whole thing as a functioning system. Learning
+it by trial and error is non-trivial. There are lots of things we
+could improve about the system, and anyone with some computer nous is
+very welcome to muck in. It is slowly getting better organised.</p>
+
+<p>This manual is organized in a how-to sort of style. The categories,
+rather than referring to specific elements of the data management system, refer to
+processes that a maintainer would want to do.</p>
+<p>Note that to display the survey data you will need a copy of the survex software.
+
+<h3>Contents</h3>
+
+<ol>
+<li><a href="#usernamepassword">Getting a username and password</a></li>
+<li><a href="#repositories">The repositories</a></li>
+<li><a href="#howitworks">How the data management system works</a></li>
+<li><a href="#quickstart">Quick start</a></li>
+<li><a href="#editingthedata management system">Editing the data management system</a></li>
+<li><a href="#Mercurialinwindows">Using version control software in Windows</a></li>
+<li><a href="#expowebupdate">The expoweb-update script</a></li>
+<li><a href="#cavepages">Updating cave pages</a></li>
+<li><a href="#updatingyears">Updating expo year pages</a></li>
+<li><a href="logbooks.html">Adding typed logbooks</a></li>
+<li><a href="uploading.html">Uploading photos</a></li>
+<li><a href="#tickingoff">Ticking off QMs</a></li>
+<li><a href="#surveystatus">Maintaining the survey status table</a></li>
+<li><a href="#automation">Automation</a></li>
+<li><a href="#arch">Archived updates</a></li>
+</ol>
+Appendices:
+<ul>
+<li><a href="data management system-history.html">History of the data management system</a></li>
+</ul>
+
+<h3><a id="usernamepassword">Getting a username and password</a></h3>
+
+<p>Use these credentials for access to the site. The user is 'expo',
+  with a cavey:beery password. Ask someone if this isn't enough clue for you.
+  <b>This password is important for security</b>. The whole site <strong>will</strong> get hacked by spammers or worse if you are not careful with it. Use a secure method for passing it on to others that need to know (i.e not unencrypted email), don't publish it anywhere, don't check it in to the data management system by accident. A lot of people use it and changing it is a pain for everyone so do take a bit of care.
+</p>
+
+<p>Note that you don't need a password to view most things, but you will need one to change them</p>
+
+<h3><a id="repositories">The repositories</a></h3>
+
+<p>All the expo data is contained in 4 "repositories" at
+expo.survex.com. This is currently hosted on a server at the university. We use a distributed version control system (DVCS) to manage these repositories because this allows simultaneous collaborative editing and keeps track of all changes so we can roll back and have branches if needed.</p>
+
+<p>The site has been split into four parts:</p>
+
+<ul>
+ <li><a href="http://expo.survex.com/repositories/home/expo/expoweb/graph">expoweb</a> - the data management system itself, including generation scripts</li>
+ <li><a href="http://expo.survex.com/repositories/home/expo/troggle/graph/">troggle</a> - the database-driven part of the data management system</li>
+ <li><a href="http://expo.survex.com/repositories/home/expo/loser/graph/">loser</a> - the survex survey data</li>
+ <li><a href="http://expo.survex.com/repositories/home/expo/tunneldata/graph/">tunneldata</a> - the tunnel (and therion) data and drawings</li>
+</ul>
+
+
+<p>All the scans, photos, presentations, fat documents and videos are
+stored just as files (not in version control) in 'expofiles'. See
+below for details on that.</p>
+
+<h3><a id="howitworks">How the data management system works</a></h3>
+
+<p>Part of the data management system is static HTML, but quite a lot is generated by scripts. So anything you check in which affects cave data or descriptions won't appear on the site until the data management system update scripts are run. This happens automatically every 30 mins, but you can also kick off a manual update. See 'The expoweb-update script' below for details.</p>
+
+<p>Also note that the data management system you see is its own Mercurial checkout (just like your local one) so that has to be 'pulled' from the server before your changes are reflected.</p>
+
+<h3><a id="editthispage">Using 'Edit This Page'</a></h3>
+<p>This edits the file served by the webserver  on
+the expo server in Cambridge but it does not update the copy of the file in the
+repository in expo.survex.com. To properly finish the job you need to
+<ul>
+<li>
+ssh into expo@expo.survex.com (use putty on a Windows machine) 
+<li>cd to the directory containing the repo you want, i.e. "cd loser" for
+cave data or "cd expoweb" for the handbook and visible data management system, which takes you to /home/expo/expoweb 
+<li>Then run "hg status" (to check what
+changes are pending), 
+<li>then "hg diff" to see the changes in detail 
+(or "hg diff|less" if you know how to use "less" or "more") and 
+<li>then DO NOT just run 'hg commit' unless you know how emacs works as it will dump 
+you into an emacs editing window (C-x C-C is the way to exit emacs). Instead, do 
+'hg commit -m "found files left over - myName" '
+which submits the obligatory comment witht he commit operation.
+</ul>
+
+
+<h3><a id="quickstart">Quick start</a></h3>
+
+<p>If you know what you are doing here is the basic info on what's where:<br>
+(if you don't know what you're doing, skip to <a href="#editingthedata management system">Editing the data management system</a> below.)
+
+
+<dl>
+    <dt>expoweb (The data management system)</dt>
+    <dd>
+      <tt>hg clone ssh://expo@expo.survex.com/expoweb</tt> (read/write)<br />
+      <tt>hg clone http://expo.survex.com/repositories/home/expo/expoweb/</tt> (read-only checkout)
+    </dd>
+
+    <dt>troggle (The data management system backend)</dt>
+    <dd>
+      <tt>hg clone ssh://expo@expo.survex.com/troggle</tt> (read/write)<br />
+      <tt>hg clone http://expo.survex.com/repositories/home/expo/troggle/</tt> (read-only checkout)
+    </dd>
+
+    <dt>loser (The survey data)</dt>
+    <dd>
+      <tt>hg clone ssh://expo@expo.survex.com/loser</tt> (read/write)<br />
+      <tt>hg clone http://expo.survex.com/repositories/home/expo/loser/</tt> (read-only)
+    </dd>
+
+    <dt>tunneldata (The Tunnel drawings)</dt>
+    <dd>
+      <tt>hg clone ssh://expo@expo.survex.com/tunneldata</tt> (read/write)<br />
+      <tt>hg clone http://expo.survex.com/repositories/home/expo/expoweb/</tt> (read-only)
+    </dd>
+</dl>
+<dl>
+    <dt>expofiles (all the big files and documents)</dt>
+
+<p>Photos, scans (logbooks, drawn-up cave segments) (This was about
+60GB of stuff in 2017 which you probably don't actually need locally).
+<p>If you don't need an entire copy of all 60GB, then it is probably best to use Filezilla to copy just a small part of the filesystem to your own machine and to upload the bits you add to or edit.
+Instructions for installing and using Filezilla are found in the expo user instructions for uploading photographs: <a href="uploading.html">uploading.html</a>.
+
+<p> To sync all
+the files from the server to local expofiles directory:</p>
+
+<p><tt>rsync -av expo@expo.survex.com:expofiles /home/expo</tt></p>
+
+<p>To sync the local expofiles directory back to the server (but only if your machine runs Linux):</p>
+<p><tt>rsync --dry-run --delete-after -a /home/expo/expofiles expo@expo.survex.com</tt></p>
+then CHECK that the list of files it produces matches the ones you absolutely intend to delete forever! ONLY THEN do:
+<p><tt>rsync -av /home/expo/expofiles expo@expo.survex.com:</tt></p>
+
+<p>(do be <b>incredibly</b> careful not to delete piles of stuff then rsync back, or to get the directory level of the command wrong - as it'll all get deleted on the server too, and we may not have backups!). It's <b>absolutely vital</b>Use rsync --dry-run --delete-after -a first to check what would be deleted. 
+
+<p>If you are using rsync from a Windows machine you will <em>not</em> get all the files as some filenames are incompatible with Windows. What will happen is that rsync will invisibly change the names as it downloads them from the Linux expo server to your Windows machine, but then it forgets what it has done and tries to re-upload all the renamed files to the server even if you have touched none of them. Now there won't be any problems with simple filenames using all lowercase letters and no funny characters, but we have nothing in place to stop anyone creating such a filename somewhere in that 60GB or of detecting the problem at the time. So don't do it. If you have a Windows machine use Filezilla not rsync.
+
+<p>(We may also have an issue with rsync not using the appropriate user:group  attributes for files pushed back to the server. This may not cause any problems, but watch out for it.)</p>
+</dl>
+<h3><a id="editingthedata management system">Editing the data management system</a></h3>
+
+<p>To edit the data management system fully, you need to use the disributed version control system (DVCM) software which is currently mercurial/TortoiseHg. Some (static text) pages can be edited directly on-line using the 'edit this page link' which you'll see if you are logged into troggle. In general the dynamically-generated pages, such as those describing caves which are generated from the cave survey data, can not be edited in this way, but forms are provided for some types of these like 'caves'.</p>
+
+<p>What follows is for Linux. If you are running Windows then see below <a href="#Mercurialinwindows">Using Mercurial/TortoiseHg in Windows</a>.
+
+<p>Mercurial can be used from the command line, but if you prefer a GUI, TourtoiseHg is highly recommended on all OSes.</p>
+
+<p>Linux: Install mercurial and tortoisehg-nautilus from synaptic,
+then restart nautilus <tt>nautilus -q</tt>. If it works, you'll be able to see the menus of tortoise within your Nautilus windows. </p>
+
+<p>Once you've downloaded and installed a client, the first step is to create what is called a checkout of the data management system. This creates a copy on your machine which you can edit to your heart's content. The command to initially check out ('clone') the entire expo data management system is:</p>
+
+<p><tt>hg clone ssh://expo@expo.survex.com/expoweb</tt></p>
+
+<p>for subsequent updates</p>
+
+<p><tt>hg update</tt></p>
+
+<p>will generally do the trick.</p>
+
+<p>In TortoiseHg, merely right-click on a folder you want to check out to, choose "Mercurial checkout," and enter</p>
+
+<p><tt>ssh://expo@expo.survex.com/expoweb</tt></p>
+
+<p>After you've made a change, commit it to you local copy with:</p>
+
+<p><tt>hg commit</tt>   (you can specify filenames to be specific)</p>
+
+<p>or right clicking on the folder and going to commit in TortoiseHg. Mercurial can't always work out who you are. If you see a message like "abort: no username supplied" it was probably not set up to deduce that from your environment. It's easiest to give it the info in a config file at ~/.hgrc (create it if it doesn't exist, or add these lines if it already does) containing something like</p>
+
+<p><tt>
+[ui]<br/>username = Firstname Lastname &lt;myemail@example.com&gt;
+</tt></p>
+
+<p>The commit has stored the changes in your local Mercurial DVCS, but it has not sent anything back to the server. To do that you need to:</p>
+
+<p><tt>hg push</tt></p>
+
+<p>Before pushing, you should do an <tt>hg pull</tt> to sync with upstream first. If someone else has edited the same files you may also need to do:</p>
+
+<p><tt>hg merge</tt></p>
+
+<p>(and sort out any conflicts if you've both edited the same file) before pushing again</p>
+
+<p>Simple changes to static files will take effect immediately, but changes to dynamically-generated files (cave descriptions, QM lists etc) will not take effect, until the server runs the expoweb-update script.</p>
+
+
+
+
+<h3><a id="Mercurialinwindows">Using Mercurial/TortoiseHg in Windows</a></h3>
+
+<p>Read the instructions for setting up TortoiseHG in <a href="tortoise/tortoise-win.htm">Tortoise-on-Windows</a>.
+<p>In Windows: install Mercurial and TortoiseHg of the relevant flavour from <a href="https://tortoisehg.bitbucket.io/">https://tortoisehg.bitbucket.io/</a> (ignoring antivirus/Windows warnings). This will install a submenu in your Programs menu)</p>
+
+<p>To start cloning a repository: first create the folders you need for the repositories you are going to use, e.g. D:\CUCC-Expo\loser and D:\CUCC-Expo\expoweb. Then start TortoiseHg Workbench from your Programs menu, click File -> Clone repository, a dialogue box will appear. In the Source box type</p>
+
+<p><tt>ssh://expo@expo.survex.com/expoweb</tt></p>
+
+<p>for expoweb (or similar for the other repositories). In the Destination box type whatever destination you want your local copies to live in on your laptop e.g. D:\CUCC-Expo\expoweb. Hit Clone, and it should hopefully prompt you for the usual beery password.
+
+<p>The first time you do this it will probably not work as it does not recognise the server. Fix this by running putty (downloading it from <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/">https://www.chiark.greenend.org.uk/~sgtatham/putty/</a>), and connecting to the server 'expo@expo.survex.com' (on port 22). Confirm that this is the right server. If you succeed in getting a shell prompt then ssh connection are working and TortoiseHg should be able to clone the repo, and send changes back.</p>
+
+
+<h3><a id="expowebupdate">The expoweb-update script</a></h3>
+
+<p>The script at the heart of the data management system update mechanism is a makefile that runs the various generation scripts. It is run every 15 minutes as a cron job (at 0,15,30 and 45 past the hour), but if you want to force an update more quickly you can run it he</p>
+
+<p>The scripts are generally under the 'noinfo' section of the site just because that has (had) some access control. This will get changed to something more sensible at some point</p>
+
+
+<h3><a id="cavepages">Updating cave pages</a></h3>
+
+<p>Cave description pages are automatically generated from a set of
+cave files in noinfo/cave_data/ and noinfo/entrance_data/. These files
+are named <area>-<cavenumber>.html (where area is 1623 or 1626). These
+files are processed by troggle. Use <tt>python databaseReset.py
+caves</tt> in /expofiles/troggle/ to update the site/database after
+editing these files.</p>
+
+<p>Clicking on 'New cave' (at the bottom of the cave index) lets you enter a new cave. <a href="caveentry.html">Info on how to enter new caves has been split into its own page</a>.</p>
+
+<p>(If you remember something about CAVETAB2.CSV for editing caves, that was 
+superseded in 2012).</p>
+<p>This may be a useful reminder of what is in a survex file <a href="survey/how_to_make_a_survex_file.pdf">how to create a survex file</a>.
+
+<h3><a id="updatingyears">Updating expo year pages</a></h3>
+
+<p>Each year's expo has a documentation index which is in the folder</p>
+
+<p>/expoweb/years</tt></p>
+
+<p>, so to checkout the 2011 page, for example, you would use</p>
+
+<p>hg clone ssh://expo@expo.survex.com/expoweb/years/2011</tt></p>
+
+<p> Once you have pushed your changes to the repository you need to update the server's local copies, by ssh into the server and running hg update in the expoweb folder. </p>
+
+<h3>Adding a new year</h3>
+<p>Edit noinfo/folk.csv, adding the new year to the end of the header
+line, a new column, with just a comma (blank
+cell) for people who weren't there, a 1 for people who were there, and
+a -1 for people who were there but didn't go caving. Add new lines for
+new people, with the right number of columns.</p>
+
+<p>This proces is tedious and error-prone and ripe for improvement.
+Adding a list of people, fro the bier book, and their aliases would be
+a lot better, but some way to make sure that names match with previous
+years would be
+good.</p>
+
+<h3><a id="tickingoff">Ticking off QMs</a></h3>
+
+<p>To be written.</p>
+
+
+<h3><a id="surveystatus">Maintaining the survey status table</a></h3>
+
+<p>There is a table in the survey book which has a list of all the surveys and whether or not they have been drawn up, and some other info.</p>
+
+<p>This is generated by the script tablizebyname-csv.pl from the input file Surveys.csv</p>
+
+
+<h3 id="automation">Automation on expo.survex.com</h3>
+
+<p>Ths section is entirely out of date (June 2014), and awaiting deletion or removal</p>.
+
+<p>The way things normally work, python or perl scripts turn CSV input into HTML for the data management system. Note that:</p>
+<p>The CSV files are actually tab-separated, not comma-separated despite the extension.</p>
+<p>The scripts can be very picky and editing the CSVs with microsoft excel has broken them in the past- not sure if this is still the case.</p>
+<p>Overview of the automagical scripts on the expo data management system</p>
+[Clearly very out of date is it is assuming the version control is svn whereas we changed to hg years ago.]
+<pre>
+Script location 	Input file 	Output file 	Purpose
+/svn/trunk/expoweb/noinfo/make-indxal4.pl 	/svn/trunk/expoweb/noinfo/CAVETAB2.CSV 	many 	produces all cave description pages
+/svn/trunk/expoweb/noinfo/make-folklist.py 	/svn/trunk/expoweb/noinfo/folk.csv 	http://expo.survex.com/folk/index.htm 	Table of all expo members
+
+/svn/trunk/surveys/tablize-csv.pl /svn/trunk/surveys/tablizebyname-csv.pl
+	/svn/trunk/surveys/Surveys.csv 	
+
+http://expo.survex.com/expo/surveys/surveytable.html http://expo.survex.com/surveys/surtabnam.html
+	Survey status page: "wall of shame" to keep track of who still needs to draw which surveys
+
+</pre>
+
+<h3><a id="arch">Archived updates</a></h3>
+<p>Since 2008 we have been keeping detailed records of all data management system updates in the version control system. 
+Before then we manually maintained <a href="../update.htm">a list of updates</a> which are now only of historical interest.
+
+<h2>The data management system conventions bit</h2>
+ <p>This is likely to change with structural change to the site, with style changes which we expect to implement and with the method by which the info is actually stored and served up.</p>
+<p>... and it's not written yet, either :-)</p>
+<ul>
+
+<li>Structure</li>
+<li>Info for each cave &ndash; automatically generated by <tt>make-indxal4.pl</tt></li>
+<li>Contents lists &amp; relative links for multi-article publications like  journals. Complicated by expo articles being in a separate hierarchy from journals.</li>
+<li>Translations</li>
+<li>Other people's work - the noinfo hierarchy.</li>
+<li>Style guide for writing cave descriptions: correct use of boldface (<em>once</em> for each passage name, at the primary definition thereof; other uses of the name should be links to this, and certainly should not be bold.) </li>
+</ul>
+
+
+<hr />
+</body>
+</html>
+

handbook/paperwork.html

@@ -48,6 +48,7 @@ adequate reimbursement of costs incurred in coping with accident (clothing cut o
 The policy option you need for Snowcard is 
 <a href="https://www.snowcard.co.uk/activity-levels/max-adventure">"Max Adventure"</a> 
 which covers original cave exploration in an area which has "organised local cave rescue".
+<p>Snowcard insurance is not available for people who are not &quot;normally resident&quot; in the UK. Attempts to find equivalent schemes for other countries have not proved successful. If this applies to you, you may wish to consider joining the local Austrian cave club (see below). 
 <p>It is very difficult to find out whether any insurance policy actually covers expedition caving or not. 
 Some have complete 
 exclusions for, say "potholing and climbing which normally requires guides or ropes", some are less explicit.
@@ -60,7 +61,7 @@ from here
 and needs to be emailed to <em>hoehle (at) tele2.at </em> which goes to Robert TWC (The Wonder Caver). 
 
 <p>Cost of VfH&Ouml; membership is &euro;30 per year. There are details of how to do the bank transfer on their website
-but generally Robert turns up at the dinner and cash is handed over. But do not let this informality mislead you: a renewal fee may be due every year thereafter and the expo may be responsible. This is why you need to understand the implications of using this mechanism to get insurance and get agreement from the expedition.
+but generally Robert turns up at the dinner and cash is handed over. But do not let this informality mislead you: a renewal fee will be due every year thereafter and the expo may be responsible. To avoid this, you need to explicitly cancel your membership in writing before the end of the calendar year - email to the address above will suffice. This is why you need to understand the implications of using this mechanism to get insurance and get agreement from the expedition.
 <em>
 <div style="margin-left:30px">
 <p>

handbook/rope_history.html

@@ -11,7 +11,33 @@
 </tr>
 </theader>
 <tbody>
-
+<tr>
+<td class="year">2018</td>
+<td class="manafacturer">Corde Courante</td>
+<td class="type">9mm Equirial</td>
+<td class="docs"><a href="rope/notice_generale_cordes_courant_downloaded_22_07_16.pdf">General notice</a></td>
+<td class="desc">green with 3 black strips</td>
+<td class="droptest">To be tested 2021</td>
+<td class="retiretment">Post expo 2028</td>
+</tr>
+<tr>
+<td class="year">2018</td>
+<td class="manafacturer">Teufelberger</td>
+<td class="type">9mm Patron</td>
+<td class="docs"><a href="https://www.teufelberger.com/pub/media/contentmanager/content/downloads/2018-06_6800501_Kernmantelseile_WEB.pdf">General notice</a></td>
+<td class="desc">blue orange (UK Caving Donation)</td>
+<td class="droptest">To be tested 2021</td>
+<td class="retiretment">Post expo 2028</td>
+</tr>
+<tr>
+<td class="year">2017</td>
+<td class="manafacturer">Teufelberger</td>
+<td class="type">9mm Patron</td>
+<td class="docs"><a href="https://www.teufelberger.com/pub/media/contentmanager/content/downloads/2018-06_6800501_Kernmantelseile_WEB.pdf">General notice</a></td>
+<td class="desc">blue black blue (UK Caving Donation)</td>
+<td class="droptest">To be tested 2020</td>
+<td class="retiretment">Post expo 2027</td>
+</tr>
 <tr>
 <td class="year">2016</td>
 <td class="manafacturer">Corde Courante</td>
@@ -76,4 +102,4 @@
 <td class="retiretment">Post expo 2020</td>
 </tr>
 </tbody>
-</table></body></html>
+</table></body></html>

handbook/survey/athome.htm

@@ -11,47 +11,61 @@
 <h1>In the UK</h1>
 
 <p>In an ideal world, we would have a beautifully drawn up survey and
-detailed guidebook descriptions of everything ready to show at the BCRA
-conference (mid-September). Although we are getting better, it is in fact a
-struggle to get these before next expedition ! Life is made particularly
+detailed guidebook descriptions of everything ready to show at the 
+<a href="https://www.hidden.earth/">
+Hidden Earth</a>
+conference (September). Although we are getting better, it is in fact a
+struggle to get these before next expedition. Life is made particularly
 difficult when bits of data and description arrive in dribs and drabs,
 meaning a lot of piecemeal updating. By the time the majority of expo members
 are back in Cambridge, it is at least two months since the return home, all
 urgency has been lost and memories have faded. To avoid this, <b>think</b>:</p>
 
-<p>Did you have to leave Austria without finishing your sketching ? Use the
-post or visit Cambridge! Get hold of a centre line and draw up your survey
+<p style="margin-left:20px">Did you have to leave Austria without finishing your sketching ? Use the
+post or visit Cambridge! Get hold of a centre line (ask someone if you don't know how) and draw up your survey
 as soon as possible - don't leave it to the start of next term when your
 memory will have faded. Some entirely nonsensical surveys <!-- the top of Kiwi
 Suit in the 2002 drawn up survey --> have been produced by surveys being drawn
 up by people other than the original explorers, in the pub, several months
 later</p>
 
-<p>Have you written a passage description ? If not, do it when you get home.
+<p style="margin-left:20px">Have you written a passage description ? If not, do it when you get home.
 If you can type it, so much the better, email it to any or preferably all of 
-Martin Green <b>&lt;mjg54&gt; at cam.ac.uk</b>, Mark Shinwell <b>&lt;mrs30&gt; at cam.ac.uk</b>,
-David Loeffler <b>&lt;dl267&gt; at cam.ac.uk</b>, Wookey <b>&lt;wookey&gt; at aleph1.co.uk</b> and 
-anyone else relevant.
-Failing that, send a disc to one of the above people (someone with email, at
-least) or whoever is in Cambridge doing the drawing up. If you have to write it
-on paper, photocopy it, send a copy to whoever has the survey book (to glue in)
-and to someone else who will take the trouble to type it up and circulate it.</p>
+Mark Shinwell <b>&lt;mshinwell&gt; at Gmail</b>, Philip Sargent <b>&lt;p.m.sargent.72&gt; at cantab.net</b>
+ Wookey <b>&lt;wookey&gt; at aleph1.co.uk</b> and 
+anyone else relevant or whoever is in Cambridge doing the drawing up. 
 
-<p>Have you got the survey book or the log book ? Photocopy it so there is a
-back up and get copies to other addresses before your house burns down. Get
-copies (or the original) to Andy, Wookey, whoever is doing the drawing up, or
+<br>If you have to write it
+on paper, photocopy it or scan it and post or email it to whoever has the survey book (to glue in)
+and to someone else who will take the trouble to type it up.</p>
+
+<p style="margin-left:20px">Have you got the survey book or a 
+<a href="../logbooks.html">
+logbook</a>? 
+Photocopy it, or phototgraph all the pages with your camera, so there is a
+back up and get copies to other addresses before your house burns down. 
+<br>Check what has already been typed up by looking at the online copy of the
+<a href="../../pubs.htm">published logbooks</a>
+<br>Get
+copies (or the original) to the expo leader or Wookey or whoever is doing the drawing up, or
 anyone who will volunteer to type in the logbook or cave descriptions.</p>
 
-<p>Have you got some good (even recognisable...) photographs ? Offer them
-to whoever is doing the BCRA lecture. Try to get them scanned and send
-jpegs to Andy, or even better, let Andy have 35mm negatives (not the
-prints) or slides to scan - he now has a Nikon scanner which does even
-better than the Photo-CD resolution used for the 1996 images..</p>
+<p style="margin-left:20px">Have you got some good (even recognisable...) photographs ? 
+Offer them to those who are writing blog posts and
+to whoever is doing the Hidden Earth lecture. Upload them using 
+<a href="../uploading.html">these  instructions</a>.
 
-<p>Have you some unique experience or amusing anecdote? Write an article
-for the exCS/CUCC mailing list, for the web site and/or the journal.</p>
+<p style="margin-left:20px">Have you got some GPS tracks on your device which you never did anything with? Upload them using 
+Upload them for future expos using <a href="../gpxupload.html">these  instructions</a>.
 
-<p>Is the only copy of the survey data on your computer ? Get it backed up,
+<p style="margin-left:20px">Have you some unique experience or amusing anecdote? 
+Tweet it <a href="https://twitter.com/CUCC_Expo">@CUCC_Expo</a>, 
+write an article
+for this year's 
+<a href="https://ukcaving.com/board/index.php?topic=23424.0"> UK Caving blog</a>, 
+the Expo or CUCC mailing list, for the web site, or for publishing in a caving magazine.</p>
+
+<p>Is <b>the only copy</b> of any survey data on your computer? Get it backed up,
 preferably including copies to other people involved.  Multiple disc failures
 have caused total loss of the Kaninchenh&ouml;hle dataset once already, and
 backup to another site saves almost infinite grief.</p>
@@ -68,6 +82,10 @@ under it), and update the whole lot so it's consistent with current XHTML
 standards. While you should be revising for your exams. I ought to get 'mug'
 tattooed across my forehead.  DL 2004.04.22. -->
 
+<!-- Well it's 2018 and I have too much time on my hands on expo due to buggered knee,
+and by now my beard is also long. XHTML is history and we are in the sunny uplands
+of HTML5... PhilipS 2018-08-10 -->
+
 <hr />
 
 <ul id="links">

handbook/survey/coord2.html

@@ -0,0 +1,141 @@
+<html>
+<head>
+<title>CUCC Expo Surveying Handbook: GPS coordinate systems</title>
+<link rel="stylesheet" type="text/css" href="../../css/main2.css" />
+</head>
+<body>
+
+<h2 id="tophead">CUCC Expo Surveying Handbook</h2>
+<h1>GPS and coordinate systems</h1>
+
+<h3>Coordinate systems</h3>
+
+<p>It doesn't especially matter what display options are selected when you
+are getting the GPS fix, but it is important to use standard ones when writing
+down the reported position in the survey book. The usual systems are either
+Lat/Long with the WGS84 datum, which all GPSses support out of the box; or
+the Austrian BMN (Bundesmeldnetz) system, which should be relative to the
+Austrian MGI datum (Hermannskogel), which is what we use for our surveys. It
+doesn't matter <i>too</i> much what combination of parameters you actually use
+as long as you record what they were, since we have conversion programs that
+can convert coordinates between the systems; but remember to record <b>which
+grid and which datum</b> your GPS was set for when you copy the fix into the
+survey file. (Besides the risk of introducing severe errors, it is an
+extraordinarily tedious task to have to repeatedly try all the plausible
+combinations of grid and datum that a given set of numbers might be in, convert
+them all to dataset coordinates and see which ones give answers in vaguely the
+right place, which is what someone will have to do if you don't write the
+details down.)</p>
+
+<p>If you want to set up your GPS to use the same coordinates the survey data
+set uses, which makes life a lot easier, then these are the runes to use as a
+"User Grid" if the unit doesn't support BMN coordinates immediately (which
+Garmin ones don't, for example):</p>
+
+<div style="background-color: #BDB">
+<table>
+<tr>
+<th>Ellipsoid:</th><td>Austrian (Bessel 1841)<br />
+a = 63377397.155m (&Delta;A = 739.845)<br />
+1/f = 299.1528128 (&Delta;f x 10,000 = 0.10037428)
+</td></tr>
+<tr>
+<th>Datum:</th>
+<td>Austria MGI (Hermannskogel)</td></tr>
+<tr><th>Projection:</th><td>Transverse Mercator (BMN zone M31)</td></tr>
+<tr><th>North reference:</th><td>Grid</td></tr>
+<tr><th>Grid parameters:</th><td>Central meridian 13&deg;20'E<br />
+False easting 450km<br />
+No additional scaling<br />
+Grid boundaries at 11&deg;50' and 14&deg;50'</td></tr>
+<tr><th>EFEC coordinate conversion<br />equation with respect to WGS84:</th>
+<td>Offsets &Delta;x = -575m, &Delta;y = -93m, &Delta;z = -466m<br />
+Rotations &omega;<sub>x</sub> = 5.1"; &omega;<sub>y</sub> = 1.6", &omega;<sub>z</sub> = 5.2"<br />
+Scaling -2.5ppm
+</td></tr></table>
+</div>
+
+<p>Note: The table above used to incorrectly give the y rotation as 5.1".
+But there's a slightly more accurate version in the
+<a href="coord.htm#ftnBMN">Coordinate Systems section</a>.</p>
+
+<p>(Technical note: the BMN grid is actually the same as Universal Transverse
+Mercator zone 31, but setting your GPS for UTM will give rather different
+coordinates, as the plateau is actually in zone 33. My understanding of the
+situation is that the Austrians have found it more convenient to extend one
+grid to cover the whole country, thus deviating from UTM for the areas of the
+country which are just over the grid boundary. This is an important gotcha to
+watch out for, since while all the other coordinate systems produce answers in
+recognisably different formats, UTM 33 coordinates look like dataset
+coordinates but are offset by a couple of kilometres. Having your GPS set to
+the wrong datum produces even more subtle errors - the difference between BMN
+grid + WGS84 datum and BMN grid + Austrian datum is an offset of around 500m to
+the south and 50m in altitude.)</p>
+
+<p>A good way of testing that your GPS is correctly set up is to set it WGS84
+Lat/Long and enter a waypoint for a point whose coordinates are known &ndash;
+such as the 204a tag, at 47&deg;41.456'N 013&deg;49.288' &ndash; and then
+change the settings again to use the user grid. It will now convert this point
+into the new grid; if you check its coordinates, it should come out as
+something close to 486697E, 5283699N, which are the BMN coordinates for 204a.
+For use in the dataset we tend to subtract the 450km offset in the easting and
+ignore the first two digits of the northing, giving 36697E 83699N.</p>
+
+<p>Write down the figure that the GPS gives for each waypoint <i>at the
+time</i> (just in case some failure loses the data from the GPS memory &ndash;
+this has happened a couple of times in recent years, much to the annoyance of
+everybody involved). That's all you need to do at the cave. Get the GPS data
+downloaded to a computer next time you are in Base Camp (or Top Camp if someone
+has a laptop :-), and as a backup (expo computers break down surprisingly often
+it seems) write it down by hand on one of the A5 cave info sheets with all the
+other details of your cave and put that in the surveys ringbinder file.  </p>
+
+<p>If you want to read about the nitty gritty of converting GPS coordinates to
+the ones used by the Kataster system, you can do no better than read the
+short introduction to <a href="coord.htm">coordinate systems</a>, which briefly
+says "it's horribly complicated and we use computer programs to do it properly".
+(A rather outdated first attempt at this can also be found in Wookey's
+<a href="../../years/1996/gps.htm">Compass Points Article</a> from 1996, which
+briefly says "it's horribly complicated and we don't really know how to do it
+properly".) Overall things have significantly improved since the early days,
+particularly as without the fog of the SA variation it's now easy to find out
+whether your GPS is set up right by just GPSsing a known point and comparing
+the results.  However, the main point of having a GPS fix on an entrance is
+so we can find it again and be sure it is the same one!</p>
+
+<hr />
+
+<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: <a href="getin.htm">getting it in</a> 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>
+</html>

handbook/survey/drawup.htm

@@ -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: Drawing Up</title>
 <link rel="stylesheet" type="text/css" href="../../css/main2.css" />
 </head>
@@ -10,12 +8,18 @@
 <h2 id="tophead">CUCC Expo Surveying Handbook</h2>
 <h1>Drawing up your survey</h1>
 
-<p>The original notes and sketches should be filed in a clearly marked
-envelope - don't take them out until you are ready to draw up, and put them
+<p>The original notes and sketches will be filed in a clearly marked
+wallet - see  <a href="newcave.html#newwallet">"Creating a new cave"</a> 
+- don't take them out until you are ready to scan them, and put them
 away again as soon as you have finished. They may never be referred to again,
 but ultimately they are the most valuable record of your survey and are kept
 for reference if there is ever a problem.</p>
 
+<p>After typing in all the data in <a href="newcave.html#survexformat">
+survex format</a> , run 
+<a href="newcave.html#runsurvex">
+aven</a> (the GUI interface to survex) and print out a centre-line plan.
+
 <p>Take the printed centre lines and redraw the survey round it, working from
 the original sketches as if this was to be the final published survey. You
 can "invent" details like boulders in boulder-strewn passage, but otherwise,
@@ -36,41 +40,25 @@ by the BCRA, with occasional differences - such as large-enough boulders
 which are sketched to scale using the US symbol. The current state of
 standardisation for cave survey symbols (a useful guide to what we should
 be using where possible) has been documented by
-<a href="http://www.olsen.ch/~devon/uis/misc/praezis/">H&auml;uselmann,
+<a href="http://www.chaos.org.uk/survex/cp/CP14/CPoint14.htm">H&auml;uselmann,
 Weidmann and Ruder (1996)</a>, but this is up for discussion in 1997.
 An alternative set of standards can be seen from the
 Australian Speleological Federation
-<a href="http://rubens.its.unimelb.edu.au/~pgm/asf/stdsurv.html">here</a>.</p>
+<a href="http://www.caves.org.au/resources/internal-resources/category/29-surveying">here</a>.</p>
 
 <p>Make sure that you draw both plan and elevation (the latter should be an
 extended section, rather than a projected elevation) for horizontal passage.
 For pitches, several plans at different levels may be easiest (rather like
 the cross sections at each survey station used in horizontal passage). Also
-projected elevations may be useful in addition to the extended section.</p>
+projected elevations may be useful in addition to the extended section. But 
+learning a good set of procedures for using survex is the way to go.</p>
 
-<p>Write a <b>passage description</b>. 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. It will be
-regarded as helpful if you actually type this description into a computer
-rather than writing in the log book - but make sure it can be found again! In
-written descriptions, underline passage names the first time they are
-mentioned, or when they are "defined".</p>
-
-<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 all natural belays recognised.
-Ideally, the knots should be left in ropes removed at derigging, so they can
-be <b>measured</b> for the rigging guide. Remember to do this before undoing
-the knots for rope-washing. 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!</p>
 
 <p>If you did all that properly, there should be very little left to do in
 the UK, unless you have volunteered to help with drawing up the final survey.
 (Fool!) However, it is as well to check that you have done all you can before
 BCRA conference, by reading the <a href="athome.htm">Back in the UK</a> page.</p>
+
 <!-- This looks like a rather hollow joke in the context of the last year's
 experience: it's now late April 2004, and the 204 survey is only just
 approaching completion. This shows how easy it is for these things to go wrong.
@@ -89,25 +77,23 @@ broke down last summer, so a number of surveys never got drawn up. -->
 		<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>Pitfalls to avoid, <a href="hints.htm">hints'n'tips</a></li>
 		<li>Methods: <a href="ontop.htm">surface</a></li>
 		<li>Base Camp: <a href="getin.htm">getting it in</a> to the
 		computer</li>
-		<li>Base Camp: drawing it up, writing the description</li>
+		<li>Base Camp: drawing it up</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>
+<li><a href="../../index.htm">Expedition Intro page</a></li>
+<li><a href="../../../index.htm">CUCC Home page</a></li>
 </ul>
 
 </body>

handbook/survey/getin.htm

@@ -1,56 +1,81 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html>
 <head>
-<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" />
 </head>
 <body>
 
-<div class="onleft">
+<h2 id="tophead">CUCC Expo Surveying Handbook</h2>
+<h1>From muddy book to survex plot</h1>
+
+<div class="onright">
 <a href="../../piclinks/typing.htm"><img src="../../tinypix/typing.jpg"
 width="176" height="115" alt="" /></a>
-<p class="caption">Tony Rooke entering data</p></div>
+<p class="caption">Tony Rooke entering data (1991)</p></div>
 
-<h2 id="tophead">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
-envelope - don't take them caving again and don't leave them lying around to
-be "G&ouml;ssered"!</p>
-
-<p>The notes (all of them, including dates, personnel, calibration, LRUD,
-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
-marginally legible). This should be proof checked by someone else. Current
-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
-"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.</p>-->
-
-<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
-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
-folder the notes are in, with index numbers.</p>
 
 <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
-fairly clear. Survex has some very flexible data entry options, so there
+fairly clear. 
+<p>Survex has some very flexible data entry options, so there
 are a few extra guidelines to try to get some consistency in the way
 everyone uses it within this project.</p>
 
-<ul>
-<li>It will be easiest if you start from one of the existing template files,
+<p>Survex (including the graphical software 'aven') is already installed
+on the expo laptop. These instructions assume that you are using the expo laptop.
+
+
+
+<h3>Where to put your data</h3>
+
+<p>Where to put your data: <b>If in doubt, ask!</b>. These instructions assume 
+that you are typing it in on the <em>expo laptop</em>. (You can do it fom your own
+laptop if you have been initiated into the deep magic of the "loser" repository
+of the distributed version control system - see the
+<a href="../update.htm#repositories">list of repos</a>.
+
+<ul><li>If it is a surface
+survey, it goes in the "surface" directory; 
+<li>if it is a file of fixed points
+(like GPS fixes, or map coordinates), it goes in the "fixedpts" directory; 
+<li>if
+it is a new cave on the near-plateau, put it in a new directory under "caves-1623".
+</ul>
+<li>Underground data for Steinbr&uuml;ckenh&ouml;hle goes in one of the
+subdirectories under caves-1623/204; it may well be clear which one from what it
+links to, but if not, ask.</p>
+</li>
+</ul>
+
+<h3>Use a template</h3>
+
+
+<p>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
-don't leave any blanks! Copy this to where you want to put your data
-<em>before</em> editing it (with any luck, the template should be on CD-ROM, so
-you can't trash it :-).</li>
+don't leave any blanks! Copy <em>and rename this</em>  to where you want to put your data
+<em>before</em> editing it. Too many people have overwritten the
+template in the past, try not to do this yourself.
+
+<h3>Filename and data-entry conventions</h3>
+
+<ul>
+<li>Use Unix line endings (i.e. \n not \r\n).
+
+<li>Use UTF-8 character encoding.
+
+<li>Cave numbers are written without any leading zeros at all (in filenames,
+  survey names, or anything else!).
+
+<li>Entrances have station names such as p204b.  In the event of the tag
+  location being different from the entrance location, the tag point
+  should be named with a "t" instead, e.g. t204b.
+
+<li>No full stop (.) characters in station names.
+
+<li>All filenames to be in lower case. Capital letters in filenames can still (in 2018)
+cause hassle when moving between Linux and Windows.
 
 <!-- I think we can dispense with this now - DL
 <li>Filenames: Because Survex is used on different sorts of computer, it is
@@ -65,16 +90,17 @@ 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
 characters with no extension.-->
 
-<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
-(like GPS fixes, or map coordinates), it goes in the "fixedpts" directory; if
-it is a new cave on the plateau, put it in a new directory under "caves".
-Underground data for Steinbr&uuml;ckenh&ouml;hle goes in one of the
-subdirectories under caves/204; it may well be clear which one from what it
-links to, but if not, ask.</p>
-</li>
+<li>No filenames starting with "-" or "!".
 
-<li>What to call your survey: all your data should be inside a begin/end pair
+<li>Caves with a provisional number consisting of a year and a serial number
+  should be <em>hyphenated</em>, thus 2018-ad-01 not 2018_01 or any of the various other
+  variants.
+</ul>
+
+
+
+<h3>The name of your survey</h3>
+What to call your survey: all your data should be inside a begin/end pair
 with a meaningful name. This need not be the same name as the file, but as a
 general rule it should be so unless there is a really good reason not to.  On
 the other hand, if you have made two or three trips to the same cave,
@@ -90,14 +116,19 @@ it can be a good idea to nest surveys in one file:
     *end pt2
 *end 2050-01
 </pre>
+or you can create several .svx files. 
+Creating several .svx files seemsto be current practice as it 
+simplifies the manual process of knitting several different people's trips together.
 
 <p>There is no restriction on the length of these names, but as they can be
-displayed in Aven, Tunnel and other such programs, it helps not to have
-anything too elaborate. Older versions of Survex required each prefix to be
+displayed in aven, tunnel and other such programs, it helps not to have
+anything too elaborate. Older versions of survex required each prefix to be
 unique in its first eight characters, and this is not a bad guideline to
 follow.</p></li>
 
-<li>Every station should have a number <em>within your survey</em> even if it
+<h3>Station names</h3>
+
+<p>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
@@ -107,7 +138,7 @@ head of new pitch</tt> &ndash; this may or may not catch on as a standard.</li>
 
 <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 data, or
-the Survex syntax of <tt>*equate</tt> and <tt>*export</tt> which can be rather
+the survex syntax of <tt>*equate</tt> and <tt>*export</tt> which can be rather
 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>
@@ -119,38 +150,44 @@ dataset:</p>
 
 <li>Don't put any *equate directives to other surveys into your file (or any
 survey legs which quote station names from other survey files).  Instead, go to
-the file which *includes the other files in the same area.  For example, if you
-have created a file Trivial.svx in the caves/204/deepsouth directory, go to the
+the file which *includes the other files in the same area.  <br><br>
+For example, if you
+have created a file trivial.svx in the caves-1623/204/deepsouth directory, go to the
 file deepsouth/deepsouth.svx, where you will find *include lines for each of
 the files, together with the *equate lines to connect them together. Add an
 include for your file, and *equate lines for each of your survey stations which
 is the same as one in another survey. If your survey connects to points in
 surveys in files in more than one directory then the *equates should go in the
-204/204.svx file, but at this stage it is probably worth enlisting the help of
-someone who knows the structure of the data inside-out!</li>
-<li>You should now find that if you run Survex on one of the master files
+/204/204.svx file, but at this stage it is probably worth enlisting the help of
+someone who knows the structure of the data inside-out! <br><br>
+<li>You should now find that if you run survex on one of the master files
 (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
-.3d file in Aven. Using 204.svx should give info on how long and how
+.3d file in vven. Using 204.svx should give info on how long and how
 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>
 
-<p><a name="concrete">To make that</a> all a bit more concrete, here is a
+<p>Now you have been typing this on the expo laptop, and before you let someone 
+else use the laptop you need to find a nerd to do the deep magic to add your 
+file to the version control repository "loser". Watching the nerd do this is 
+usually your first initiation into learning how to do it yourself.
+
+
+<h3 id="concrete">Example svx file</h3>
+
+<p>To make that all a bit more concrete, here is a
 fictitious example of a survey off Swings &amp; Roundabouts in 204. Let's say
 that you went to explore a lead from the QM list numbered 2002-99, that the
 nearest survey station was listed as 204.allswings.swings5.2 and you found it
 successfully, and numbered it within your own survey as station 0. Then you
-might create the following file:</p>
+might create the following file: (note we don't use umlauts)</p>
 <!-- Stolen, with apologies to Martin and Lucia, from
 caves/204/swings/ermintrude.svx. --> 
 <pre><i>File wibble.svx</i>
 *begin wibble
 
 ; Locn:	Totes Gebirge, Austria - Loser/Augst-Eck Plateau (kataster group 1623)
-; Cave:	Steinbruckenhöhle
+; Cave:	Steinbruckenhohle
 *title "Wibbled by Goesser"
 *date 2004.08.32 ;date the survey was done
 *team Insts John Doe
@@ -177,10 +214,10 @@ caves/204/swings/ermintrude.svx. -->
 *end wibble
 </pre>
 
-<p>That lot would be typed by copying caves/204/template.svx to
-caves/204/swings/wibble.svx and then filling in the blanks and adding your
+<p>That lot would be typed by copying caves-1623/204/template.svx to
+caves-1623/204/swings/wibble.svx and then filling in the blanks and adding your
 data. If you are linking to the rest of the survey then in the file
-caves/204/swings/allswings.svx add the lines:</p>
+caves-1623/204/swings/allswings.svx add the lines:</p>
 
 <pre>
 *include wibble
@@ -195,7 +232,7 @@ the file which includes both surface stuff and underground stuff.</p>
 
 <p>Once you have your data typed in and checked, it must be run through the
 survey software (which on expo will be <a
-href="http://www.survex.com/">Survex</a>) and a centre line printed, both for
+href="http://www.survex.com/">survex</a>) and a centre line printed, both for
 plan and for extended elevation. Measure the print out to check that it really
 has printed at the scale you wanted (typically 1:500), as this has sometimes
 caused problems in the past.</p>
@@ -204,36 +241,5 @@ caused problems in the past.</p>
 
 <hr />
 
-<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>
 </html>

handbook/survey/gps.htm

@@ -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: GPS</title>
 <link rel="stylesheet" type="text/css" href="../../css/main2.css" />
 </head>
@@ -25,11 +23,15 @@ this is the point to use for a GPS fix too.</p>
 
 <p>If however, you are dealing with a cave at the foot of a cliff, or
 otherwise with a restricted view of the sky, then choose instead a good
-landmark with a clear view, and within one (or maybe two) survey shots
+landmark with a wide, clear view of the sky, and within one (or maybe two) survey shots
 of the entrance. If you have found a group of caves close together, it
 might be better to GPS a central point rather than get quick (but less
 accurate) fixes on each entrance.</p>
 
+<p>We now (2018) have differential GPS which is much more accurate than
+in the past (e.g. Wookey's 1996 article) but altitudes are often very inaccurate
+and GPOS devices don't tell you how inaccurate the altitude is.
+
 <h3>Taking the fix</h3>
 
 <p>Once you have chosen your point, mark it in some way (could be a spit hole
@@ -54,134 +56,13 @@ the waypoint averaging before moving the unit or changing the display page.
 <b>Take a photo of your GPS point showing at least one of your cave entrances
 too.</b></p>
 
-<h3>Coordinate systems</h3>
+<p>We all use the same coordinate system WGS84 these days, so <a href="coord2.html">the extensive discussion 
+on coordinate systems</a> has been moved to a different page. If you are really interested you can read 
+<a href="coord.htm">Olaf's article</a>too.
 
-<p>It doesn't especially matter what display options are selected when you
-are getting the GPS fix, but it is important to use standard ones when writing
-down the reported position in the survey book. The usual systems are either
-Lat/Long with the WGS84 datum, which all GPSses support out of the box; or
-the Austrian BMN (Bundesmeldnetz) system, which should be relative to the
-Austrian MGI datum (Hermannskogel), which is what we use for our surveys. It
-doesn't matter <i>too</i> much what combination of parameters you actually use
-as long as you record what they were, since we have conversion programs that
-can convert coordinates between the systems; but remember to record <b>which
-grid and which datum</b> your GPS was set for when you copy the fix into the
-survey file. (Besides the risk of introducing severe errors, it is an
-extraordinarily tedious task to have to repeatedly try all the plausible
-combinations of grid and datum that a given set of numbers might be in, convert
-them all to dataset coordinates and see which ones give answers in vaguely the
-right place, which is what someone will have to do if you don't write the
-details down.)</p>
-
-<p>If you want to set up your GPS to use the same coordinates the survey data
-set uses, which makes life a lot easier, then these are the runes to use as a
-"User Grid" if the unit doesn't support BMN coordinates immediately (which
-Garmin ones don't, for example):</p>
-
-<div style="background-color: #BDB">
-<table>
-<tr>
-<th>Ellipsoid:</th><td>Austrian (Bessel 1841)<br />
-a = 63377397.155m (&Delta;A = 739.845)<br />
-1/f = 299.1528128 (&Delta;f x 10,000 = 0.10037428)
-</td></tr>
-<tr>
-<th>Datum:</th>
-<td>Austria MGI (Hermannskogel)</td></tr>
-<tr><th>Projection:</th><td>Transverse Mercator (BMN zone M31)</td></tr>
-<tr><th>North reference:</th><td>Grid</td></tr>
-<tr><th>Grid parameters:</th><td>Central meridian 13&deg;20'E<br />
-False easting 450km<br />
-No additional scaling<br />
-Grid boundaries at 11&deg;50' and 14&deg;50'</td></tr>
-<tr><th>EFEC coordinate conversion<br />equation with respect to WGS84:</th>
-<td>Offsets &Delta;x = -575m, &Delta;y = -93m, &Delta;z = -466m<br />
-Rotations &omega;<sub>x</sub> = 5.1"; &omega;<sub>y</sub> = 1.6", &omega;<sub>z</sub> = 5.2"<br />
-Scaling -2.5ppm
-</td></tr></table>
-</div>
-
-<p>Note: The table above used to incorrectly give the y rotation as 5.1".
-But there's a slightly more accurate version in the
-<a href="coord.htm#ftnBMN">Coordinate Systems section</a>.</p>
-
-<p>(Technical note: the BMN grid is actually the same as Universal Transverse
-Mercator zone 31, but setting your GPS for UTM will give rather different
-coordinates, as the plateau is actually in zone 33. My understanding of the
-situation is that the Austrians have found it more convenient to extend one
-grid to cover the whole country, thus deviating from UTM for the areas of the
-country which are just over the grid boundary. This is an important gotcha to
-watch out for, since while all the other coordinate systems produce answers in
-recognisably different formats, UTM 33 coordinates look like dataset
-coordinates but are offset by a couple of kilometres. Having your GPS set to
-the wrong datum produces even more subtle errors - the difference between BMN
-grid + WGS84 datum and BMN grid + Austrian datum is an offset of around 500m to
-the south and 50m in altitude.)</p>
-
-<p>A good way of testing that your GPS is correctly set up is to set it WGS84
-Lat/Long and enter a waypoint for a point whose coordinates are known &ndash;
-such as the 204a tag, at 47&deg;41.456'N 013&deg;49.288' &ndash; and then
-change the settings again to use the user grid. It will now convert this point
-into the new grid; if you check its coordinates, it should come out as
-something close to 486697E, 5283699N, which are the BMN coordinates for 204a.
-For use in the dataset we tend to subtract the 450km offset in the easting and
-ignore the first two digits of the northing, giving 36697E 83699N.</p>
-
-<p>Write down the figure that the GPS gives for each waypoint <i>at the
-time</i> (just in case some failure loses the data from the GPS memory &ndash;
-this has happened a couple of times in recent years, much to the annoyance of
-everybody involved). That's all you need to do at the cave. Get the GPS data
-downloaded to a computer next time you are in Base Camp (or Top Camp if someone
-has a laptop :-), and as a backup (expo computers break down surprisingly often
-it seems) write it down by hand on one of the A5 cave info sheets with all the
-other details of your cave and put that in the surveys ringbinder file.  </p>
-
-<p>If you want to read about the nitty gritty of converting GPS coordinates to
-the ones used by the Kataster system, you can do no better than read the
-short introduction to <a href="coord.htm">coordinate systems</a>, which briefly
-says "it's horribly complicated and we use computer programs to do it properly".
-(A rather outdated first attempt at this can also be found in Wookey's
-<a href="../../years/1996/gps.htm">Compass Points Article</a> from 1996, which
-briefly says "it's horribly complicated and we don't really know how to do it
-properly".) Overall things have significantly improved since the early days,
-particularly as without the fog of the SA variation it's now easy to find out
-whether your GPS is set up right by just GPSsing a known point and comparing
-the results.  However, the main point of having a GPS fix on an entrance is
-so we can find it again and be sure it is the same one!</p>
 
 <hr />
 
-<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: <a href="getin.htm">getting it in</a> 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>
 </html>

handbook/survey/hints.htm

@@ -1,14 +1,14 @@
-<!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: Hints &amp; tips</title>
 <link rel="stylesheet" type="text/css" href="../../css/main2.css" />
 </head>
 <body>
 
 <h2 id="tophead">CUCC Expo Surveying Handbook</h2>
-<h1>Wookey's hints and tips to save you going back to do it again</h1>
+<h1>Wookey's hints and tips</h1>
+
+<p>... to save you going back to do it again.
 
 <p><i>"hmm - not going to finish this even slightly, so some points to bear
 in mind:"</i></p>
@@ -59,7 +59,7 @@ might get rubbed off.</li>
 
 <li>Take at least one spare pencil!</li>
 
-<li>Return instuments to the carbide dessicator before you fall asleep
+<li>Return instuments to the dessicator before you fall asleep
 otherwise they are likely to fog up the next time. Don't leave them in the
 cave, both for the above reason and because the next survey may need them
 somewhere else entirely.</li>
@@ -109,37 +109,6 @@ Mulu once like that - Andy F)</li>
 
 <hr />
 
-<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, hints'n'tips to
-		make life easier</li>
-		<li>Methods: <a href="ontop.htm">surface</a></li>
-		<li>Base Camp: <a href="getin.htm">getting it in</a> 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>
 </html>

handbook/survey/how.htm

@@ -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: Underground</title>
 <link rel="stylesheet" type="text/css" href="../../css/main2.css" />
 </head>
@@ -103,8 +101,9 @@ useful - record approx compass points of the directions taken.
 <p>LRUD is becoming increasingly important so we can use some of the
 fancy cave visualisation software which is now becoming available. For
 a discussion of how to record this data, see Andy Atkinson's article in
-<a href="http://www.chaos.org.uk/survex/cp/cp10/cpoint10.htm#art3">Compass
-Points #10</a>.</p></li>
+<a href="lrudcp10a3.html">"Enhanced LRUD Recording"</a> (originally published in the
+<a href="http://www.chaos.org.uk/survex/cp/CP10/CPoint10.htm#Art_3">Compass
+Points archive</a>. </p></li>
 
 <li>Station location. Some stations will never be used again, and the location
 is only needed when drawing up, as an additional helpful datum.  Stations at
@@ -146,38 +145,6 @@ before and after the trip).</li>
 do the above, written from experience in Austria.</p>
 
 <hr />
-<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: underground</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: <a href="getin.htm">getting it in</a> 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>
 </html>

handbook/survey/index.htm

@@ -37,7 +37,13 @@ detailed topics.</p>
 	<ul>
 		<li><a href="what.htm">What is a cave survey ?</a></li>
 		<li><a href="why.htm">Why am I doing this ?</a></li>
-	</ul></li>
+	</ul>
+  </li>
+	<li><b>For those new to CUCC expo surveying:</b>
+	<ul>
+		<li><a href="newcave.html">The complete process for recording cave data</a></li>
+	</ul>
+  </li>
 	<li><b>For those carrying out a survey:</b>
 	<ul>
 		<li>Methods: <a href="how.htm">underground</a></li>

handbook/survey/lrudcp10a3.html

@@ -0,0 +1,151 @@
+<html>
+<head>
+<title>CUCC Expo Surveying Handbook: LRUDs</title>
+<link rel="stylesheet" type="text/css" href="../../css/main2.css" />
+</head>
+<body>
+
+<h2 id="tophead">CUCC Expo Surveying Handbook - LRUDs</h2>
+
+<h1>Enhanced LRUD Recording</h1>
+<P>
+<I>Andy Atkinson</I>
+<P>
+<I>A number of survey software packages now let you
+include LRUD (Left Right Up Down) passage dimensions in some form
+or other and will produce a plot using this information. All of
+these, with the exception of Toporobot, are simplistic in their
+approach, and if you have seen the output you will recognise the
+rather odd-looking characteristic shapes that occur. There are
+good reasons why this is so. The conventions that surveyors use
+when recording the data, such as 'in the direction of the survey',
+and 'across the passage' are not very easily defined in computing
+terms. Also the fact that LRUDs are typically taken at stations,
+and stations are often at junctions causes problems as junctions
+tend to be atypical, rather than typical, of the passage. There
+are a whole host of other things like what to do when a value
+is not given, a question mark is entered, and at the ends of passages.
+If zero is assumed at an omitted reading then a pinch-point occurs
+in the walls at that station - not really the desired effect.</I>
+<P>
+<I>We have been examining the details of this process
+with a view to implementing something in Survex, and generationg
+a proper 3D model of the complex Kaninchenhohle. It quickly became
+clear that as well as the programming difficulties there were
+significant problems in terms of the data that was actually collected.
+Obviously a set of 4 numbers conveys much less information than
+a sketch. Unfortunately a sketch is inherently 2-dimensional,
+and thus is not very helpful when trying to construct a 3D model.
+So the question becomes - what is the least information that needs
+to be recorded in order to construct a useful 3D model? Obviously
+the answer depends on what you want to use the finished model
+for, and the usual constraints on surveying manpower, time &amp;
+conditions.</I>
+<P>
+<I>Andy Atkinson took a look at the  specific area
+of improving the information contained in the LRUD data without
+dramatically increasing the time it took to record, or the complexity
+beyond the point which surveyors would stand (where relatively
+inexperienced Cambridge Cavers in Austria's horrible caves have
+a particularly low tolerance of such things). Obviously improvements
+of this nature are no use if surveyors think they are too much
+extra work. Here he presents his second iteration of the idea
+for comment.</I>
+<P>
+<I>The computing aspects of LRUD interpretation and
+ the broader issues of wall modelling need articles of their own
+to explore. These will be in future issues.<BR>
+</I>
+<P>
+The suggested format is an extension of the now standard
+LRUD, with a 5th column  -'E' for Extension - which is used in
+some cases. One obvious improvement is a notation for allowing
+more than one value to be given in the same direction. This particularly
+useful in traversable rift where you really want to indicate the
+distance to both the actual and apparent floors, or sometimes
+in a wide bedding where only the centre part is person-sized.
+There are many possibly notations, all prone to confusion, or
+not completely general. 
+<UL>
+<LI>Two values separated by a slash is obvious except
+that many people (CUCC included) use slash instead of the decimal
+point, so that would be confusing. 
+<LI>A secondary reading below the first may use an
+extra line or be cramped, and which is which?.
+<LI>A comma-separated pair is plausible, but the
+French use commas for decimal points. 
+<LI>Or you could use another letter: e.g. F3, in
+the E or comment columns, meaning Floor., but Americans use Floor
+instead of Down.
+<LI>R for rift is likely to be confused with R for
+right if put in the comment column.
+<LI>A for Alternate is the best I can think of. Obviously
+you could just pick any letter, but we have been careful thoughout
+to use easy-to-remember abbreviations so something completely
+arbitrary is not a good idea.
+</UL>
+
+<TABLE BORDERCOLOR=#808080 BORDER=1>
+<TR><TD BGCOLOR=#FFFF00 WIDTH=83><CENTER><B>Bit of Cave</B></CENTER>
+</TD><TD BGCOLOR=#FFFF00 WIDTH=36><CENTER><B>L</B></CENTER>
+</TD><TD BGCOLOR=#FFFF00 WIDTH=38><CENTER><B>R</B></CENTER>
+</TD><TD BGCOLOR=#FFFF00 WIDTH=38><CENTER><B>U</B></CENTER>
+</TD><TD BGCOLOR=#FFFF00 WIDTH=38><CENTER><B>D</B></CENTER>
+</TD><TD BGCOLOR=#FFFF00 WIDTH=27><CENTER><B>E</B></CENTER>
+</TD><TD BGCOLOR=#FFFF00 WIDTH=100><CENTER><B>Comment</B></CENTER>
+</TD><TD BGCOLOR=#FFFF00 WIDTH=298><CENTER><B>Explanation</B></CENTER>
+</TD></TR>
+<TR><TD WIDTH=83>
+<CENTER><IMG src="../i/img00060.gif"></CENTER></TD><TD WIDTH=36><CENTER>n</CENTER>
+</TD><TD WIDTH=38><CENTER>~n</CENTER></TD><TD WIDTH=38><CENTER>n</CENTER></TD><TD WIDTH=38><CENTER>n</CENTER></TD>
+<TD WIDTH=27><P></TD><TD WIDTH=100></TD><TD WIDTH=298>L &amp; R are defined as the bisector of the legs. For the last station they are perpendicular to the last leg. ~ is used to indicate estimated distances (very useful to know which numbers may be suspect when drawing up)
+</TD></TR>
+<TR><TD WIDTH=83>
+<CENTER><IMG src="../i/img00061.gif"></CENTER></TD><TD WIDTH=36><CENTER>(n)</CENTER>
+</TD><TD WIDTH=38><CENTER>n</CENTER></TD><TD WIDTH=38><CENTER>n</CENTER></TD><TD WIDTH=38><CENTER>n</CENTER></TD>
+<TD WIDTH=27><P></TD><TD WIDTH=100>(220)</TD><TD WIDTH=298>Where L or R in standard direction is unhelpful, irrelevant or meaningless another direction is given. The approximate bearing is given in the comments field.
+</TD></TR>
+<TR><TD WIDTH=83><P></TD><TD><CENTER>Pn<P>Pn<P></CENTER></TD><TD
+WIDTH=38><CENTER>Pn<P>P(n)<P></CENTER></TD>
+<TD WIDTH=38><CENTER>Pn<P>P(n)<P></CENTER></TD><TD
+WIDTH=38><CENTER>Pn<P>P(n)<P></CENTER></TD><TD
+WIDTH=27><P></TD><TD WIDTH=100><P>(NE)(160)(260)
+</TD><TD WIDTH=298>For pitches give NSEW instead of LRUD.<BR>Where NSEW is not appropriate (e.g. axes of elliptical shaft lie in another orientation) then use bracket notation to give bearings</TD></TR>
+<TR><TD WIDTH=83>
+<CENTER><IMG src="../i/img00062.gif"></CENTER></TD><TD WIDTH=36><CENTER>Jn</CENTER>
+</TD><TD WIDTH=38><CENTER>n</CENTER></TD><TD WIDTH=38><CENTER>n</CENTER></TD><TD WIDTH=38><CENTER>n</CENTER></TD>
+<TD WIDTH=27><P></TD><TD WIDTH=100><P></TD><TD WIDTH=298>At a Junction the value that would otherwise disappear down the joining passage is given as where the wall would have been if the joining passage was not there.
+</TD></TR>
+<TR><TD WIDTH=83>
+<CENTER><IMG src="../i/img00063.gif"></CENTER></TD><TD WIDTH=36><CENTER>Jn</CENTER>
+</TD><TD WIDTH=38><CENTER>Jn</CENTER></TD><TD WIDTH=38><CENTER>n</CENTER></TD><TD WIDTH=38><CENTER>n</CENTER></TD>
+<TD WIDTH=27><CENTER>n</CENTER></TD><TD WIDTH=100><P></TD><TD WIDTH=298>When a survey ends at a junction the L &amp; R values for the surveyed passage as if it continued are given. Also given is the 'Extension'. The distance that the survey leg would need to be continued to meet the wall.
+</TD></TR>
+<TR><TD WIDTH=83>
+<CENTER><IMG src="../i/img00064.gif"></CENTER></TD><TD WIDTH=36><CENTER>n</CENTER>
+</TD><TD WIDTH=38><CENTER>n</CENTER></TD><TD WIDTH=38><CENTER>Jn</CENTER></TD><TD WIDTH=38><CENTER>n</CENTER></TD>
+<TD WIDTH=27><CENTER>n</CENTER></TD><TD WIDTH=100><P></TD><TD WIDTH=298>At a point where a passage meets a pitch The extension is given to the far wall and the roof or floor (roof in the example) is given using the Junction notation.
+</TD></TR>
+<TR><TD WIDTH=83>
+<CENTER><IMG src="../i/img00065.gif"></CENTER></TD><TD WIDTH=36><CENTER>C</CENTER>
+</TD><TD WIDTH=38><CENTER>n</CENTER></TD><TD WIDTH=38><CENTER>n</CENTER></TD><TD WIDTH=38><CENTER>n</CENTER></TD>
+<TD WIDTH=27><P></TD><TD WIDTH=100><P></TD><TD WIDTH=298>For a perimeter survey use C (for Chamber) in either the L (anticlockwise survey) or R (clockwise) column. Readings are on bisectors of legs
+</TD></TR>
+<TR><TD WIDTH=83><CENTER><IMG src="../i/img00066.gif"><P><Pre> </Pre><IMG src="../i/img00067.gif"></CENTER></TD><TD
+WIDTH=36><CENTER>C<P>C<P><Pre> </Pre>Cn<P></CENTER></TD><TD WIDTH=38><CENTER>C<P>C<P><Pre> </Pre>Cn<P></CENTER></TD><TD WIDTH=38><CENTER>n<P>n<P><Pre> </Pre>n<P></CENTER>
+</TD><TD WIDTH=38><CENTER>n<P>n<P><Pre> </Pre>n<P></CENTER></TD><TD WIDTH=27><CENTER>C<P>n<P><Pre> </Pre>n<P></CENTER></TD><TD
+WIDTH=100><P></TD>
+<TD WIDTH=298>For a radial survey the centre point is given like this<BR>Then
+the other give the Extension value to the wall, as well as U &amp; D<P>In more complex areas L &amp; R values can also be given if they are significant
+</TD></TR>
+<TR><TD WIDTH=83>
+<CENTER><IMG src="../i/img00068.gif"></CENTER></TD><TD WIDTH=36><CENTER>n</CENTER>
+</TD><TD WIDTH=38><CENTER>n</CENTER></TD><TD WIDTH=38><CENTER>Jn</CENTER></TD><TD WIDTH=38><CENTER>Jn</CENTER></TD>
+<TD WIDTH=27><CENTER>Jn</CENTER></TD><TD WIDTH=100><P></TD><TD WIDTH=298>For more complicated bits of the cave the notations given can be combined to fit the need
+</TD></TR>
+</TABLE>
+
+<hr />
+
+</body>
+</html>

handbook/survey/more.htm

@@ -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: More resources</title>
 <link rel="stylesheet" type="text/css" href="../../css/main2.css" />
 </head>
@@ -15,13 +13,6 @@
 It also has a <a href="http://www.survex.com/maillist.html">mailing list</a>
 to keep you up to date with new releases and the like.</p>
 
-<!-- this list is so out of date that it's not worth pointing to unless
- it gets a thorough overhaul...
-<p>You can find a list of
-<a href="http://www.sat.dundee.ac.uk/~arb/surveying/">other available
-surveying software</a> on Andrew Brooks' site (along with pages for BCRA and
-its various special interest groups, and quite a lot of other caving clubs).
--->
 
 <p>For more discussion on Cave Surveying, there is a specialist
 <a href="http://www.survex.com/maillist.html">cave-surveying
@@ -30,45 +21,11 @@ here is not at the beginning-surveyor level, however.</p>
 
 <p>You might also like to join the Cave Surveying <a
 href="http://www.sat.dundee.ac.uk/~arb/surveying/csg.html">special interest
-group</a> of the British Cave Research Association. This publishes the
-quarterly <a href="../../../../survex/cp/index.htm">Compass Points</a>, which
-is also available on the web, some time after the printed edition (the delay
-depends somewhat on how much work the webmaster has to do on <b>this</b> site
-before finding time for Compass Points :-)</p> <!-- I understand he hasn't done
-any more work on Compass Points lately than he has on this site. -->
+group</a> of the British Cave Research Association. This published (1993-2008) the
+quarterly <a href="http://www.chaos.org.uk/survex/cp/">Compass Points</a>, which
+is also available on the web.
 <hr />
 
-<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: <a href="getin.htm">getting it in</a> 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>
 </html>

handbook/survey/newcave.html

@@ -0,0 +1,259 @@
+<html>
+<head>
+<title>Handbook - Doing a new cave</title>
+<link rel="stylesheet" type="text/css" href="../../css/main2.css" />
+</head>
+<body>
+<h2 id="tophead">CUCC Expedition Handbook -  New Cave</h2>
+<h1>Creating a new cave in the online system</h1>
+
+<h2>Great, I have discovered a new cave...</h2>
+<p>So, you have staggered off the plateau with a fist-full of notes and surveys, 
+and you want to let the world know of your massive discovery.
+<ul>
+<li>If you have not yet learned how to record your prospecting and survey 
+your leads, read the <a href="../look4.htm">prospecting introduction</a> and
+<a href="../survey/index.htm">survey handbook</a> which tells you how to record 
+survey information in your waterproof notebook. But first you should read the
+<a href="/expofiles/presentations/cave_surveying_20130626.pdf">
+Cave Surveying training course slidepack</a>.
+
+<li>This page outlines the rest of the process. Each part of it is documented separately.
+</ul>
+<h2>Process</h2>
+<p>After 40 years or so, we have a well-defined process which you will need to learn. 
+Read <em>all</em> this list first, then follow 
+the instructions section by section which tell you how to
+actually do these things.
+
+<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 (see <a href="#onlinew">below</a> for the filenames to use and <a href="#scan">how to use the scanner</a>)
+<li>Type in survey data (in the right place in the file system) in <a href="#survexformat">survex format</a>.<br>
+(This includes passage descriptions and open leads known as QMs: Question Marks).
+<li>Run survex to create a centre-line printout
+<li>Transcribe your sketches onto centre-line paper
+<li>Scan your centre-lined sketches
+<li>Use tunnel to digitise your centre-line sketches
+</ul>
+<p>and either later or at the same time, you will be doing these other tasks
+<ul>
+<li>Create a new folder in the file system for the wallet data 
+<li>Create a new folder in the file system for the survex data 
+<li>Create a "new cave entry" for the guidebook description 
+<li>Write the <b>full cave description</b> into the correct html files. <br>
+(This will mean copying the passage descriptions from the survex files.)
+<li>Update the index tick boxes on paper: as your wallet progresses through this process
+<li>Update the online record of those tick boxes
+<li>Regenerate the <a href="/expofiles/surveyscans/2018/">list of outstanding survey tasks</a> for everyone
+</ul>
+<p>This documentation assumes that you have recorded your survey data in 
+a  waterproof paper notebook. If instead you are using a PDA to record the survey readings
+digitally for your first cave, don't. Use the paper process first, then when you are familiar 
+the overall process, look at the <a href="pdanotes.html">PDA additional notes</a>.
+
+<h3 id="newwallet">Starting a new wallet</h3>
+<ol>
+<li>Put all your written notes into the next empty "wallet": 
+(a transparent folder/envelope) in this year's lever-arch file labelled 
+e.g. "Expo Survey 2018" in the potato hut*.
+<li>The wallet has a paper sticky label on it with the wallet-identifier, 
+e.g. <b>2018#22</b>, already printed on the label.
+<li>Write the date and the names of the people on the trip on the label.
+<li>Tick whether your trip was a surface or a cave trip.
+<li>Write the name of the cave  (with number if you know it), e.g. "264 Balkon"
+<li>Write the area in the cave you did your surveying, e.g. "mongol rally"<br>
+<li>Now turn to the index sheets at the front of the folder, 
+and fill in the line (e.g. 2018#22) for your wallet
+<ul>
+<li>"264 mongol rally"
+<li>date of trip
+<li>people who were on it
+<li>then there are a lot of tick boxes. The explanations for these will come later.
+</ul>
+<li>Now, if you have not done it immediately after you left the cave,
+photograph all the pages of survey notes with your phone. 
+Get one or more of the people also on the trip to do this too.
+</ol>
+
+<p>* As people spend longer and longer at top camp, we may establish 
+a wallet file at top camp
+too, with pre-allocated numbers.
+
+<p>The original notes and sketches should be filed in the clearly marked
+wallet. Rip them out of the notebook, don't take them caving again and <em>don't leave them lying around to
+be "G&ouml;ssered"!</em></p>
+
+<p>The notes (all of them, including dates, personnel, calibration, LRUD,
+station details, etc.) should be filed away in the wallet in the current year's
+surveys file. You should include a transcription on a sheet of paper 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
+marginally legible). This should be proof checked by someone else. Current
+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
+"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.</p>-->
+
+<h3 id="onlinew">Scan the notes into the online wallet</h3>
+
+<p>Each wallet has a corresponding folder in the online system where a record is kept
+of what information is in the wallet and where the corresponding survey data is filed:
+<pre>
+/expofiles/surveyscans/2018/2018#22/
+</pre>
+
+
+<p>This is where the scanned (or photographed) copies of the survey notes are kept.
+<p id="scan">To use the scanner attached to the <em>expo laptop</em>, select the "Simple Scan" 
+icon from the vertical menu of icons which you get by clicking on 
+"Activities" in the top lefthand corner of the screen. 
+
+<p style="margin-left:20px">[ Normal people should skip this, <br>&nbsp;
+but nerds need to look here 
+for the <a href="onlinewallet.html">online wallet maintenance process</a> ]. 
+
+<p>If your initial backup photos of your notes were poor quality, use the 
+scanner in the potato hut to make better copies. Scan to JPEG format as .jpg files.
+<p>Name the scanned pages "<em>notes1.jpg</em>, <em>notes2.jpg</em>" etc. This is important as a script detects whether these files exist
+and if you name them something else it will hassle you unnecessarily.
+
+<p>Scanned survey notes are voluminous and so are not kept in the version control system. Instead it is all kept
+in the file bucket "expofiles" on the expo server in Cambridge.
+<p>You will be using the expo laptop to do the scanning 
+and you will put all the scan files in the folder for your wallet, e.g. for 2018#19 it is:
+<pre>
+/home/expo/expofiles/surveyscans/2018/2018#19/
+</pre>
+and tell someone nerdy when you have finished and they will 
+ensure that it is copied to the expo server. 
+[ If you want to do this yourself, or are using your own laptop, then learn how to use Filezilla
+- as <a href="../uploading.html">documented for uploading your expo photographs</a>. The correct folder
+on the expo server is the same as that on the expo laptop- because we set up the expo laptop to be like that.
+But <em>only copy files to the server that you created yourself and which live in your own wallet folder</em> ]
+
+<h3 id="runsurvex">Storing your electronic survey files</h3>
+<p>If you used a PDA instead of making notes on paper, you need to store your .topo files in the right place.
+
+<p>If you using the expo laptop you can put the .topo files in a special "X" folder for your virtual 
+wallet, as there is no physical wallet, 
+e.g. for 2018#X16 it would be:
+<pre>
+/home/expo/expofiles/surveyscans/2018/2018#X16/
+</pre>
+and tell someone nerdy when you have finished and they will 
+ensure that it is copied from the <em>expo laptop</em> to the expo server. 
+
+<p>[ If all else fails, use the "Upload your photos" documented process and store 
+the .topo files where you would have stored your .jpg photo files. Otherwise you can email all the .topo files
+to a friendly nerd who will put them in the right place. ]
+<p><em>to be further documented - probably in a separate page</em>
+
+<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="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 whcih is why we are only 
+telling them to use the <em>expo laptop</em>.] 
+
+
+<h3 id="runsurvex">Running survex to create a centre-line</h3>
+<p><em>to be documented</em>
+
+
+
+<h3>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:
+<pre>
+/home/expo/expofiles/surveyscans/2018/2018#19/
+</pre>
+
+<h3>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 //tunneldata//.
+
+<h3>Interim rigging guide</h3>
+<p>The logbook is the place where we record the rigging of caves as we discover them.
+<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.</p>
+
+<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 troggle 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 />
+
+<ul id="links">
+<li><a href="../index.htm">Expedition Handbook</a>
+<li><a href="index.htm">Survey Handbook</a>
+</ul>
+</body>
+</html>

handbook/survey/onlinewallet.html

@@ -0,0 +1,275 @@
+<html>
+<head>
+<title>Survey Handbook - online wallet</title>
+<link rel="stylesheet" type="text/css" href="../../css/main2.css" />
+</head>
+<body>
+<h2 id="tophead">CUCC Expedition Handbook</h2>
+<h1>Maintaining the online wallets</h1>
+<p>If you are a newcomer to the system, read the <a href="newcave.html#onlinew">beginners introduction to online wallets</a> first.
+
+<h3>Why we have online wallets</h3>
+<p>There are three quite different reasons:
+<ol>
+<li>The scans of the survey notebook pages are the ultimate original raw survey data and completely irreplaceable.
+<li>The other files in the wallet are part of the process of producing a survey of the cave as a whole.
+<li>Individual to-do lists are produced automatically for each caver listing what survey processing tasks they haven't finished yet.
+</ol>
+
+<h3>The scanned pages</h3>
+<p>These are simply the scanned imaages (or digital photographs) of each page of the original survey notes. 
+They should be named <em><span style="font-family:monospace">notesXXX.jpg</span></em> where "XXX" can be 
+anything you like. Typically we have the scanned pages called notes1.jpg, notes2.jpg, notes3.jpg.
+<p>It is important that you use use the .jpg (JPEG) file format, and definitely not PNG (very voluminous) 
+or PDF (very hard to re-use elsewhere). Set the scanner at 300 dpi and adjust the contrast of the image after scanning
+by using photo-editing software to enhance the writing. Also please crop each image to just the area containing 
+the survey data.
+<p>As soon as the notes have been scanned you should (a) copy them to a USB stick or email them to someone, (b) upload the entire online wallet to the expo server in Cambridge 
+<span style="font-family:monospace">expo.survex.com</span>. This is so that these precious files are backed-up as soon as possible.
+
+<h3>The other files and online index <em><span style="font-family:monospace">contents.json</span></em></h3>
+<p>All the other files are part of the multi-step process of producing the cave survey - see <a href="newcave.html">
+Creating a new cave...</a> for the full list of steps.
+
+<p>We keep an index of how many of those steps have been completed in two places:
+<ul>
+<li>On paper, in the tick boxes in the contents list of this years' survey trips' lever-arch file in the potato hut.
+<li>Online in the <em><span style="font-family:monospace">contents.json</span></em> file which exists in each trip online wallet.
+</ul>
+
+<p>but the  <em><span style="font-family:monospace">contents.json</span></em> file has another,completely different function:
+it is the <b>only online record</b> that connects the wallet number to the cave identifier. So if a future cave surveyor deperately needs
+to consult the original cave survey, it can be done by, e.g. <br>
+<span style="font-family:monospace">
+grep -rl "2018-dm-07" expofiles/surveyscans
+</span><br>
+will find and list all the wallets which contain survey data for cave 2018-dm-07 (which is also known as "Homecoming Cave" and which will
+have a different Austrian Kataster number issued for it in due course).
+
+<p> The paper tick-list tracks the following steps for each online wallet:
+<ul>
+<li><u>Survex</u>
+<ul>
+<li>Data
+<li>LRUD
+<li>Description + QMs
+</ul>
+<li><u>Drawn</u>
+<ul>
+<li>Plan + Xsections
+<li>Elevation
+</ul>
+<li><u>Scanned</u>
+<ul>
+<li>In cave notes
+<li>Plan + Xsections
+<li>Elevation
+</ul>
+
+<li>Tunnel
+<li>Online guidebook updated
+<li>json file edited
+</ul>
+<p>(where the "json file updated" step only refers to the initial editing of the json file to ensure 
+that it has the right people, date and cave identifier and name).
+
+<p>A fully-populated and complete <em><span style="font-family:monospace">contents.json</span></em> file
+looks like this:
+<pre>
+{
+ "description written": false, 
+ "website updated": false, 
+ "people": [
+    "Dickon Morris",
+    "Jon Arne Toft",
+    "Becka Lawson"], 
+ "elev not required": false, 
+ "cave": "2018-dm-07", 
+ "survex not required": false, 
+ "qms written": true, 
+ "plan not required": false, 
+ "electronic survey": false, 
+ "plan drawn": true, 
+ "date": "2018-07-13", 
+ "elev drawn": true, 
+ "description url": "", 
+ "survex file": "caves-1626/2018-dm-07/2018-dm-07.svx", 
+ "name": "Homecoming cave"
+}
+</pre>
+Yes, this is <a href="https://en.wikipedia.org/wiki/JSON">a programming format</a>
+  (standardised in 2013) and every comma is critical.
+
+<h3>"To do" lists for every caver</h3>
+<p>The folder containing all the wallets for the year, e.g.
+<pre>
+/home/expo/expofiles/surveyscans/2018/
+</pre>
+will, after the appropriate magic has happened, contain a file 
+<pre>
+index.html
+</pre>
+which lists all the wallets which have uncompleted tasks, and lists all the people responsible for completing them. 
+You can see <a href="../../../expofiles/surveyscans/2016/index.html">the  index.html for 2016</a> 
+(most of these have been done, but the index has not been updated). Also there will be a linked file for each individual 
+for their personal to-do list, and each online wallet contains its own 
+<span style="font-family:monospace">index.html</span> file which  describes the survey production status for all the wallets.
+
+<p>All this magic is created by a script <span style="font-family:monospace">make.py</span>. 
+
+<h3>Setting up the online wallets</h3>
+<p>When, at the beginning of expo, you create the folder in
+<span style="font-family:monospace">expofiles/surveyscans/</span> for the current year, e.g. 
+<span style="font-family:monospace">/2018/</span>, you will copy <span style="font-family:monospace">make.py</span> 
+from the previous year's folder. You will do this on your own laptop or on the expo laptop.
+<p>You will also manually create a number of subfolders, e.g. 2018#01, 2018#02 etc. to be ready for the influx of
+new trip surveys.
+<p>Next you will test that the magic works: open a terminal in 
+<span style="font-family:monospace">expofiles/surveyscans/2018/</span> and run
+<pre>
+python make.py
+</pre>
+<p>which will work immediately without errors because you are using Linux and the 
+correct version of python is already installed.
+<p>This will create a default <span style="font-family:monospace">contents.json</span> and
+<span style="font-family:monospace">index.html</span> in each online wallet folder and also a 
+<span style="font-family:monospace">index.html</span> in the /2018/ folder.
+
+<h3>Maintaining the online wallets</h3>
+<p>Ideally the cavers who are scanning their notes and typing in the survey data will also be updating the 
+<span style="font-family:monospace">contents.json</span> file in their wallet. In your dreams.
+
+<p>The first difficulty when editing a blank <span style="font-family:monospace">contents.json</span> 
+for a newly-created wallet is finding out which cave the wallet describes. 
+The wallet may say "radaghost to blitzkriek"
+(or whatever) but without the name of the cave you can't find the .svx files 
+as you don't know that you need to look in e.g. loser/caves-1626/2018-dm-07/.
+Usually the cave number is written by hand on the label of the wallet. Sometimes it will just give the 
+informal name of the cave,e.g. "Homecoming",instead of the identifier "2018-dm-07" you want.
+<p>A regular task during expo is for a nerd to review the <span style="font-family:monospace">contents.json</span> files for
+recently created wallets and to check that names, dates and cave numbers are correct.
+
+You will run 
+<pre>
+python make.py
+</pre>
+regularly, after every batch of survey data is entered or scanned. 
+<p>This will always overwrite all the <span style="font-family:monospace">index.html</span> files but it will never touch
+the <span style="font-family:monospace">contents.json</span> files.
+<p>You will also regularly synchronise your laptop
+and the expo laptop with <span style="font-family:monospace">expo.survex.com/expofiles/surveyscan/2018/</span>
+and this is where it gets tricky.
+<p><span style="font-family:monospace">expo.survex.com/expofiles/</span> is not under version control, 
+so the most recent person
+to upload the contents of <span style="font-family:monospace">/2018/</span> will overwrite everyone else's work. 
+This does not matter for the autogenerated files, but it is vital that it does not overwrite all the painfully manually edited
+<span style="font-family:monospace">contents.json</span> files. Which is very easy to do.
+This does mean that this is one of the cases where 
+it is better to use <span style="font-family:monospace">rsync</span> rather than an FTP client such as Filezilla.
+
+<p>A copy of useful rsync scripts is kept in a file such as 
+<span style="font-family:monospace">expo.survex.com/expofiles/rsync2018toserver</span>. Always run it with the -n option first,
+to see what overwriting you will do.
+
+<h3>More <em><span style="font-family:monospace">make.py</span></em> magic</h3>
+<p>The python script does more than just re-format the <span style="font-family:monospace">contents.json</span> data into
+different formats. It also 
+<ul>
+<li>checks whether the .svx files listed are actually present,
+<li>checks for the presence of notesXXX.jpg, planXXX.jpg and elevXXX.jpg files
+<li>creates a template <span style="font-family:monospace">contents.json</span> in any wallet which does not have one.
+</ul>
+
+<p>Things it might do in future (if someone gets around to it) include: <br>
+- checking the cave number specified matches the folder for the .svx file,<br>
+- detecting whether there is a description or a list of QMs in the survex file,<br>
+- accepting a list of .svx files and not just one (a very common thing),<br>
+- checking the name of the cave against the cave number,<br>
+- checking whether the website page even exists for this cave,<br>
+- being more intelligent about .topo files and thus the lack of scan files,<br>
+- checking the date is in the recent past etc.<br><br>
+
+<h3>How <em><span style="font-family:monospace">contents.json</span></em> fields match 
+<em><span style="font-family:monospace">index.html</span></em> reports</h3>
+<p>
+<em>to be written...</em>
+<hr>
+Old notes, being turned into real documentation...
+<pre>
+# Instructions
+# 2018-08-14
+# Philip Sargent
+
+
+Wookey told me to sort out the contents.json files in expofiles/surveyscans/2018/
+and these are my notes to remind myself what this entails.
+
+The job is to populate the contents.json file in each folder, e.g.
+
+expofiles/surveyscans/2018/2018#03/contents.json
+
+using the following input materials:
+- the wallet 2018#03 and the papers inside it. This is in the 2018 lever-arch file.
+- the folder in repo 'loser' holding the appropriate .svx files e.g.
+  "caves-1623/2017-cucc-24/gshclimb.svx"
+- the script expofiles/surveyscans/2018/make.py (run by "python make.py")
+
+the "make.py" script creates index.html files in each folder /2018/2018#nn/
+and creates or updates a webpage for each person listed in any of the contents.json files
+in the folder/2018/ e.g. "Becka Lawson.html".
+
+The script make.py requires that the //loser// repo is populated on the machien that you
+run the script on so that it can find the.svx files. Do not run this script on
+the expo server itself as the loser repo is in the wrong place and all the .svx files
+will be flagged as "not found" (Paul Fox did this once).
+
+Before doing anything else, run make.py. This will create empty template contents.json
+files in each folder.
+
+You may need to create missing folders,e.g. I just had to create /2018/2018#30 to #32.
+
+Every time you finish entering the data in contents.json in a folder, 
+run make.py to update the "person" html files and to 
+re-generate the index.html file for the 2018 folder as 
+a whole (surveyscans/2018/index.html).
+
+There are ambiguities about how the entries in the contents.json actually lead to
+reminder instructions in the html files produced, and this is particularly
+difficult for electronic caves where the topo files are missing
+and for surface prospecting where it is not clear which of the actions
+should be done and thus which products should be produced.
+
+This needs to be documented.
+
+For prospecting and surface surveying it is not clear whether the default folder
+for the url link should be repo //loser// surface/1623/allplateau.svx
+
+When there are more than one .svx file there seems to be no way of recording the list 
+in contents.json so it is impossible to tell what was done on that trip or whether
+there is anything missing. This is especially true if it was electronic and the 
+.topo files are missing. Wookey confirms that this is the case.
+
+NAMING
+The script detects if there are notesX.jpg planX.jpg and elevX.jpgfiles present, and 
+produces a reminder/warning if they are not,even if these have all been scanned 
+and given different names.
+
+The job of the checker (perhaps on a second pass) if to rename files so that these
+warnings disappear. 
+
+HINT
+When there are a lot on wallets all with the same cave, make your own template
+with the cave name and the right folder prefix for the svx folder 
+(in the loser repo) and copy it in to all those wallet folders - overwriting 
+the blank template produced by the make.py
+
+
+
+
+</pre>
+
+
+<hr />
+
+</body>
+</html>

handbook/survey/ontop.htm

@@ -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

handbook/survey/pdanotes.html

@@ -0,0 +1,23 @@
+<html>
+<head>
+<title>Survey Handbook</title>
+<link rel="stylesheet" type="text/css" href="../../css/main2.css" />
+</head>
+<body>
+<h2 id="tophead">CUCC Expedition Survey Handbook</h2>
+<h1>PDA additional notes</h1>
+<p>This is where you learn how to use a PDA with the CUCC expo survey process instead of using pencil and notebook.
+<p>This will be replaced with the information you want as soon as someone gets around to writing it. 
+Why not find out how to do this yourself ?
+
+
+<hr />
+
+<ul id="links">
+<li><a href="../index.htm">Expedition Handbook</a>
+<li><a href="newcave.html">Registering a new cave process</a>
+<li><a href="index.htm">Expo Survey Handbook</a>
+
+</ul>
+</body>
+</html>

handbook/survey/status.html

@@ -0,0 +1,29 @@
+<html>
+<head>
+<title>Expo server</title>
+<link rel="stylesheet" type="text/css" href="../css/main2.css" />
+</head>
+<body>
+<h2 id="tophead">CUCC Expedition Handbook - status of surveys</h2>
+<h1>Current status of surveying during expo</h1>
+
+<h3>How do I.. find out the progress of surveying during expo?</h3>
+
+<p>You simply look online at <br>
+
+<a href="http://expo.survex.com/expofiles/surveyscans/2018/index.html"><b>/expofiles/surveyscans/2018/</b></a>
+<br>
+
+replacing "2018" with whatever year you want to check up on.
+<p>Then scroll down to check the list against your own name, or the status of the particular wallet
+you want to know about.
+<p>The online wallet system and how it works are <a href="newcave.html#onlinew">well documented in the survey handbook</a>.
+
+
+<hr />
+
+<ul id="links">
+<li><a href="index.htm">Expedition Handbook</a>
+</ul>
+</body>
+</html>

handbook/survey/why.htm

@@ -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

handbook/travel.html

@@ -106,12 +106,15 @@ the <a href="http://www.openstreetmap.org/?mlat=47.61616&mlon=13.81218#map=19/47
 	fields on the left, keeping left at the only junction, then
 	past a petrol station).  After about 20 minutes you'll reach
 	the main 3-way "roundabout" junction in the centre of town
-	mentioned above.  You are now at the Post Office ("Postampt") which is on your left as you have walked from the station..
+	mentioned above.  You are now at the Post Office ("Postampt") 
+which is on your left as you have walked from the station..
 
 
 <p>If you walk this far and now want to get the bus, you can also catch the 956 bus from here. 
 The bus stop you want is on the opposite side of the road from the Post Office building. 
 Take the 956 which is the only bus that goes to Grundlesee. 
+This  <em>may be replaced by an anonymous 
+white minibus</em> with a taxi company logo. Don't get caught out by not getting onto it.
 The jouney takes 6 minutes and 'Staudnwirt Gallhof' is the 4th stop. 
 However there are only 8 buses a day in July and August (outside school term). 
 They leave the Post Office (2018) at 

handbook/update.htm

@@ -1,373 +1,122 @@
 <html>
 <head>
-<title>CUCC Expedition Handbook: The Website</title>
+<title>CUCC Expedition Handbook: Online system overview</title>
 <link rel="stylesheet" type="text/css" href="../css/main2.css" />
 </head>
 <body>
-<h2 id="tophead">CUCC Expedition Handbook</h2>
-<h1>Expo Website Manual</h1>
-<p>The website is now large and complicated with a lot of aspects. 
+<h2 id="tophead">CUCC Expedition Handbook - Online systems</h2>
+<h1>Expo Online Systems Overview</h1>
+<p>The online data system and webinterface is now large and complicated with a lot of aspects. 
 This handbook section contains info at various levels: 
 simple 'How to add stuff' information for the typical expoer, 
 more detailed info for cloning it onto your own machine for more significant edits, 
 and structural info on how it's all put together for people who want/need to change things. 
-[This manual is now so big that it is being restructured and split up. Much of it is obsolete.]</p>
 
-<p>We have <a href="http://wookware.org/talks/expocomputer/#/">an Overview Presentation</a> on how the cave data, handbook and website are constructed and managed. It contains material which will be merged into this website manual.
+
+<p>We have <a href="http://wookware.org/talks/expocomputer/#/">an Overview Presentation</a> (many parts out of date)
+on how the cave data, 
+handbook and public website are constructed and managed. 
+It contains material which will be merged into this online systems manual.
 
 <ul>
 <li><a href="uploading.html">Uploading your photos</a></li>
 <li><a href="logbooks.html">Uploading typed logbooks</a></li>
 <li><a href="gpxupload.html">Uploading GPS tracks</a></li>
-<li><a href="#update">Updating the website</a></li>
-<li><a href="#manual">Expo Website manual</a></li>
+<li><a href="manual.html#update">Updating the guidebook descriptions and handbook</a></li>
+<li><a href="manual.html#manual">Expo software and server maintenance manual</a></li>
 </ul>
 
-<h2><a id="update">Updating the website - overview</a></h2>
+<h2><a id="update">Updating the online systems - overview</a></h2>
 
-<p>Short <a href="checkin.htm">command-line instructions</a> for updating the website
-(on the expo machine). This is a memory jog for experts, not beginners.</p>
+<h3>Experts short cut</h3>
 
-<p>You can update the site via the troggle pages, by editing pages
-online via a browser ("Edit this page" on the menu on the left), by
-editing them on the server remotely, or by checking out the relevant part to
-your computer and editing it there. Which is best depends on your
-knowledge and what you want to do. For simple addition of cave or
-survey data troggle ("edit this page") is recommended. For other edits it's best if you
-can edit the files directly but that means you either need to be on expo with the expo
-computer, or be able to check out a local copy using the version control system. If neither of these
-apply then using the 'edit this page' button is fine.</p>
+<p>Short <a href="checkin.htm">command-line instructions</a> for updating the
+data on the server
+(using the <em>expo laptop</em>). This is a memory jog for experts, not beginners.</p>
 
-<p>It's important to understand that everything on the site (except things under 
-'expofiles') is stored in a distributed version control system (DVCS)
-which means that every edited
-file needs to be 'checked in' after editing. The Expo website manual
-goes into more detail about this, below. This stops us losing data and
-makes it very hard for you to screw anything up permanently, so don't
-worry about making changes - they can always be reverted if there is a
-problem. It also means that several people can work on the site on
-different computers at once and normally merge their changes
-easily.</p>
-
-<p>Increasing amounts of the site are autogenerated by <a href="#troggle">troggle</a>, and are not static files,
+<h3>Autogenerated pages</h3>
+<p>Some key sections of the online webpages  are autogenerated by 
+<a href="#troggle">troggle</a>, and are not static files,
 so you have to edit the base data, not the generated file (e.g cave
 pages, QM (question mark) lists, expo members list, prospecting pages). All
 autogenerated files say 'This file is autogenerated - do not edit' at
 the top - so check for that before wasting time on changes that will
 just be overwritten</p>
 
-<h3 id="troggle">Troggle - what it is</a></h3>
-<p>
-Troggle is a system under development . 
-<p>
-Troggle is the software collection (not really a "package") based on <a href="https://www.djangoproject.com/">Django</a>  
-for keeping track of all expo data in a logical and accessible way, and displaying it on the web.
-It also re-formats HTML web pages (such as the Expo Handbook) to create useful links 
-(such as "Edit this page" in the left hand menu of this page that you are reading - if you are a logged-on user).
-<p>See the <a href="http://www.srcf.ucam.org/caving/wiki/Troggle">Troggle page on the CUCC website</a> - which is not up to date.
+<h3>Using "Edit this page"</h3>
+
+<p>You can update the site via the troggle pages, by editing pages
+online via a browser ("Edit this page" on the menu on the left), by
+editing them on the server remotely, or by checking out the relevant part to
+your computer and editing it there. Which is best depends on your
+knowledge and what you want to do. For simple addition of cave or
+survey data troggle ("edit this page") is recommended. (For other edits it's best if you
+can edit the files directly but that means you either need to be on expo with the expo
+computer, or be able to check out a local copy using the version control system - 
+see the <a href="manual.html#manual">Expo software and server maintenance manual</a>. If neither of these
+apply then using the 'edit this page' button is fine.</p>
+
+<p>It's important to understand that the pages you can edit by this method 
+are stored in a distributed version control system (see below). This stops us losing data and
+makes it very hard for you to screw anything up permanently, so don't
+worry about making changes - they can always be reverted if there is a
+problem. It also means that several people can work on the site on
+different computers at once and normally merge their changes
+easily.
+
+<p>After doing this, you need to ask a nerd to finish the process fairly soon as the "Edit this page"
+mechanism does not tidy-up after itself properly. 
+See <a href="manual.html#editthispage">these instructions for this tidy-up</a>
+
+
+
+
+<h3><a id="surveystatus">Maintaining the status of new surveys being drawn up</a></h3>
+
+<p>This is managed in this years' folder in e.g.
+<pre>
+expofiles/surveyscans/2018/
+</pre> 
+and is documented in the <a href="survey/newcave.html">New Cave survey data entry</a>
+manual pages.
+
 
 <h3 id="mercurial">DVCS - version control</a></h3>
-<p>We use a distributed revision control system (DVCS) for all the important data.  On expo this means that many people can edit and merge their changes with the expo server in the Tatty Hut even if there is no internet access.  Also anyone who is up to date with the  Tatty Hut can take their laptop somewhere where there is internet access and update expo.survex.com - which will then get all the updates done by everyone on expo.
+<p>We use a distributed revision control system (DVCS) for all the important data.  
+On expo this means that many people can edit and merge their changes with the expo 
+server in the Tatty Hut even if there is no internet access.  Also anyone who is up 
+to date with the  Tatty Hut can take their laptop somewhere where there is internet 
+access and update expo.survex.com - which will then get all the updates done by everyone on expo.
 </p>
-<p>In principle, survey notes can be typed into a laptop up on the plateau which is then synchronised with the Tatty Hut on returning to base.
+<p>In principle, survey notes can be typed into a laptop up on the plateau which is 
+then synchronised with the Tatty Hut on returning to base.
 </p>
-<p>A DVCS is inefficient for scanned survey notes, which are large files that do not get modified, so they are kept as a plain directory of files 'expofiles'. The same goes for holiday photographs and GPS logs.</p>
+<p>A DVCS is inefficient for scanned survey notes, which are large files that 
+do not get modified, so they are kept as a plain directory of files 'expofiles'. 
+The same goes for holiday photographs and GPS logs.</p>
 
-<h2><a id="manual">Expo website manual</a></h2>
 
-<p>Editing the expo website is an adventure. Until 2007, there was no
-guide which explained the whole thing as a functioning system. Learning
-it by trial and error is non-trivial. There are lots of things we
-could improve about the system, and anyone with some computer nous is
-very welcome to muck in. It is slowly getting better organised.</p>
 
-<p>This manual is organized in a how-to sort of style. The categories,
-rather than referring to specific elements of the website, refer to
-processes that a maintainer would want to do.</p>
-<p>Note that to display the survey data you will need a copy of the survex software.
 
-<h3>Contents</h3>
 
-<ol>
-<li><a href="#usernamepassword">Getting a username and password</a></li>
-<li><a href="#repositories">The repositories</a></li>
-<li><a href="#howitworks">How the website works</a></li>
-<li><a href="#quickstart">Quick start</a></li>
-<li><a href="#editingthewebsite">Editing the website</a></li>
-<li><a href="#Mercurialinwindows">Using version control software in Windows</a></li>
-<li><a href="#expowebupdate">The expoweb-update script</a></li>
-<li><a href="#cavepages">Updating cave pages</a></li>
-<li><a href="#updatingyears">Updating expo year pages</a></li>
-<li><a href="logbooks.html">Adding typed logbooks</a></li>
-<li><a href="uploading.html">Uploading photos</a></li>
-<li><a href="#tickingoff">Ticking off QMs</a></li>
-<li><a href="#surveystatus">Maintaining the survey status table</a></li>
-<li><a href="#automation">Automation</a></li>
-<li><a href="#arch">Archived updates</a></li>
-</ol>
-Appendices:
-<ul>
-<li><a href="website-history.html">History of the website</a></li>
-</ul>
+<h3 id="troggle">Troggle - what it is</a></h3>
+ 
+<p>
+Troggle is the software collection (not really a "package") based on <a href="https://www.djangoproject.com/">Django</a>  
+originally intended to manage all expo data in a logical and accessible way 
+and displaying it on the web.
+<p>Only a small part of troggle's original plan was fully implemented and deployed: that bit which
+re-formats HTML web pages (such as the Expo Handbook). Troggle creates the contents index on every page
+and provides the 
+"Edit this page" capability and provides some help in creating online guidebook descriptions 
+for the caves. (You can see "Edit this page" in the left hand menu of this 
+page that you are reading if you are a logged-on user.)
+<p> Once you have edited the page you need to 
+update the server's local repo copies, by ssh into the server and running hg update in the expoweb folder. 
+Otherwise nobody else can use your changes via the repo mechanism even though they are pubished by the webserver</p>
 
-<h3><a id="usernamepassword">Getting a username and password</a></h3>
-
-<p>Use these credentials for access to the site. The user is 'expo',
-  with a cavey:beery password. Ask someone if this isn't enough clue for you.
-  <b>This password is important for security</b>. The whole site <strong>will</strong> get hacked by spammers or worse if you are not careful with it. Use a secure method for passing it on to others that need to know (i.e not unencrypted email), don't publish it anywhere, don't check it in to the website by accident. A lot of people use it and changing it is a pain for everyone so do take a bit of care.
-</p>
-
-<p>Note that you don't need a password to view most things, but you will need one to change them</p>
-
-<h3><a id="repositories">The repositories</a></h3>
-
-<p>All the expo data is contained in 4 "repositories" at
-expo.survex.com. This is currently hosted on a server at the university. We use a distributed version control system (DVCS) to manage these repositories because this allows simultaneous collaborative editing and keeps track of all changes so we can roll back and have branches if needed.</p>
-
-<p>The site has been split into four parts:</p>
-
-<ul>
- <li><a href="http://expo.survex.com/repositories/home/expo/expoweb/graph">expoweb</a> - the website itself, including generation scripts</li>
- <li><a href="http://expo.survex.com/repositories/home/expo/troggle/graph/">troggle</a> - the database-driven part of the website</li>
- <li><a href="http://expo.survex.com/repositories/home/expo/loser/graph/">loser</a> - the survex survey data</li>
- <li><a href="http://expo.survex.com/repositories/home/expo/tunneldata/graph/">tunneldata</a> - the tunnel (and therion) data and drawings</li>
-</ul>
-
-
-<p>All the scans, photos, presentations, fat documents and videos are
-stored just as files (not in version control) in 'expofiles'. See
-below for details on that.</p>
-
-<h3><a id="howitworks">How the website works</a></h3>
-
-<p>Part of the website is static HTML, but quite a lot is generated by scripts. So anything you check in which affects cave data or descriptions won't appear on the site until the website update scripts are run. This happens automatically every 30 mins, but you can also kick off a manual update. See 'The expoweb-update script' below for details.</p>
-
-<p>Also note that the website you see is its own Mercurial checkout (just like your local one) so that has to be 'pulled' from the server before your changes are reflected.</p>
-
-<h3><a id="editthispage">Using 'Edit This Page'</a></h3>
-<p>This edits the file served by the webserver (Apache) on
-expo.survex.com but it does not update the copy of the file in the
-repository in expo.survex.com. To properly finish the job you need to
-use putty to ssh into expo.survex.com and run "hg diff" (to check what
-changes are pending) and then "hg commit" in the directory
-/home/expo/expoweb .</p>
-
-<h3><a id="quickstart">Quick start</a></h3>
-
-<p>If you know what you are doing here is the basic info on what's where:<br>
-(if you don't know what you're doing, skip to <a href="#editingthewebsite">Editing the website</a> below.)
-
-
-<dl>
-    <dt>expoweb (The Website)</dt>
-    <dd>
-      <tt>hg clone ssh://expo@expo.survex.com/expoweb</tt> (read/write)<br />
-      <tt>hg clone http://expo.survex.com/repositories/home/expo/expoweb/</tt> (read-only checkout)
-    </dd>
-
-    <dt>troggle (The Website backend)</dt>
-    <dd>
-      <tt>hg clone ssh://expo@expo.survex.com/troggle</tt> (read/write)<br />
-      <tt>hg clone http://expo.survex.com/repositories/home/expo/troggle/</tt> (read-only checkout)
-    </dd>
-
-    <dt>loser (The survey data)</dt>
-    <dd>
-      <tt>hg clone ssh://expo@expo.survex.com/loser</tt> (read/write)<br />
-      <tt>hg clone http://expo.survex.com/repositories/home/expo/loser/</tt> (read-only)
-    </dd>
-
-    <dt>tunneldata (The Tunnel drawings)</dt>
-    <dd>
-      <tt>hg clone ssh://expo@expo.survex.com/tunneldata</tt> (read/write)<br />
-      <tt>hg clone http://expo.survex.com/repositories/home/expo/expoweb/</tt> (read-only)
-    </dd>
-</dl>
-<dl>
-    <dt>expofiles (all the big files and documents)</dt>
-
-<p>Photos, scans (logbooks, drawn-up cave segments) (This was about
-60GB of stuff in 2017 which you probably don't actually need locally).
-<p>If you don't need an entire copy of all 60GB, then it is probably best to use Filezilla to copy just a small part of the filesystem to your own machine and to upload the bits you add to or edit.
-Instructions for installing and using Filezilla are found in the expo user instructions for uploading photographs: <a href="uploading.html">uploading.html</a>.
-
-<p> To sync all
-the files from the server to local expofiles directory:</p>
-
-<p><tt>rsync -av expo@expo.survex.com:expofiles /home/expo</tt></p>
-
-<p>To sync the local expofiles directory back to the server (but only if your machine runs Linux):</p>
-<p><tt>rsync --dry-run --delete-after -a /home/expo/expofiles expo@expo.survex.com</tt></p>
-then CHECK that the list of files it produces matches the ones you absolutely intend to delete forever! ONLY THEN do:
-<p><tt>rsync -av /home/expo/expofiles expo@expo.survex.com:</tt></p>
-
-<p>(do be <b>incredibly</b> careful not to delete piles of stuff then rsync back, or to get the directory level of the command wrong - as it'll all get deleted on the server too, and we may not have backups!). It's <b>absolutely vital</b>Use rsync --dry-run --delete-after -a first to check what would be deleted. 
-
-<p>If you are using rsync from a Windows machine you will <em>not</em> get all the files as some filenames are incompatible with Windows. What will happen is that rsync will invisibly change the names as it downloads them from the Linux expo server to your Windows machine, but then it forgets what it has done and tries to re-upload all the renamed files to the server even if you have touched none of them. Now there won't be any problems with simple filenames using all lowercase letters and no funny characters, but we have nothing in place to stop anyone creating such a filename somewhere in that 60GB or of detecting the problem at the time. So don't do it. If you have a Windows machine use Filezilla not rsync.
-
-<p>(We may also have an issue with rsync not using the appropriate user:group  attributes for files pushed back to the server. This may not cause any problems, but watch out for it.)</p>
-</dl>
-<h3><a id="editingthewebsite">Editing the website</a></h3>
-
-<p>To edit the website fully, you need to use the disributed version control system (DVCM) software which is currently mercurial/TortoiseHg. Some (static text) pages can be edited directly on-line using the 'edit this page link' which you'll see if you are logged into troggle. In general the dynamically-generated pages, such as those describing caves which are generated from the cave survey data, can not be edited in this way, but forms are provided for some types of these like 'caves'.</p>
-
-<p>What follows is for Linux. If you are running Windows then see below <a href="#Mercurialinwindows">Using Mercurial/TortoiseHg in Windows</a>.
-
-<p>Mercurial can be used from the command line, but if you prefer a GUI, TourtoiseHg is highly recommended on all OSes.</p>
-
-<p>Linux: Install mercurial and tortoisehg-nautilus from synaptic,
-then restart nautilus <tt>nautilus -q</tt>. If it works, you'll be able to see the menus of tortoise within your Nautilus windows. </p>
-
-<p>Once you've downloaded and installed a client, the first step is to create what is called a checkout of the website. This creates a copy on your machine which you can edit to your heart's content. The command to initially check out ('clone') the entire expo website is:</p>
-
-<p><tt>hg clone ssh://expo@expo.survex.com/expoweb</tt></p>
-
-<p>for subsequent updates</p>
-
-<p><tt>hg update</tt></p>
-
-<p>will generally do the trick.</p>
-
-<p>In TortoiseHg, merely right-click on a folder you want to check out to, choose "Mercurial checkout," and enter</p>
-
-<p><tt>ssh://expo@expo.survex.com/expoweb</tt></p>
-
-<p>After you've made a change, commit it to you local copy with:</p>
-
-<p><tt>hg commit</tt>   (you can specify filenames to be specific)</p>
-
-<p>or right clicking on the folder and going to commit in TortoiseHg. Mercurial can't always work out who you are. If you see a message like "abort: no username supplied" it was probably not set up to deduce that from your environment. It's easiest to give it the info in a config file at ~/.hgrc (create it if it doesn't exist, or add these lines if it already does) containing something like</p>
-
-<p><tt>
-[ui]<br/>username = Firstname Lastname &lt;myemail@example.com&gt;
-</tt></p>
-
-<p>The commit has stored the changes in your local Mercurial DVCS, but it has not sent anything back to the server. To do that you need to:</p>
-
-<p><tt>hg push</tt></p>
-
-<p>Before pushing, you should do an <tt>hg pull</tt> to sync with upstream first. If someone else has edited the same files you may also need to do:</p>
-
-<p><tt>hg merge</tt></p>
-
-<p>(and sort out any conflicts if you've both edited the same file) before pushing again</p>
-
-<p>Simple changes to static files will take effect immediately, but changes to dynamically-generated files (cave descriptions, QM lists etc) will not take effect, until the server runs the expoweb-update script.</p>
-
-
-
-
-<h3><a id="Mercurialinwindows">Using Mercurial/TortoiseHg in Windows</a></h3>
-
-<p>Read the instructions for setting up TortoiseHG in <a href="tortoise/tortoise-win.htm">Tortoise-on-Windows</a>.
-<p>In Windows: install Mercurial and TortoiseHg of the relevant flavour from <a href="https://tortoisehg.bitbucket.io/">https://tortoisehg.bitbucket.io/</a> (ignoring antivirus/Windows warnings). This will install a submenu in your Programs menu)</p>
-
-<p>To start cloning a repository: first create the folders you need for the repositories you are going to use, e.g. D:\CUCC-Expo\loser and D:\CUCC-Expo\expoweb. Then start TortoiseHg Workbench from your Programs menu, click File -> Clone repository, a dialogue box will appear. In the Source box type</p>
-
-<p><tt>ssh://expo@expo.survex.com/expoweb</tt></p>
-
-<p>for expoweb (or similar for the other repositories). In the Destination box type whatever destination you want your local copies to live in on your laptop e.g. D:\CUCC-Expo\expoweb. Hit Clone, and it should hopefully prompt you for the usual beery password.
-
-<p>The first time you do this it will probably not work as it does not recognise the server. Fix this by running putty (downloading it from <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/">https://www.chiark.greenend.org.uk/~sgtatham/putty/</a>), and connecting to the server 'expo@expo.survex.com' (on port 22). Confirm that this is the right server. If you succeed in getting a shell prompt then ssh connection are working and TortoiseHg should be able to clone the repo, and send changes back.</p>
-
-
-<h3><a id="expowebupdate">The expoweb-update script</a></h3>
-
-<p>The script at the heart of the website update mechanism is a makefile that runs the various generation scripts. It is run every 15 minutes as a cron job (at 0,15,30 and 45 past the hour), but if you want to force an update more quickly you can run it he</p>
-
-<p>The scripts are generally under the 'noinfo' section of the site just because that has (had) some access control. This will get changed to something more sensible at some point</p>
-
-
-<h3><a id="cavepages">Updating cave pages</a></h3>
-
-<p>Cave description pages are automatically generated from a set of
-cave files in noinfo/cave_data/ and noinfo/entrance_data/. These files
-are named <area>-<cavenumber>.html (where area is 1623 or 1626). These
-files are processed by troggle. Use <tt>python databaseReset.py
-caves</tt> in /expofiles/troggle/ to update the site/database after
-editing these files.</p>
-
-<p>Clicking on 'New cave' (at the bottom of the cave index) lets you enter a new cave. <a href="caveentry.html">Info on how to enter new caves has been split into its own page</a>.</p>
-
-<p>(If you remember something about CAVETAB2.CSV for editing caves, that was 
-superseded in 2012).</p>
-<p>This may be a useful reminder of what is in a survex file <a href="survey/how_to_make_a_survex_file.pdf">how to create a survex file</a>.
-
-<h3><a id="updatingyears">Updating expo year pages</a></h3>
-
-<p>Each year's expo has a documentation index which is in the folder</p>
-
-<p>/expoweb/years</tt></p>
-
-<p>, so to checkout the 2011 page, for example, you would use</p>
-
-<p>hg clone ssh://expo@expo.survex.com/expoweb/years/2011</tt></p>
-
-<p> Once you have pushed your changes to the repository you need to update the server's local copies, by ssh into the server and running hg update in the expoweb folder. </p>
-
-<h3>Adding a new year</h3>
-<p>Edit noinfo/folk.csv, adding the new year to the end of the header
-line, a new column, with just a comma (blank
-cell) for people who weren't there, a 1 for people who were there, and
-a -1 for people who were there but didn't go caving. Add new lines for
-new people, with the right number of columns.</p>
-
-<p>This proces is tedious and error-prone and ripe for improvement.
-Adding a list of people, fro the bier book, and their aliases would be
-a lot better, but some way to make sure that names match with previous
-years would be
-good.</p>
-
-<h3><a id="tickingoff">Ticking off QMs</a></h3>
-
-<p>To be written.</p>
-
-
-<h3><a id="surveystatus">Maintaining the survey status table</a></h3>
-
-<p>There is a table in the survey book which has a list of all the surveys and whether or not they have been drawn up, and some other info.</p>
-
-<p>This is generated by the script tablizebyname-csv.pl from the input file Surveys.csv</p>
-
-
-<h3 id="automation">Automation on expo.survex.com</h3>
-
-<p>Ths section is entirely out of date (June 2014), and awaiting deletion or removal</p>.
-
-<p>The way things normally work, python or perl scripts turn CSV input into HTML for the website. Note that:</p>
-<p>The CSV files are actually tab-separated, not comma-separated despite the extension.</p>
-<p>The scripts can be very picky and editing the CSVs with microsoft excel has broken them in the past- not sure if this is still the case.</p>
-<p>Overview of the automagical scripts on the expo website</p>
-[Clearly very out of date is it is assuming the version control is svn whereas we changed to hg years ago.]
-<pre>
-Script location 	Input file 	Output file 	Purpose
-/svn/trunk/expoweb/noinfo/make-indxal4.pl 	/svn/trunk/expoweb/noinfo/CAVETAB2.CSV 	many 	produces all cave description pages
-/svn/trunk/expoweb/noinfo/make-folklist.py 	/svn/trunk/expoweb/noinfo/folk.csv 	http://expo.survex.com/folk/index.htm 	Table of all expo members
-
-/svn/trunk/surveys/tablize-csv.pl /svn/trunk/surveys/tablizebyname-csv.pl
-	/svn/trunk/surveys/Surveys.csv 	
-
-http://expo.survex.com/expo/surveys/surveytable.html http://expo.survex.com/surveys/surtabnam.html
-	Survey status page: "wall of shame" to keep track of who still needs to draw which surveys
-
-</pre>
-
-<h3><a id="arch">Archived updates</a></h3>
-<p>Since 2008 we have been keeping detailed records of all website updates in the version control system. 
-Before then we manually maintained <a href="../update.htm">a list of updates</a> which are now only of historical interest.
-
-<h2>The website conventions bit</h2>
- <p>This is likely to change with structural change to the site, with style changes which we expect to implement and with the method by which the info is actually stored and served up.</p>
-<p>... and it's not written yet, either :-)</p>
-<ul>
-
-<li>Structure</li>
-<li>Info for each cave &ndash; automatically generated by <tt>make-indxal4.pl</tt></li>
-<li>Contents lists &amp; relative links for multi-article publications like  journals. Complicated by expo articles being in a separate hierarchy from journals.</li>
-<li>Translations</li>
-<li>Other people's work - the noinfo hierarchy.</li>
-<li>Style guide for writing cave descriptions: correct use of boldface (<em>once</em> for each passage name, at the primary definition thereof; other uses of the name should be links to this, and certainly should not be bold.) </li>
-</ul>
+<p>See the outdated <a href="http://www.srcf.ucam.org/caving/wiki/Troggle">Troggle page 
+</a> for a snapshot of development some years ago.
 
 
 <hr />

handbook/uploading.html

@@ -11,9 +11,14 @@
 <h2>The end-result you are trying to achieve</h2>
 What you are trying to do is to get your happy holiday snaps appear properly indexed with all the others from the previous decades of expo history. You can see them all here: <br /> <a
 href="http://expo.survex.com/photos/">http://expo.survex.com/photos/</a><br />
-which is the end result. But all you have to do is to upload the photos to the right place. A hidden script does the hard work to make it all look nice.
+which is the end result. But all you have to do is to upload the photos to the right place. 
+A hidden script does the hard work to make it all look nice.
 
-<p>If you are really lazy (or really a beginner) you can use the initial simple method for the photos you have taken of cave entrances [for cave survey and prospecting purposes] so long as you label the filenames of the photos very carefully and tell an admin/nerd what you have done.
+<p>If you are really lazy (or really a beginner) you can use the initial simple method (using /uploads/ )
+for the photos  you have taken of cave entrances for cave survey and prospecting purposes. But please
+rename the filenames of the photos intelligently, e.g. "big-hole-near-path-to-fgh.jpg", or
+"2018-ad-07-entrance3.jpg" (rather than "DSC31415926.jpg"), and explain to an admin/nerd what you have done. 
+Please use lower-case for all filenames.
 
 <p>If you are looking for how to upload a GPS track, those instructions have <a href="gpxupload.html">been moved to here</a>.
 <h2>Simple instructions</h2>
@@ -60,7 +65,13 @@ directory: /home/expo/expofiles/<b>photos</b>/2018/YourName/
 </pre>
 
 <p>Obviously replace 'YourName' with your actual name (no spaces!). 
-It is important that you get this right as this specific way of writing your name is standardised across the website (this is known as "CamelCase"). 
+It is important that you get this right as this specific way of writing 
+your name is standardised across the website 
+(this is known as "<a href="https://en.wikipedia.org/wiki/Camel_case">CamelCase</a>"). 
+<p style="margin-left:20px">This is the only place in the whole system
+that you should use some capital letters. Absolutely everywhere else you should use
+only lower-case letters, no spaces, and hyphens (not underlines) when creating filenames, folder names or variable names of any sort.
+<p>
 Use the year that the photo was taken or the GPStrack logged.</p>
 
 <p>Note that uploading photos does not automatically update the view
@@ -84,13 +95,22 @@ mac and android with other tools. If you have Windows 10 and <a href="https://ms
 <p>screenshots:
 <a href="http://winscp.net/eng/docs/screenshots">http://winscp.net/eng/docs/screenshots</a></p>
 
+<!-- WedDAV no longer works because the effective user is "apache" and the permissions
+for the folder /uploads/ no longer allow it to write anything because we had to change it to allow Filezilla 
+to work.Philip & Wookey 11 August 2018
+
 <h3>Using WebDAV - cadaver</h3>
 <p>Command-line people can use the 'cadaver' client which is even
 available for windows too:
 <a href="http://www.phtagr.org/2009/04/01/cadaver-for-windows/">www.phtagr.org/2009/04/01/cadaver-for-windows/</a></p>
+-->
 
-<p>Both scp and cadaver give you an 'explorer-like' interface (although winscp can
+<p>scp gives you an 'explorer-like' interface (although winscp can
 give you a norton-commander-style 2-pane UI as well).</p>
+
+<h3>Using WebDAV</h3>
+This no longer works as we had to change the folder permissions for /uploads/. Sorry.
+
 <h3>Using rsync</h3>
 <p>No, don't use rsync for this. Really don't. It's too liable to delete everything or to overwrite files which are not changed at all because of the incompatibilities between Linux and Windows filename conventions (uppercase and lowercase are automagically converted and rsync gets it wrong).
 <hr />

handbook/website-history.html

@@ -7,6 +7,12 @@
 <h2 id="tophead">CUCC Expedition Handbook</h2>
 <h1>EXPO Data Management History</h1>
 
+<div style="text-align:left">
+<!-- Comment 
+Justified text is hard to read:
+https://designshack.net/articles/mobile/the-importance-of-designing-for-readability/
+https://designforhackers.com/blog/justify-text-html-css/
+-->
 <h2>History in review</h2>
 <p>
 Over 32 years, CUCC has developed methods for handling such information. Refinements in data 
@@ -117,7 +123,7 @@ university since Feb 2014. In 2018 we have 4 repositories, see <a href="update.h
 
 <p>In spring 2018 Sam, Wookey and Paul Fox updated the  Linux version and the Django version to 
 something vaguely acceptable to the university computing service and fixed all the problems that were then observed.
-
+</div>
 Return to<br>
 <a href="update.html">Website update</a><br>
 <a href="expodata.html">Website developer information</a><br>

handbook/zilla-uploads.xml

@@ -19,7 +19,7 @@
 			<Colour>0</Colour>
 			<LocalDir>/home/</LocalDir>
 			<RemoteDir>1 0 4 home 4 expo 9 expofiles 7 uploads</RemoteDir>
-			<SyncBrowsing>1</SyncBrowsing>
+			<SyncBrowsing>0</SyncBrowsing>
 			<DirectoryComparison>1</DirectoryComparison>
 			<Name>Expo-uploads</Name>Expo-uploads<Bookmark>
 				<Name>Expo-uploads</Name>
@@ -28,4 +28,7 @@
 			</Bookmark>
 		</Server>
 	</Servers>
+	<Settings>
+		<Setting name="Preserve timestamps">1</Setting>
+	</Settings>
 </FileZilla3>

infodx.htm

@@ -13,9 +13,10 @@
 <ul>
   <li><a href="indxal.htm">Cave Descriptions Index</a>.  Recently-explored major caves:
     <ul>
-    <li><a href="1623/40/cucc.htm">Schwarzmooskogeleish&ouml;hle</a></li>
+    <li><a href="1623/2017-cucc-28/">Fischgesicht </a></li>
     <li><a href="1623/258/258.html">Tunnockschacht</a></li>
     <li><a href="1623/264/264.html">Balkonh&ouml;hle</a></li>
+    <li><a href="1623/40/cucc.htm">Schwarzmooskogeleish&ouml;hle</a></li>
     <li><a href="1623/76/76.htm">Eislufth&ouml;hle</a></li>
     <li><a href="1623/107.htm">Gemsh&ouml;hle</a></li>
     <li><a href="1623/161/top.htm">Kaninchenh&ouml;hle</a></li>
@@ -40,77 +41,71 @@
   <li><a href="years/">Other years<a/></li>
 </ul>
 
+<h2>Public articles and presentations</h2>
+<ul>
+ <li><a href="intro.htm">Introduction to expo</a></li>
+ <li><a href="expofiles/presentations/">External Presentations(Hidden Earth, etc)</a></li>
+</ul>
+
 <h2>Area Description</h2>
 <ul>
-  <li><a href="noinfo/all.3d">Current data</a> for display with aven</li>
-  <li>The Austrian <a href="katast.htm">Kataster</a> or cave catalogue</li>
+  <li><a href="pubs.htm">Published Articles and Presentations</a> in Journals and at conferences (bibliography with links)</li>
   <li><a href="areas.htm">Area/subarea descriptions</a></li>
   <li><a href="geolog.htm">Geological outline</a></li>
   <li><a href="indxal.htm">Cave Descriptions Index</a>
-  <li><a href="dplong.htm">Deep and Long Caves list</a></li>
-  <li><a href="fixaid.htm">Fixed Ropes</a> in CUCC caves</li>
+  <li>The Austrian <a href="katast.htm">Kataster</a> or cave catalogue</li>
+  <li><a href="noinfo/all.3d">Current data</a> - download file for display using aven</li>
   <li><a href="tollrd.htm">Loser Panoramastra&szlig;e</a></li>
   <li><a href="http://www.tagesbild.at/tageseng.htm">The weather at Grundlesee</a> from a webcam about 5km from basecamp</li>
   <li><a href="fester.htm">Festering</a> - or alternative activities for jaded cavers</li>
   <li><a href="dclaim.htm">Independent visitors' info</a></li>
   <li><a href="others/index.htm">Other groups</a> who have worked in the area.</li>
-  <li><a href="pubs.htm">Published Articles and Presentations</a> in Journals and at conferences (bibliography with links)</li>
+  <li><a href="dplong.htm">Deep and Long Caves list</a> -  out of date</li>
+  <li><a href="fixaid.htm">Fixed Ropes</a> in CUCC caves - very out of date</li>
 </ul>
 
 
 <h2>Expedition Handbook</h2>
 <ul>
-  <li>Full <a href="handbook/index.htm">Expedition Handbook</a></li>
-  <li><a href="intro.htm">Introduction</a></li>
+  <li>Full <a href="handbook/index.htm">Expedition Handbook</a> - start here.<br>
+This contains the Prospecting Handbook and the Surveying Handbook sections.</li>
   <li><a href="primer.htm">Primer</a> - for new expedition members</li>
-  <li><a href="handbook/kitlist.html">Kit list</a></li>
-  <li><a href="travel.htm">How to get to Expo</a></li>
-  <li>Camps: <a href="bcamps.htm">Base camp</a> and <a href="tcamps.htm">High camps</a></li>
-  <li><a href="handbook/look4.htm">Prospecting Guide</a> - Expo handbook
-    <ul>
-      <li><a href="/prospecting_guide/">Table of caves</a></li>
-      <li><a href="handbook/prospecting_guide.html">Map with list of caves</a></li>
-      <li><a href="noinfo/katasterable-or-not">'Katasterable or not' list</li>
-    </ul>
-  <li><a href="handbook/update.htm">Expo Website</a> - How the website and data
-  repositories are accessed, and updated.</li>
-  <li>Surveying:
-    <ul>
-    <li><a href="survey.html">Survey data</a></li>
-    <li><a href="handbook/survey/index.htm">Expo handbook section on surveying</a></li>
-    <li>Therion protractors in <a href="templates/therion1_250.pdf">1:250</a> and <a href="templates/therion1_500.pdf">1:500</a> scales. Thanks to Martin Budaj for these!</li>
-    </ul></li>
-  <li><a href="handbook/rigit.htm">Rigging pitches</a> - embryonic Expedition Handbook section
-    <ul>
-    <li>For now, see Sherry's <a href="http://www.cavepage.magna.com.au/cave/SRTrig.html">Alpine Rigging guide</a> (beta release)</li> <!--<br>... of which there may be a <a href="handbook/3rdparty/sherry/srtrig.htm">local copy</a> if you are
-  browsing from disc-->
-    </ul></li>
-  <li><a href="handbook/1staid.html">First Aid info</a> - equipment and training info</li>
   <li><a href="handbook/rescue.htm">Rescue guide</a> - part of the evolving CUCC Expo handbook</li>
-  <li><a href="handbook/photo.htm">Photography</a> - embryonic Expedition Handbook section</li>
-  <li><a href="handbook/solar.html">Solar Panels</a> - how to set up and store topcamp electrics system</li>
-  <li><a href="handbook/planning.html">Expo Planning Guide</a> - Various helpful information during the planning stages</li>
+  <li><a href="handbook/logbooks.html">Expo logbooks procedures</a> 
+  <li><a href="handbook/look4.htm">Handbook section on prospecting</a> 
+  <li><a href="handbook/essentials.html">Get GPS data on cave locations</a> 
+  <li><a href="handbook/survey/index.htm">Handbook section on surveying</a></li>
+  <li><a href="handbook/rigit.htm">Rigging pitches in Austria</a> 
+  <li><a href="handbook/computer.html">Computing and network setup</a> 
+  <li><a href="handbook/planning.html">Expo Planning Guide</a> - 
+How to plan and make an expo happen.
 </ul>
 
+
+
 <h2>Others</h2>
 <ul>
   <li><a href="folk/index.htm">Members</a> 1976-present, with links to mugshots</li>
   <li><a href="folk/author.htm">Authors</a> of material here <!--(for contacts, see Feedback)</li>-->
   <li><a href="copyit.htm">Copyright info</a></li>
-  <li><a href="links.htm">Links</a> to other relevant websites</li>
-  <li><a href="https://www.srcf.net/mailman/listinfo/caving-expo">Mailing list</a></li>
+  <li><a href="links.htm">Links</a> to Austrian and other caving clubs working in this area</li>
   <li><a href="sponsr.htm">Sponsors</a> - our thanks to those supporting Expo</li>
+  <li><a href="https://www.srcf.net/mailman/listinfo/caving-expo">CUCC Expo mailing list</a></li>
 </ul>
 
-<h2>Useful files external to website</h2>
-<p>These files are not version-controlled (take care updating), and will not be available if you are looking at an offline copy of the website.</p>
+<h2>Useful links for experts</h2>
+<p>These links are shortcuts for those <em>already familiar</em> with the expo surveying 
+and data-management procedures, the respository software system and manual procedures.
+<p>These files are not version-controlled (take care updating).</p>
 <ul>
 <li><a href="expofiles">General file bucket</a></li>
 <li><a href="expofiles/surveyscans/">Survey scans</a></li>
-<li><a href="expofiles/presentations/">External Presentations(Hidden Earth, etc)</a></li>
 <li><a href="expofiles/surveys">Full-size surveys</a></li>
 <li><a href="expofiles/rigging_topos">Rigging topos</a></li>
 <li><a href="expofiles/terrain">Terrain models</a></li>
+<li><a href="handbook/planning.html">Data repository updating</a> - updating online data 
+(including most of the website and handbook pages). Experts only.
+
 <li><a href="expofiles/tunnelwiki/wiki/pages/Tunnel.html">Tunnel Wiki (documentation)</a></li>
 
 </ul>
@@ -226,7 +221,7 @@ Information for each year's expedition<br/>
           <td>|</td>
           <td><a href="years/2017/">2017</a></td>
           <td>|</td>
-          <td><a href="years/2018/">2017</a></td>
+          <td><a href="years/2018/">2018</a></td>
         </tr>
       </table>
 <hr />

intro.htm

@@ -14,18 +14,17 @@ of <span lang="de-at">Salzburg</span> in Austria.
 The cave system we have discovered and explored over these years now 
 extends to more than 150km of passages and shafts.</b></p>
 
-<p>The expedition runs in the Summer, usually July/August. This year we are in the
- middle of  <a href="years/2018/index.html">Expo 2018 </a>.This website (over 800
+<p>The expedition runs in the Summer, usually July/August.This website (over 800
 pages and over 700 images) contain much of the documentation from the
 exploration of these annual expeditions.</p>
 
 <p>For those coming on an Austria expedition for the first time, this great
 bulk of material can seem a little overwhelming. However, it's important for
 people to have some idea of what they are coming to, in order that they can get
-the most out of expo. It is probably worth starting with the <a
-href="primer.htm">Expedition Primer</a> - a document intended specifically for
+the most out of expo. It is probably worth starting with the 
+<a href="primer.htm">Expedition Primer</a> - a document intended specifically for
 new expo members, and leading to some of the more important pages which you
-should read.</p>
+should read in the <a href="handbook/index.htm">Expo Handbook</a>.</p>
 
 <h4>A little history</h4>
 

noinfo/cave_data/1623-2004-18.html

@@ -1,6 +1,6 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
 <!-- Only put one cave in this file -->
-<!-- If you edit this file, make sure you update the website database -->
+<!-- If you edit this file, make sure you update the websites database -->
 <html lang="en">
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
@@ -9,11 +9,11 @@
 <cave>
 <non_public>False</non_public>
 <caveslug>1623-2004-18</caveslug>
-<official_name></official_name>
+<official_name>Eiskeller</official_name>
 <area>1623</area>
 <area>2d</area>
 <kataster_code>0/S -</kataster_code>
-<kataster_number></kataster_number>
+<kataster_number></kataster_number> 
 <unofficial_number>2004-18</unofficial_number>
 
 <entrance>
@@ -21,18 +21,25 @@
   <letter></letter>
 </entrance>
 
-<explorers>Entrance noted CUCC 2004 Martin, Frank. Descended 2005 Olly, Mark, Dave.</explorers>
-<underground_description>Spacious entrance shaft lands on snow plug about 10m down. At one side (uphill, which is probably roughly east) is a short section of rift, and a slot down one side of the snow plug, but this proved too narrow (at least with 2005 snow levels) </underground_description>
-<equipment>20m rope + slings</equipment>
+<explorers>Entrance noted CUCC 2004 Martin, Frank. Descended 2005 Olly, Mark, Dave. Descended and surveyed 2018 Paul, Natalie, Wookey.</explorers>
+<underground_description>Spacious entrance shaft lands on snow cone about 10m down, and a circular ledge of loose rocks which the snow cone does not fully cover. Walk along this ledge, around the south side of the snow cone. The rope can be rigged to 2 bolts on the south wall to continue descending the north-east slope of the snow cone. On this ledge, at the eastern uphill side, is a short section of rift that would require more rigging to explore further. The base of the snow cone sits on a floor of loose rocks which appear to overlie a vertical shaft (continuation of the entrance shaft). At the western tip of the snow cone base is a tiny gap in the snow which could possibly be explored with a safety rope. At the northern side of the snow cone base is a small chamber with an approx. 8m high aven.  
+<P>
+[2005 description: "Spacious entrance shaft lands on snow plug about 10m down. At one side (uphill, which is probably roughly east) is a short section of rift, and a slot down one side of the snow plug, but this proved too narrow (at least with 2005 snow levels)"] </underground_description>
+<equipment>50m rope, 5 hangers and and a rope protector/deviation sling (for the bad rub near the top).
+<P> 
+20m rope and slings were sufficient in 2005 when snow levels were much higher.
+
+</equipment>
 <references><a href="../../years/2005/logbook.html#t2005-08-03B">2005 logbook description</a></references>
-<survey>NOTES MISSING</survey>
+<survey><A HREF=2004-18-elev.pdf>
+ 2004-18-elev.pdf</A> and <A HREF=2004-18-elev2.pdf> 2004-18-elev2.pdf</A></survey>
 <kataster_status></kataster_status>
 <underground_centre_line></underground_centre_line>
 <notes></notes>
-<length></length>
-<depth></depth>
+<length>40m</length>
+<depth>28m</depth>
 <extent></extent>
-<survex_file></survex_file>
+<survex_file>caves-1623/2004-18/2004-18.svx</survex_file>
 <description_file></description_file>
 <url>1623/2004-18/index.html</url>
 </cave>

noinfo/cave_data/1623-2012-dd-08.html

@@ -1,6 +1,6 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
 <!-- Only put one cave in this file -->
-<!-- If you edit this file, make sure you update the website database -->
+<!-- If you edit this file, make sure you update the websites database -->
 <html lang="en">
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
@@ -9,10 +9,10 @@
 <cave>
 <non_public>False</non_public>
 <caveslug>1623-2012-dd-08</caveslug>
-<official_name>Unnamed</official_name>
+<official_name>Haizahnhoehle (Shark Tooth Cave)</official_name>
 <area>1623</area>
 <kataster_code></kataster_code>
-<kataster_number></kataster_number>
+<kataster_number></kataster_number> 
 <unofficial_number>2012-dd-08</unofficial_number>
 
 <entrance>
@@ -20,11 +20,12 @@
   <letter></letter>
 </entrance>
 
-<explorers>CUCC, Duncan Collis and Anthony Day, 2012-08-10</explorers>
-<underground_description>2m high, 3m wide horizontal entrance at base of 5m high escarpment. Passage chokes after ~10m but holes down on the left side lead to a strongly draughting dig/squeeze ascending into further passage [qm a]</underground_description>
+<explorers>CUCC, Duncan Collis and Anthony Day, 2012-08-10; Chris Densham, Frank Tully, Anthony Day, Todd Rye 2018-07-11</explorers>
+<underground_description>5m diameter phreatic tube opens out after 20 m.
+Three low passages on left interconnect and choke. Up slope to right leads to narrow descending rift. Opens out at bottom into phreas but ckokes directly ahead. Draft reported in 2012. Name relates to shark-tooth-like popcorn formations.</underground_description>
 <equipment></equipment>
 <references></references>
-<survey></survey>
+<survey><img src="2012-dd-08/i/2012-dd-08.png" width="600px"/></survey>
 <kataster_status></kataster_status>
 <underground_centre_line></underground_centre_line>
 <notes></notes>

noinfo/cave_data/1623-2017-cucc-28.html

@@ -0,0 +1,129 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
+<!-- Only put one cave in this file -->
+<!-- If you edit this file, make sure you update the websites database -->
+<html lang="en">
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+</head>
+<body>
+<cave>
+<non_public>False</non_public>
+<caveslug>1623-2017-cucc-28</caveslug>
+<official_name>Fischgesichthöhle</official_name>
+<area>1623</area>
+<kataster_code></kataster_code>
+<kataster_number></kataster_number> 
+<unofficial_number>2017-cucc-28</unofficial_number>
+
+<explorers>CUCC (2017-)
+</explorers>
+<underground_description><h2>Twelve Pitches</h2>
+
+<p>
+Entrance is strongly drafting horizontal walking / stooping rift with some snow. From entrance, travel along passage for <5 min to reach <b>first pitch</b>.
+</p>
+
+<p>
+Below first pitch, cross chamber and head right into tube to reach <b>second pitch</b>. Left leads to Windy Tube and 12 Monkeys.
+</p>
+
+<p>
+Below second pitch, cross ice plug and small climb to traverse leading to <b>third pitch (Pendulum Pitch)</b>. Pendule to rock halfway down into rift passage.
+</p>
+
+<p>
+Passage starts as a meandering rift, drops <b>fourth pitch</b> (33m) into a canyon with a stream at the bottom (Blitzen Boulevard). 
+</p>
+
+<p>
+After traversing Blitzen boulevard for roughly 20m down stream, you come to a phreatic passage on the left had side above a slightly tricky climb. Following this passage onwards foe roughly 20m you reach a small chamber know as Benign Bubble Baby Bypass. So called due to the odd look formation suck in the corner. To the left of the formation you reach <b>fifth pitch</b> (7m) that drops into Piss Pot (so called due to how it was used during the exploration of the meander). 
+</p>
+
+<p>
+Piss Pot is roughly 15m in depth but ends in a bouldery choke, not worth any more exploration unless you fancy starting a dig. left of the pitch at station 7 is another meandering passage. Following this for roughly 15m you reach <b>sixth pitch (Liquid Luck)</b>.
+</p>
+
+<p>
+Liquid Luck is a roughly 25m pitch head that drops onto a ledge, surrounded by canyon. The chamber is large and fairly drippy. 
+</p>
+
+<p>
+Opposite this ledge is a phreatic passage that can be accessed by a traverse. The passage leads to a pitch head and a large chamber called the Urinal (also named due to its usage during exploration. The traverse above must be rigged and the descent is roughly 19m to the bottom, however the ceiling extends by roughly 20m above the pitch head and is suspected to connect into happy butterfly.
+</p>
+
+<p>
+Back at Liquid Luck, phreatic development also continues South East. Traverse along the phreatic passage, into another chamber, stay high and traverse along until you are across to into the continuation of of the phreatic passage. This is the beginning of Freeattic Flys, so called because Lydia Leather is dyslexic and didn't realise it wasn't spelt that way. 
+</p>
+
+<p>
+This passage continues along for 30m, passing intricate coral looking formation and it a continues rifting meandering passage. There are several awkward free climbs down. Eventually you get to <b>seventh pitch</b> (5m) that drops into a ledge halfway down, with the continuation called Odious Odium going South East on a traverse line, instead of continuing down to the bottom.
+</p>
+
+<p>
+If you do drop to the bottom of seventh pitch, it puts you into Toto chamber, So called because of the boulder in the shape of Africa. This leads to crystal crumble where stalactites lie.
+</p>
+
+<p>
+Odious Odium continues the phreatic passage with <b>eighth pitch</b> (6m) and <b>ninth pitch</b> (5m). Ninth pitch is a one-bolt-wonder which puts you into a junction which continues both left and right. 
+</p>
+
+<p>
+Turning right will lead you toward Ulysses. Ulysses is a very large chamber, roughly 20 metres in diameter, and a currently unknown depth but expected to be greater than 50 metres. The walls around the this chamber however pretty crap. A traverse has been rigged along the right side wall, with the intension of either A) traversing half way round the chamber and dropping it to find the expected depth, or B) continuing to traverse the chamber, in order to reach the strong lead on the opposite wall, which is a massive rail way sized, continuing phreatic tunnel which requires a 20m bolt climb. This is still to be explored, however has strong draft facing SE. The chamber itself is excessively crumbly, and likely no amount of gardening will make the chamber "safe", so if the pitch is dropped, descents should be very carefully made, one by one, with awareness on very possible falling rock.  
+</p>
+
+<p>
+Turning left after ninth pitch will lead to <b>tenth pitch</b> (15m) which drops into the Shit Show. The chamber is made up of of false floor and massive boulder chokes, and is not an area to tread heavily. The way on is through a rift out of the chamber and leads to <b>eleventh pitch</b> (6m).
+</p>
+
+<p>
+Shortly after eleventh pitch you arrive at <b>twelfth pitch (Rubble Rumble)</b>, a significant 70m pitch into a large chamber. Crossing over a large boulder and then climbing down underneath the chamber has the final 3m hang which can be rigged from the end of the same rope in a steeply sloping passage with a lot of loose choss, which leads to a low crawl crossroads. 
+</p>
+
+<h2>Lower Horizontal Level</h2>
+
+<p>
+Left at the crossroads leads to Big Bastard, an as-yet undropped pitch expected to be 80+m in depth. Straight at the crossroads is a small crawl passage, unexplored.
+</p>
+
+<p>
+Right at the crossroads leads to Miracle Maze, an assortment of sandy phreatic tubes. The first left in Miracle Maze takes you eventually to a large junction chamber. In this chamber, the right turn is a small climb up to a large phreatic development that loops back to the rest of Miracle Maze. The left turn is the downstream continuation of the phreatic tube, called Kubla Khan.
+</p>
+
+<p>
+Kubla Khan continues downstream, with a floor rift joining in from the right in Avian Appendix, named after a prominent wall marking that looks like a bird. Following Avian Appendix is a horribly precarious rift which also leads back to Miracle Maze.
+</p>
+
+<p>
+Kubla Khan itself continues downstream with the walking surface descending to the water level to reach a small pool (Caverns measureless to man, down to a sunless sea) which is good for having a piss in. After the pool the walking surface rises again, past a precarious mudstone arch. Eventually the water and the floor rift leaves the passage again on the right.
+</p>
+
+<p>
+At the end of Kubla Khan the passage splits, a high level phreatic tube requires a handline bolting over a nasty traverse, whereas the low level goes under a crawl into a small sandy tube.
+</p>
+
+<p>
+Back in Miracle Maze, the passage continues with a sandy floor, with passages coming in on the left from Kubla Khan and Avian Appendix. Eventually it reaches Eldritch Eyeholes, a chamber with two prominent round solution pockets in the ceiling which look like eyes. There are three routes here which all join back together after 5-10m. 
+</p>
+
+<p>
+The passage climbs out of Eldritch Eyeholes until a rift re-enters from the right at a 2m climb. Above the climb, the rift may be followed or a tube on the left taken, however the tube turns right back to re-join the rift after only a few meters. In the rift is a right turn which goes up to Coconut Chamber, or the continuation of the rift also eventually reaches the same chamber.
+</p>
+
+<p>
+In Coconut Chamber, a series of narrow tubes to the left of the large rift continue, and eventually loop back to the same rift that can be seen from the chamber itself. The final lead is a small climb in the tubes which leads to an undropped pitch of approximately 10m.
+</p></underground_description>
+<equipment>lots of rope</equipment>
+<references></references>
+<survey></survey>
+<kataster_status>unkatastered</kataster_status>
+<underground_centre_line>In Dataset</underground_centre_line>
+<notes></notes>
+<length></length>
+<depth></depth>
+<extent></extent>
+<survex_file>1623/2017_cucc_28/2017_cucc_28.svx</survex_file>
+<description_file></description_file>
+<url>1623/2017_cucc_28</url>
+</cave>
+</body>
+</html>

noinfo/cave_data/1623-2018-ad-01.html

@@ -0,0 +1,39 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
+<!-- Only put one cave in this file -->
+<!-- If you edit this file, make sure you update the websites database -->
+<html lang="en">
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+</head>
+<body>
+<cave>
+<non_public>False</non_public>
+<caveslug>1623-2018-ad-01</caveslug>
+<official_name>2018-ad-01</official_name>
+<area>1623</area>
+<kataster_code></kataster_code>
+<kataster_number></kataster_number> 
+<unofficial_number>2018-ad-01</unofficial_number>
+
+<entrance>
+  <entranceslug>1623-2018-ad-01</entranceslug>
+  <letter></letter>
+</entrance>
+
+<explorers>Anthony Day, Todd Rye, Frank Tully, Chris Densham</explorers>
+<underground_description>Undescended shaft of ~10m.</underground_description>
+<equipment></equipment>
+<references></references>
+<survey></survey>
+<kataster_status></kataster_status>
+<underground_centre_line></underground_centre_line>
+<notes></notes>
+<length></length>
+<depth></depth>
+<extent></extent>
+<survex_file></survex_file>
+<description_file></description_file>
+<url>1623/2018-ad-01</url>
+</cave>
+</body>
+</html>

noinfo/entrance_data/1623-2012-dd-08.html

@@ -1,6 +1,6 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
 <!-- Only put one entrance in this file -->
-<!-- If you edit this file, make sure you update the website database -->
+<!-- If you edit this file, make sure you update the websites database -->
 <html lang="en">
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
@@ -15,8 +15,8 @@
 <map_description></map_description>
 <location_description>East of summit of Hohes Augst Eck, south of 2012-dd-06 and 07 and a little higher up.</location_description>
 <approach>Via summit of Hohes Augst Eck </approach>
-<underground_description>Passage chokes after ~10m but holes down on the left side lead to a strongly draughting dig/squeeze ascending into further passage [qm a]</underground_description>
-<photo><img src="2012-dd-08/i/2012-dd-08.JPG"/></photo>
+<underground_description></underground_description>
+<photo><img src="2012-dd-08/i/2012-dd-08.JPG" width="600px"/></photo>
 <!-- marking options: P  = Paint,
                       P? = Paint (?),
                       T  = Tag,

noinfo/entrance_data/1623-2012-dd-10.html

@@ -1,6 +1,6 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
 <!-- Only put one entrance in this file -->
-<!-- If you edit this file, make sure you update the website database -->
+<!-- If you edit this file, make sure you update the websites database -->
 <html lang="en">
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
@@ -16,7 +16,7 @@
 <location_description>On N side of Hohes Augsteck.</location_description>
 <approach></approach>
 <underground_description></underground_description>
-<photo></photo>
+<photo><img src="2012-dd-10/2012-dd-10_entrance.jpg" width="600px"/></photo>
 <!-- marking options: P  = Paint,
                       P? = Paint (?),
                       T  = Tag,
@@ -26,7 +26,7 @@
                       S? = Spit (?),
                       U  = Unmarked,
                       ?  = Unknown" -->
-<marking>U</marking> 
+<marking>T</marking> 
 <marking_comment></marking_comment>
 <!-- findability options: ? = To be confirmed ...,
                           S = Surveyed,

noinfo/entrance_data/1623-2018-ad-01.html

@@ -0,0 +1,48 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
+<!-- Only put one entrance in this file -->
+<!-- If you edit this file, make sure you update the websites database -->
+<html lang="en">
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+</head>
+<body>
+<entrance>
+<non_public>False</non_public>
+<slug>1623-2018-ad-01</slug>
+<name>2018-ad-01</name>
+<entrance_description></entrance_description>
+<explorers></explorers>
+<map_description></map_description>
+<location_description></location_description>
+<approach>Via 2012-dd-10</approach>
+<underground_description></underground_description>
+<photo><img src="2018-ad-01/2018-ad-01_entrance.JPG" width="600px"/></photo>
+<!-- marking options: P  = Paint,
+                      P? = Paint (?),
+                      T  = Tag,
+                      T? = Tag (?),
+                      R  = Retagged,
+                      S  = Spit,
+                      S? = Spit (?),
+                      U  = Unmarked,
+                      ?  = Unknown" -->
+<marking>T</marking> 
+<marking_comment></marking_comment>
+<!-- findability options: ? = To be confirmed ...,
+                          S = Surveyed,
+                          L = Lost,
+                          R = Refindable" -->
+<findability>R</findability>
+<findability_description></findability_description>
+<alt></alt>
+<northing></northing>
+<easting></easting> 
+<tag_station></tag_station>
+<exact_station></exact_station>
+<other_station></other_station>
+<other_description></other_description>
+<bearings></bearings>
+<url></url>
+</entrance>
+</body>
+</html>

piclinks/ssvypl.htm

@@ -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 -->

piclinks/typing.htm

@@ -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>
 Typing up survey data at Base Camp
 </title>
@@ -9,7 +7,7 @@ Typing up survey data at Base Camp
 </head>
 <body>
 <div class="centre"><img src="../images/typing.jpg" width="526" height="343" alt="" /></div>
-<p>Tony Rooke typing up survey data into a PC in the Potato Hut at
+<p>Tony Rooke typing up survey data into a PC in the old Potato Hut at
 <a href="../bcamps.htm">Base Camp</a>. This is a vital part of the
 expedition, as it enables exploration to be based on a realistic idea of
 where various passages are relative to each other. If not done whilst on the

primer.htm

@@ -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 – 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>
 

tcamps.htm

@@ -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>

tollrd.htm

@@ -6,6 +6,8 @@
 <link rel="stylesheet" type="text/css" href="css/main2.css" />
 </head>
 <body>
+
+
 <h1>The Loser Panoramastra&szlig;e</h1>
 
 <p>This is a toll road, clearly signposted from the village of Altaussee. A
@@ -66,31 +68,12 @@ the views, not the traffic :-)</p>
 <table class="trad"><tr><th>Vehicle</th><th>Time up</th><th>by</th><th>Time down</th><th>by</th></tr>
 <tr><td>Bike</td><td>00:48:00</td><td>Becka Lawson (2016)</td><td>00:09:26</td><td>Clive George</td></tr>
 <tr><td> </td><td>01:15:00</td><td>Justin (1992)</td><td> </td><td> </td></tr>
-<tr><td>Car</td><td>00:07:46</td><td>Andy Waddington (1998)</td><td>00:07:30</td><td>Andy Waddington (1998)</td></tr>
+<tr><td>Car</td><td>00:07:15</td><td>Haydon Saunders (2018)</td><td>00:06:43</td><td>Haydon Saunders (2018)</td></tr>
+<tr><td></td><td>00:07:46</td><td>Andy Waddington (1998)</td><td>00:07:30</td><td>Andy Waddington (1998)</td></tr>
 </table>
 
 <hr />
 
 <!-- LINKS -->
-<ul id="links">
-<li>Back to <a href="../index.htm">CUCC Home page</a></li>
-<li><b>Main Indices:</b>
-<ul>
-<li><a href="infodx.htm"><b>Index</b> to Expo</a> information pages</li>
-<li><a href="areas.htm">Description of CUCC's area</a> and split to subareas</li>
-<li>Full <a href="indxal.htm">Index to cave descriptions</a> in area 1623</li>
-<li>List of (links to) <a href="pubs.htm">published reports and logbooks</a></li>
-</ul></li>
-<li><b>Pictures:</b>
-<ul>
-<li><a href="gall0.htm">Text only Index</a></li>
-<li><a href="gallery/0.htm">Index pages (with thumbnails)</a></li>
-</ul></li>
-<li>Other info:
-<ul>
-<li>Table of <a href="folk/index.htm">members of CUCC expeditions</a> 1976-present</li>
-<li><a href="others/index.htm">Other groups</a> who have worked in the area.</li>
-</ul></li></ul>
-
 </body>
 </html>

years/1983/log.htm

@@ -219,7 +219,7 @@ return to base was rather more subdued.
 <p>Tony M
 
 <hr />
-<a>1983-07-27 | Surface survey and Prospecting below 115. | Chas, Pete</a>
+<a id="lookfutile">1983-07-27 | Surface survey and Prospecting below 115. | Chas, Pete</a>
 
 <p>The aim was to find the end of the Futility Series popping out of the
 hillside below 115. We surface surveyed down to a permanent station, marked

years/1996/gps.htm

@@ -11,6 +11,7 @@
 15, March 1997, pp 11-15</font>
 
 <center><H2><A NAME="art4">GPS For Expedition cave location</A></H2>
+<br><br>
 <I>Wookey</I></center>
 
 <P><I><b>GPS units are now cheap enough that cavers can afford to consider
@@ -28,7 +29,7 @@ accuracy in the field could be formed. Here I describe what was done, the
 methods used, and the results obtained.</b></I>
 
 <P>I scrounged a Garmin GPS45 from my mate Ian Harvey (see his review in
-<A HREF="http://www.chaos.org.uk/survex/cp/cp11/cpoint11.htm#art4">Compass Points
+<A HREF="http://www.chaos.org.uk/survex/cp/CP11/CPoint11.htm#Art_4">Compass Points
 11</A>) to take on Cambridge UCC's annual jaunt to Austria. The expedition
 area is high up in the mountains in very unhelpful karst terrain where
 getting about is greatly impeded by dwarf pine and small cliffs, as well as

years/2018/basecamplist.html

@@ -0,0 +1,125 @@
+<html>
+<head>
+<title>CUCC Austria Expeditions: 2018 Stuff left at base camp</title>
+<link rel="stylesheet" type="text/css" href="../../css/main2.css" />
+</head>
+<body>
+<h1>Stuff left at base camp 2018</h1>
+
+<p>This inventory done Friday afternoon 17th August 2018 - to be updated. 
+<p>Some of this will be eaten over weekend as basecamp is packed up.
+<h2>Food</h2>
+<ul>
+<li>3kg sack of THE WRONG CUSTARD</li>
+<li>18x 72g sachets of the RIGHT custard</li>
+<li>5x 227g GROUND coffee bags- Sainsburys</li>
+<li>6x 200g instant coffee jars- Sainsburys(unopened)</li>
+<li>12 toilet rolls</li>
+<li>3x UNOPENED Red Label tebags sacks (480 teabags) new in 2018</li>
+<li>2x Opened Red Label tebags sack (480 teabags) more than half full, left over from 2017</li>
+<li>2x giant 2,900g tins chile con carne</li>
+<li>3x big cans (800g) chickpeas (garbanzos)</li>
+<li>3x cans white beans</li>
+<li>6x cans red kidney beans (two sizes)</li>
+<li>3x cans white beans</li>
+<li>1x giant unopened packet cornflakes</li>
+<li>1x unopened 1kg packet of muesli 
+<li>Entire Bier Tent, tables, crates of pans, plates and cutlery, cooking utensils
+</ul>
+
+<h2>Gear</h2>
+<ul>
+<li>Tarpaulins (size measured when folded) at hut
+<ul>
+<li>new, unused, unopened white tarp 7x9m 110gsm - 63sq.m.
+<li>mid-green tarp (formerly end-of-hut cover?) ~44 sq.m.
+<li>mid-green tarp 3.2m x 5.8m = 18.5 sq.m, quite good condition
+<li>2x mid-green tarps,each ~9 sq.m. good condition
+<li>dark-green, many eyelets ~3 sq.m. good condition
+<li>dark-green, many eyelets ~8 sq.m.good condition
+<li>blue, ~9 sq.m. very worn 
+</ul>
+<li>2x Bosch drills
+<li>3x Bosch drill batteries
+<li>1x Bosch drill mains charger and bits in small red plastic tub 
+<li>9x tacklebags
+<li>3x rope protectors
+<li>1x 208 litre brown plastic box (not yet assembled) like the 3 up at top camp.
+<li>2x small daysacks 
+<ul>
+<li> 1 grey (Camping Sabbiadoro) event bag
+<li> 1 dark-blue "Frontline" daysac (Cotswold Outdoor, &pound;25 with Cambridge receipt 15 Feb.2018) no gear tape.
+</ul>
+<li>2-man grey tent (poles, pegs, everything) - geartape purple
+<li>3x blue foam karrimats - purple tape
+<li>3x thin emergency orange polythene bivvy bags  - no breathing holes - muddy & dusty - in a polybag with bits of karrimat, tarp. 
+<li>3x thick emergency orange polythene bivvy bags - no breathing holes - clean and unused - geartape purple
+</ul>
+
+<h2>Networking and computing - expected to be left but not finalised</h2>
+<ul>
+<li>LCD monitor</li>
+<li>keyboard</li>
+<li>3 ethernet network cables</li>
+<li>USB hub (& non-functioning round hotplate)
+<li>USB cables for printer, scanner, WiFi antenna</li>
+<li>USB cable with <b>mini</b>USB - special for use with GPS devices
+<li>3x UK 4-way with Euro plug</li>
+<li>2x UK 4 way with UK plug</li>
+<li>Expo Stereo (ghettoblaster)</li>
+<li>scanner</li>
+<li>Colour laser printer</li>
+<li>Spare black toner cartridge</li>
+<li>laminator + ~5 pouches</li>
+<li>USB charger: 3x microUSB, 3xUSB-C, purple geartape.
+<li>1 HTC phone (donated by Sam?)</li>
+<li>Assorted leads and chargers</li>
+</ul>
+<p>The router, WiFi antenna, AcerAspire blue netbook, Dell laptop (the expo laptop), 
+power-supplies for all of these, mouse  are all expected to be brought back to the UK for fettling/updating, re-testing etc. 
+They are loaned to expo and belong to Wookey and Philip Sargent.
+
+<h2>Standard Basecamp stuff - Bring this back to Cambridge !</h2>
+<ul>
+<li>The Logbook!
+<li>The Sesh book!
+<li>The Bier Book !
+<li>Basecamp Nokia phone and charger
+<li>Topcamp Ruggear phone and charging cable (microUSB)
+</ul>
+
+<h2>Standard Basecamp stuff - expected to be left but not finalised</h2>
+<ul>
+<li>First Aid Kit (green aluminium case)</li>
+<li>First Aid Kit (green aluminium case) labelled Katey 24/7/2016 "Gloves, eyes, heat/cold"</li>
+<li>Medical stuff (green Waitrose cotton bag) random dressings and splints</li>
+<li>Base camp main makita charger ?</li>
+<li>Bread making stuff (scales, some flour, bread knife</li>
+<li>electric kettle</li>
+<li>crate of reading books</li>
+<li>crate of maps and old logbooks </li>
+<li>crate of survey notebooks, sticky-backed transparent plastic roll, rolled-up survey printouts</li>
+<li>cardboard box of about 500x brown paper envelopes</li>
+<li>expo bike, lock and bike-pump (all gear-taped purple)</li>
+<li>6 tea-towels
+<li>2x tubes Austrian toothpaste
+<li>various suncream lotions, shampoos, hand cream, handwash soap
+<li>3x full washingup liquid bottles
+</ul>
+
+<h2>More stuff...</h2>
+<ul>
+<li>yellow Speleo Narnia bag containing toddlers' sand playing toys
+<li>2x bothy bags (1x Rab:4-6 people, 1x Highlander: 4-5 people)</li>
+
+</ul>
+
+<h2>More gear - expected to be left but not finalised</h2>
+
+<ul>
+
+<li>gaz cylinders ??
+
+</ul>
+
+</body></html>

years/2018/index.html

@@ -23,15 +23,20 @@
 <li><a href="logbook.html">2018 Logbook</a></li>
 </ul>
 <h3>Post-Expo Completion</h3>
+<p>These files being created over the de-rigging weekend...
 <ul>
   <li><a href="logbook.html">Logbook</a></li>
   <li>Caver's Forum expo report Postings<a href="ukcaving/index.html">(local copy)</a>, <a href="http://ukcaving.com/board/index.php?topic=22020.0">(original on forum)</a></li>
   <li><a href="basecamplist.html">Things left at Base Camp 2018</a></li>
-   <li><a href="topcamplist.html">Things left at Top Camp 2018</a></li>
-  <li><a href="undergroundcamplist.html">Things left at Littleboy Camp 2018</a></li>
+  <li><a href="topcamplist.html">Things left at Top Camp 2018</a></li>
+  <li><a href="ugcamplist.html">Things left at undergound Camp 2018</a></li>
   <li><a href="ropes.html">Ropes out of cave at end expo</a></li>
-<li><a href="thingsfor2019.html">Things neededed for next year</a></li>
-</ul>-->
+  <li><a href="thingsfor2019.html">Things neededed for next year</a></li>
+  <li>Caver's Forum expo 2018 postings 
+<a href="https://ukcaving.com/board/index.php?topic=23424.0">(original on forum)</a>
+and <a href="ukcaving/index.html">(local copy)</a>,</li>
+
+</ul>
 <h2>Mission Statement</h2>
 <p><em>Taken from our <a href="https://ukcaving.com/board/index.php?topic=23424.0">UK Caving Rope Sponsorship application</a></em>.
 <p>
@@ -67,4 +72,4 @@ We are more than a little curious about the hydrology of this deep area of the c
 <p>
 Back to <a href="../../handbook/planning.html">Expo Planning Guide</a>.
 </body>
-</html>
+</html>

years/2018/logbook.html

@@ -1,19 +1,27 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<html>
 <head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>2018 Expo Logbook</title>
 <link rel="stylesheet" type="text/css" href="../../css/main2.css" />
 </head>
 <body id="logbk">
 <h1>CUCC Expo Logbook 2018</h1>
 
+<img src="logbook0.jpg" width=100%>
+<br>
+<p style="text-align:center"><em>Frontispiece</em>
+<br>
+<br>
+<br>
+
+
 <div class="tripdate" id="t2018-07-10a">2018-07-10</div>
 <div class="trippeople"><u>Tom Crossley</u>, Dickon Morris</div>
 <div class="triptitle">Balkonhoehle/264 - 1<sup>st</sup> rig</div>
 
 <p>
-Rigged entrance pitch as far as second deviation but found deviation tat (meant to be in-situe) had been removed along with hanger. Dickon spent 10+ minutes swinging to find bolt but it could not be found. Returned to surface leaving rope and rigging gear at last rigged Y-hang.
+Rigged entrance pitch as far as second deviation but found deviation tat (meant to be in-situe) 
+had been removed along with hanger. Dickon spent 10+ minutes swinging to find bolt but it could not be found. 
+Returned to surface leaving rope and rigging gear at last rigged Y-hang.
 </p>
 
 <div class="timeug">T/U: 4 hours</div>
@@ -23,7 +31,8 @@ Rigged entrance pitch as far as second deviation but found deviation tat (meant
 <div class="triptitle">Tunnocks - 1<sup>st</sup> rig</div>
 
 <p>
-Rigged Tunnocks to start of Caramel Catharsis (or thereabouts). In the words of Anthony: "Nothing to report, just tell everyone how great it was!"
+Rigged Tunnocks to start of Caramel Catharsis (or thereabouts). In the words of 
+Anthony: "Nothing to report, just tell everyone how great it was!"
 </p>
 
 <div class="timeug">T/U: 5 hours</div>
@@ -34,12 +43,14 @@ Rigged Tunnocks to start of Caramel Catharsis (or thereabouts). In the words of
 <div class="triptitle">Prospecting past Fisch Gesicht, beyond the ski pole line</div>
 
 <p>
-After the first spit had been set we realised that we'd forgotten the bolts, doh, so the tags for these caves have been hammered into cracks and only cucc-2018-ms01 has a hole drilled.
+After the first spit had been set we realised that we'd forgotten the bolts, doh, so the tags for 
+these caves have been hammered into cracks and only cucc-2018-ms01 has a hole drilled.
 </p>
 <p>
 <b>cucc-2018-ms01</b><br />
 Becka's phone GPS 33+ 410730 5274320 Alt 1698m Accuracy 4m<br />
-Description: Rubble slope with snow plug down to a jammed boulder. Wriggle down next to it to a 45° ramp down. This levels off to a tight squeeze down to a small chamber. Around 30m long with no draft.<br />
+Description: Rubble slope with snow plug down to a jammed boulder. Wriggle down next to it to a 45° 
+ramp down. This levels off to a tight squeeze down to a small chamber. Around 30m long with no draft.<br />
 Sketch: see notes and photo on Becka's phone at 09:30 on 13/7/18<br />
 Notes: tag hammered into crack near to placed spit<br />
 Photo: Becka's phone at 14:00<br />
@@ -47,14 +58,17 @@ Photo: Becka's phone at 14:00<br />
 <p>
 <b>cucc-2018-ms02 Blitz Baum Schacht (Lightening Tree Shaft)</b><br />
 Becka's phone GPS 33+ 410635 5283186 Alt 1724m Accuracy 4m (see also Mark's GPS)<br />
-Description: Around 30m NNE (say 020) from distinctive, large, dead tree struck by lightning. A 30m+ shaft, rocks rattle for several seconds. Hole ~5m long x 1m wide.<br />
+Description: Around 30m NNE (say 020) from distinctive, large, dead tree struck by lightning. A 
+30m+ shaft, rocks rattle for several seconds. Hole ~5m long x 1m wide.<br />
 Notes: tag hammered into crack on flat area on long side<br />
 Photo: Becka's phone and Mark's phone at 14:56
 </p>
 <p>
 <b>cucc-2018-ms03 Zufall Hoehle (Coincidence Cave)</b><br />
 Becka's phone GPS 33+ 410376 5283124 Alt 1714m Accuracy 3m (see also Mark's GPS)<br />
-Description: Squeeze through boulders then drop down c2 and along a tall, narrow rift for ~10m to head of ~7m pitch. Weak draft out. This was re-found by Dickon and Jon later the same day and they said there was also a phreatic tube visible from the pitch head. <br />
+Description: Squeeze through boulders then drop down c2 and along a tall, narrow rift for ~10m to 
+head of ~7m pitch. Weak draft out. This was re-found by Dickon and Jon later the same day and they 
+said there was also a phreatic tube visible from the pitch head. <br />
 Notes: tag hammered into above entrance boulders <br />
 Photo: Becka's phone and Mark's phone at 16:10
 </p>
@@ -66,6 +80,8 @@ Notes: tag hammered into crack <br />
 Photo: Mark's phone at 17:00
 </p>
 
+<img src="logbook1.jpg" width=100%>
+
 <!-- <div class="timeug">T/U: 4 hours</div> -->
 
 <div class="tripdate" id="t2018-07-12a">2018-07-12</div>
@@ -73,10 +89,13 @@ Photo: Mark's phone at 17:00
 <div class="triptitle">Tunnocksschacht/258 - String Theory to Procrastination Rig</div>
 
 <p>
-In via usual route to head of String Theory. Found Three ropes (~35m, ~45m, ~60m). Used ~45m and ~35m to rig String Theory (Crossley Rigging). Found ~90m left at head of Procrastination. Used ~20m rope (brought in from top camp) to rig traverse and ~90m to rig pitch of Procrastination. (Densham rigging).
+In via usual route to head of String Theory. Found Three ropes (~35m, ~45m, ~60m). Used ~45m and ~35m to 
+rig String Theory (Crossley Rigging). Found ~90m left at head of Procrastination. Used ~20m rope (brought in 
+from top camp) to rig traverse and ~90m to rig pitch of Procrastination. (Densham rigging).
 </p>
 <p>
-Left tub of flapjacks, snickers, 4 curries with bothy bag at base of Procrastination. Also left 90m 9mm rope for Kraken with slings, snap gates, hangers and maillons.
+Left tub of flapjacks, snickers, 4 curries with bothy bag at base of Procrastination. Also left 90m 9mm 
+rope for Kraken with slings, snap gates, hangers and maillons.
 </p>
 <p>
 Returned to Top Camp ~5 mins before callout - blame my (Crossley's) slow rigging of String Theory. Brought ~60m rope out of cave.
@@ -87,7 +106,9 @@ Returned to Top Camp ~5 mins before callout - blame my (Crossley's) slow rigging
 <div class="trippeople"><u>Jon Arne Toft</u>, Dickon Morris</div>
 <div class="triptitle">Prospecting Kleine Wildkogel</div>
 
-<p>Prospected along side of Kleine Wildkogel along South edge heading West. Little but choked shafts for most of the day, but promising end of the day with two good leads. Conveniently, another team claimed to have discovered one of the better finds 2 hours before we found it. This is heavily disputed and questionable.
+<p>Prospected along side of Kleine Wildkogel along South edge heading West. Little but choked 
+shafts for most of the day, but promising end of the day with two good leads. Conveniently, another team 
+claimed to have discovered one of the better finds 2 hours before we found it. This is heavily disputed and questionable.
 </p>
 
 
@@ -98,7 +119,8 @@ Jon's phone DD 47.69781N 13.81647E<br />
 
 <p><b>CUCC 2018 DM02 -</b><br />
 Jon's phone DD 47.69756N 13.81331E<br />
-8m climb in narrow shaft. 8m climb in wide rift to snow plug. Squeeze past snow plug horizontally 10m leading to small chamber w ice formations. Small window with cobble floor leading to undescended 10m pitch. Rocks rattle at bottom. </p>
+8m climb in narrow shaft. 8m climb in wide rift to snow plug. Squeeze past snow plug horizontally 
+10m leading to small chamber w ice formations. Small window with cobble floor leading to undescended 10m pitch. Rocks rattle at bottom. </p>
 
 <p><b>CUCC2018 DM03 +</b><br />
 Jon's phone DD 47.69813N 13.80967E<br />
@@ -115,7 +137,8 @@ Large open shaft. 10m. Small rift at bottom leads on another inspected 10m drop.
 <p><b>CUCC2018 DM06 -</b><br />
 <b>*THIS CAVE IS A DUPLICATE OF CUCC2018 MS03, which was apparently explored by Becka 2 hrs earlier (or so she says)*</b><br />
 Jon's phone DD 47.69514N 13.80591E<br />
-Climb down boulder tickle 5m leads to 2m climb. Rift continues to 4m pitch into chamber, unpushed. Small passage in roof above pitch ledge to left continues 30m through narrow crawl to 4-way intersection. Unexplored further.</p>
+Climb down boulder tickle 5m leads to 2m climb. Rift continues to 4m pitch into chamber, unpushed. 
+Small passage in roof above pitch ledge to left continues 30m through narrow crawl to 4-way intersection. Unexplored further.</p>
 
 <p><b>CUCC2018 DM07 -</b><br />
 Jon's phone DD 47.69429N 13.80534E<br />
@@ -140,9 +163,12 @@ From here, an impressive pitch was observed(8m diameter) which a 27m rope was in
 descend. Probably 40m deep. Strong draft, predicted by the majority of 
 CUCC to be larger than Tunnocks <i>[citation needed]</i>.</p>
 
-<p>Surveyed out of cave, tag left on small shelf right under surface level. Lack of pencils led to ditching of DM06, though this is an interesting cave. DM06 still unexplored.</p>
+<p>Surveyed out of cave, tag left on small shelf right under surface level. Lack of pencils led to 
+ditching of DM06, though this is an interesting cave. DM06 still unexplored.</p>
 
-<p>Jon sprained ankle before cave entrance, the effects of which showed up shortly after arrival to top camp, and which subsided by the next day. Strange stuff which unfortunately led to me being unable to push further the next day. :-(</p>
+<p>Jon sprained ankle before cave entrance, the effects of which showed up shortly after arrival to 
+top camp, and which subsided by the next day. Strange stuff which unfortunately led to me being 
+unable to push further the next day. :-(</p>
 
 <div class="timeug">T/U: 3 hours</div>
 
@@ -171,9 +197,13 @@ the tourist boat. Photos taken [and posted to Facebook Expo2018 page].
 <div class="trippeople"><u>Becka Lawson</u></div>
 <div class="triptitle">Rigging Guide - Tunnock 258 - Hydra - 
 - Snake Charmer - Snake Bite - Lower Snake Bite  </div>
+
+<img src="logbook2.jpg" width=100%>
+<img src="logbook3.jpg" width=100%>
 <p>
 Snakebite lands in large rift passage with waterfall entering from LHS. Water drains
-down to Lower Snakebite (this starts with an awkward free climb next to water; themore obvious passage on L of this 
+down to Lower Snakebite (this starts with an awkward free climb next to water; themore 
+obvious passage on L of this 
 (as you face downstream) is main Snakebite passage (dry) that connects to Song of the Earth.
 <p>
 [many detailed diagrams - see scanned imageswhen done]
@@ -185,13 +215,14 @@ pitch following water down free climbs.
 
 <div class="tripdate" id="t2018-07-14a">2018-07-14</div>
 <div class="trippeople"><u>Philip Sargent</u></div>
-<div class="triptitle">Surface walk Stoger Weg/115 (Schnellzugh&ouml;hle></div>
+<div class="triptitle">Surface walk Stoger Weg/115 (Schnellzugh&ouml;hle)</div>
 <p>
 Found the entrance* - but it is 60m away from where the GPS says it should be.
 <p>
 Attempted to get to the location the GPS says it is but it's impenetrable bunde.
 <p>
-Stashed in 115 ent: 1 2-man tent, 2 karrimats, 1 litre water (a bit brown - filled in gents loo at berg restaurant), small bag muesli.
+Stashed in 115 ent: 1 2-man tent, 2 karrimats, 1 litre water (a bit brown - 
+filled in gents loo at berg restaurant), small bag muesli.
 <p>
 I rigged a smallwater collection poly sheet which may get 2-3 litres if we're lucky.
 <p>
@@ -201,8 +232,10 @@ rugged than the part closer to the carpark: many granny-stoppers.
 Photos taken from turn-off point [from Stoger Weg]: "a barely discernable trod" to cave.
 This "trod" is much more overgrown thanit was in 1982.
 <p>
-*POSTSCRIPT - on 17th July found a 1981 photo of the entrance which shows that the entrance I found wasn't the main entrance. 
-I had found the upper (smaller) entrance CUCC-PS01-2018 at N 47.66743 E 013.80945 alt. 1547m (WGS84 Garmin Venture Cx)
+*POSTSCRIPT - on 17th July found a 1981 photo of the entrance which shows that the entrance 
+I found wasn't the main entrance. 
+I had found the upper (smaller) entrance CUCC-PS01-2018 at N 47.66743 E 013.80945 alt. 1547m 
+(WGS84 Garmin Venture Cx)
 7
 <div class="timeug">T/U: 4 mins</div>
 
@@ -224,19 +257,144 @@ Out of rope so we surveyed out.
 <div class="timeug">T/U: ?? hours</div>
 
 
-<div class="tripdate" id="t2018-07-18a">2018-07-18</div>
+<div class="tripdate" id="t2018-07-18a">2018-07-13</div>
 <div class="trippeople"><u>Chris Densham</u></div>
 <div class="triptitle">Steinbrucken Tarp Topo</div>
 <p>
-[DIAGRAM of tarp rigging in bivvy]
+[DIAGRAM of tarp rigging in bivvy]<br>
+
+<img src="logbook4.jpg" width=100%>
+
 
 <div class="timeug">T/U: 0 hours</div>
 
+<div class="tripdate" id="t2018-07-11b">2018-07-11</div>
+<div class="trippeople"><u>Anthony Day</u>, Chris, Frank, Todd</div>
+<div class="triptitle">Prospecting/visiting known holes near Organh&ouml;hle</div>
+<p>
+Hacked out on the cairned path to Organh&ouml;hle to look at some holes
+found on a 2012 prospecting trip, and see whatever we could find:
+<ul>
+<li><b>2012-dd-06</b> ("Big-D-H&ouml;hle") - apparently surveyed last year, 
+but not in the dataset. Red survey stations visible but unknown how far it has been explored.
+<li><b>2012-dd-08</b> ("Shark tooth cave", due to popcorn formations that look vaguely likesharks' teeth). 
+A choked 5m round phreatic tube reported as carrying some draught in 2012. Poked around
+in two holes on the left (which connect) and another at the end without finding any way 
+on. Grade 2 survey completed.
+<li><b>2012-dd-10</b> - refound and tagged. Worth descending but especially promising.
+<li><b>2018-ad-01</b> - a ~15m shaft just around corner fom 2012-dd-10 photo'd and tagged; not especially promising.
+<li><b>2012-dd-02</b> - Tagged on our way home.Reported as draughting/windy in 2012, but doesn't look amazing.
+</ul>
+
+<div class="timeug">T/U: 0 hours</div>
+
+<div class="tripdate" id="t2018-07-15a">2018-07-15</div>
+<div class="trippeople"><u>Anthony Day</u>, Becka</div>
+<div class="triptitle">Tunnock's Rig</div>
+<p>
+The ambitious plan was to rig Tunnocks as far as camp.
+This was never on after I misread the log entry from last year and believed the rope for
+Widow Trankey's was in the cave - it wasn't so we were a rope light.
+The Number of the Beast rope went down the wrong hole when I threw it down the pitch and got stuck, neccessitating much
+faffage to retrieve. The rope had also been cut and retied* necessitating a knot pass
+ - this rope should be replaced by the 45m rope currently at the top of String Theory.
+In the end made it to the top of Inferno. Dumped camp stuff (3x pits + stove)
+and headed out.
+
+[ * Becka: using an EDK (European Death Knot) with 8cm ends - who left it like this last year?! ]
+
+<div class="timeug">T/U: 11 hours</div>
+
+
+
+
+<div class="tripdate" id="t2018-07-09">2018-07-09</div>
+<div class="trippeople"><u>Lydia Clare Leather</u>, Mike Butcher, Michael Holiday</div>
+<div class="triptitle">Fisch Gesicht</div>
+Rerigged the cave entrance, to pendulum pitch and all the way to blitzen boulavard.
+<div class="timeug">T/U 8 hours</div>
+
+<div class="tripdate" id="t2018-07-10">2018-07-10</div>
+<div class="trippeople"><u>Lydia Clare Leather</u>, Mike Butcher, Michael Holiday</div>
+<div class="triptitle">Fisch Gesicht, pushing to liquid luck</div>
+Pushed past survey station 14C, found the phreatic tube lead to a small chamber (pissing pot) then continued left to a big pitch. Bolted, Rigged. Michael nearly killed Lydia --> called liquid luck.
+<div class="timeug">T/U 10 hours</div>
+
+<div class="tripdate" id="t2018-07-13">2018-07-13</div>
+<div class="trippeople"><u>Lydia Clare Leather</u>, Mike Butcher, Michael Holiday</div>
+<div class="triptitle">Fisch Gesicht, pushing phreatic flies and surveying liquid luck</div>
+Surveyed from 14C to 22. Michael bolts, lydia and Mike survey. Mike made a dry stone wall. Mike found Toto chamber.
+<div class="timeug">T/U 14 hours</div>
+
+<div class="tripdate" id="t2018-07-14">2018-07-14</div>
+<div class="trippeople"><u>Lydia Clare Leather</u>, Mike Butcher, Michael Holiday</div>
+<div class="triptitle">Fisch Gesicht, Pushing Urinal and fettling rope/rigging</div>
+Mike and Michael did more dry stone walling. More gardening. Followed the free attic opposite liquid luck ledge ti findthe Urinal. Bolted and rigged to an awkward body sized squeezing, thatr smelt of pee, having pissed down B. Boulavard. But possible free attic continuation.
+<div class="timeug">T/U 7 hours</div>
+
+<div class="tripdate" id="t2018-07-15">2018-07-15</div>
+<div class="trippeople"><u>Lydia Clare Leather</u>, Mike Butcher, Tom Crossley</div>
+<div class="triptitle">Fisch Gesicht, Pushed to Toto and surveyed free attic frys and Urinal</div>
+Tom joined Mike and Lydia, surveyed free attic frys and Urinal, found thgat Urinal has a high cieling (40m). Possible connects to Happy Butterfly above. Surveyed to chamber with boulders in the shape of Africa.
+<div class="timeug">T/U 11 hours</div>
+
+<div class="tripdate" id="t2018-07-15">2018-07-15</div>
+<div class="trippeople"><u>Lydia Clare Leather</u>, Mike Butcher, Michael Holiday, Tom Crossley</div>
+<div class="triptitle">Fisch Gesicht, Found Ulysses</div>
+<p>Took photos, Mike and Michael go down to crystal crumble, found stalactites, pretty. Tom bolted coral corner, pretty formations. Traversed round Toto chamber on a false floor to the continuation into conintuation of free attic flys called phreatic becomes meander rift, (bolted) and dind a large opening with left and right junction (very false floor) called odious odium. Taking a right turn along the false floor leads to a vast floor now called Ulysses (after the Frans Ferdinand song Michael was singing). Yet to be dropped due to its very unstable nature. Did some gardening but a lot of work needs doing. Left turn at odium, leads to a true floor, leads to multiple boulder chokes and meander in approximately the direction of Ulysses with short pitches not dropped. More photos on the way out. Michael gets ill. Wees a lot. 
+<p> lots of pee, very loose, less ice than last year, lots of key-hole passage.
+<p>Still to do (by Mike Butcher): 
+<p>- Drop pitch from entrance chamber to bypass ramp and climb of ice plug pitch = more direct.
+<p>- Investigate meander at end of windy tube (?c)
+<p>- Possible alternate route opposite pendulum pitch (?c)
+<p>- B. Boulavard rope needs changing (40m)
+<p>- Leads in Benign Bubble Baby Bypass needs looking into
+<p>- Drop 15m at far end of B. Boulavard
+<p>- Piss Pot resurveyed
+<p>- Survey bottom of liquid luck
+<p>- survey after Toto
+<p>- Toto traverse line
+<p>- KEEP PUSHING!
+
+<div class="timeug">T/U 11 hours</div>
+
+<div class="tripdate" id="t2018-07-16">2018-07-16</div>
+<div class="trippeople"><u>Becka</u>, George, Luke</div>
+<div class="triptitle">Balkon - Cathedral Kazam - Wild Honeycomb shaft - The Hangman</div>
+<p>Spent over an hour trying to calibrate top Camp's collection of distox's (my two, CHECC and ULSA). I won with 0.35 and 0.5. Luke at 0.65 was way off and two Distox's refused to pair with George's PDA. Eventually underground and swiftly to Kathedral Kazam. 2 traverses were still in but short pitch needed rigging. Luke then rigged Wild Honeycomb shaft. Ash has - audaciously - rigged this off naturals last year but it hadn't been surveyed, leaving George and Rachel's Nature Calls surveys at the base floating. George and I followed Luke down surveying, with Luke concerned he'd taken the wrong route, but all was well. 
+<p>At the base, there's a sort of horizontal level which we rigged a short pitch down (7m) and then what George and Rachel had done as a 13m chimney down which Luke and I declared a pitch. This led to a ledge with a vast, perched boulder next to it. The Hangman. 
+<p> the pitch had a massive echo and stone rattle. We drilled the pitch head spits but were out of hangers, so headed out. 
+<div class="timeug">T/U 10 hours</div>
+
+<div class="tripdate" id="t2018-07-17">2018-07-17</div>
+<div class="trippeople"><u>Becka</u>, George</div>
+<div class="triptitle">Balkon - Wild Honeycomb shaft - The Hangman - Hangman's Daughter - <b>Tunnock's Connection</b></div>
+<p>Luke was off-colour so George and I returned to the Hnagman and I rigged down the pitch then we surveyed it to a spacious ledge, from here the shaft continued (offset) but it looked damp and we were keener on the horizontal otions - a window visable part way down The Hangman's Pitch and, from the base, a climb up on the left and a traverse to the right to s vhossy climb.
+<p>George went for the latter option, and got up via some shonky bolts, boulder balancing and clambering. The entered what we've called Hangman's daughter. I followed and we surveyed into what initially looked really unpromising: narrow, catchy, little passage.
+<p>However, it took a draft. We surveyed a loop round (given that George had scooped it) then got to the only proper lead, a small pitchead topped with mostly nasty perched boulders. George heed kicked quite a few down leaving a small hole. We only had one hanger and I dithered about whether to use the massive flake as a backup but used it in the end. The ~15m pitch led to a small chamber. I climbed to the bottom where a ?c crappy hole led down and then -!!!-
+<p>noticed a survey station! WHat the hell? I shouted to George who bombed down, forgetting to bring the Dostox so I had to go up the hideous rubby pitch to fetch it. After some searching, George found another station, 7, and we finished the survey. Then tried to work out where the survey had come from. Some shreds of an oversuit on a tiny tube 3m above the floor of the chamber gave it away. The draft through had coated it in catchy popcorn. We took our SRT kits and tried to crawl through, but George didn't want to commit to going headfirst (I told him I couldn't be able to fish him out). He couldn't get through feet first so we gave up and headed out, finishing off the survey of the traverse on the way. At the top section of the Hnagman's Pitch 1 realived the rope had got hooked over a hideously sharp flake of rock and crystal. I wailed at George and down [prossiked until I could un-weight the rope  and he could free it. Argh.
+<div class="timeug">T/U 11 hours</div>
+
+[Rigging guide]:<br>
+<img src="logbook5.jpg" width=100%>
+<br>
+<img src="logbook6.jpg" width=100%>
+<br>
+<img src="logbook7.jpg" width=100%>
+<br>
+<img src="logbook8.jpg" width=100%>
+<br>
+<img src="logbook9.jpg" width=100%>
+<br>
+<img src="logbook10.jpg" width=100%>
+<br>
+<br>
 <div class="tripdate" id="t2018-07-18b">2018-07-18</div>
 <div class="trippeople"><u>Philip Sargent</u></div>
 <div class="triptitle">Solo walking in area of 115 entrances [and CUCC-PS01-2018]</div>
 <p>11:00-18:00 up the hill.
-<p>Found p115x the main "train tunnel" hole. Did a 200+ averaging GPS reading on p115x, Windloch, and cave 88 on the Stoger Weg.
+<p>Found p115x the main "train tunnel" hole. Did a 200+ averaging GPS reading on p115x, Windloch, and cave 88 
+on the Stoger Weg.
 <p>Carried safety gear from the entrance I found 4 days ago and stashed inside:
 <ul>
 <li>3l water in 3x 2l bottles
@@ -256,7 +414,8 @@ Proceed back along foot of karren slope and push aside
 3-4 branches of bunde to reach a "path".<br><br>
 Follow along this until you can descend steeply to the left (a few more branches of bunde) to  steep "rockery" scramble
 bank. Make your way with care down this and you should be able to see a truncated pine tree [4m high] on the
-other side of a small gully. (When seen from the other side, this pine tree has branches in the shape of a figure "4".) Descend and traverse round 
+other side of a small gully. (When seen from the other side, this pine tree has branches in the shape of a figure "4".) 
+Descend and traverse round 
 to the right and climb up to this pine tree across the gully.<br><br>
 Now follow "path" down and to the right across 2 areas of soil/grass/loose stones to eventually reach a big pine tree 
 with a bend in the trunk at ground
@@ -264,8 +423,10 @@ level and a small cairn on the bend in the trunk. Continue down right through bu
 see a large dead twisted tree root across a gully. Descend and get to this via via lush grass and flowers on steep slope and loose soil.
 <br><br>
 At the twisted dead tree root there is an obvious route leading to the right. At this point you are only 13m from p115x but
-you can't see it as it faces S. and you are approaching from the N. 10m on you pass a large anthill and then 3m further and you're there.<br><br>
-You may see a water collection poly sheet a lot earlier but use this route to get to it. (I did it 3x today and lots of other routes are worse.)
+you can't see it as it faces S. and you are approaching from the N. 10m on you pass a large anthill and then 3m further 
+and you're there.<br><br>
+You may see a water collection poly sheet a lot earlier but use this route to get to it. (I did it 3x today and lots of 
+other routes are worse.)
 <p>
 Oh yes, on first visit to <b>CUCC-PS01-2018</b> this morning I went in: climbing down a 30 degree straight tunnel. 
 Roof is solid rock and floor is blocks 
@@ -273,25 +434,262 @@ and rocks [and relic vadose features]. I counted 1m steps coming out and it's >1
 Continues deeper but I was in t-shirt and shorts. Slight cold outwards draft.
 </p>
 [Photos and GPS tracks and locations recorded.]
-<div class="timeug">T/U: 10 mins</div>
+<div class="timeug">T/U: 0.1 hours</div>
 
 
+<div class="tripdate" id="t2018-07-18a">2018-07-18</div>
+<div class="trippeople"><u>Nadia</u>, Tom Crossley, Todd Rye</div>
+<div class="triptitle">Homecoming - Hobnob Hallway</div>
+
+<ul>
+<li>Surveyed Hobnob Hallway until mud/sand slope.
+went over fals floor very unstable needs a traverse line. Was crumbling as we walked on it.
+
+<li>Under false floor is a trickle of water leading to a wet pitch Q.M.C.
+<li>Found side passage at the bottom of a mud slope on the left. Keyhole passage that connects
+into Dickon's passage,currently unnamed.
+<li>Heard flood pulse, while surveying, when we went out all ropes were dry except the very bottom
+of Radagast pitch. No issue with pitches being impassable except maybe Radagast.
+</ul>
+<div class="timeug">T/U: 7.5 hours</div>
+
+
+<h2>**** MORE TO TYPE IN HERE ****</h2>
+
+<h2>***Scanned images below for logbook entries whcih have not yet been typed up ***</h2>
+<img src="logbook11.jpg" width=100%><br>
+<img src="logbook12.jpg" width=100%><br>
+<img src="logbook13.jpg" width=100%><br>
+<img src="logbook14.jpg" width=100%><br>
+<img src="logbook15.jpg" width=100%><br>
+<img src="logbook16.jpg" width=100%><br>
+<img src="logbook17.jpg" width=100%><br>
+<img src="logbook18.jpg" width=100%><br>
+<img src="logbook19.jpg" width=100%><br>
+<img src="logbook20.jpg" width=100%><br>
+
+
+
+<div class="tripdate" id="t2018-07-29a">2018-07-29</div>
+<div class="trippeople"><u>Philip Sargent</u></div>
+<div class="triptitle">Surface prospecting along "lookfutile.svx" route</div>
+
+<p>Using Garmin eTrex Venture Cx GPS (WGS84)
+<p>"lookfutile.svx" was <a href="../1983/log.htm#lookfutile">surveyed by Chas and Planc</a> 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).
+<p>Generally failed to find lookfutile.svx waypoints (not even the last one with all the red paint). Something
+odd with GPS mismatch - needs nerding to resolve.
+
+<p>Found ent. * (doesn't go) obvious above grassy slope. It is up a 2m climb in a cliff. 
+This is wpt A11 in gpslog: N 47.66629 E013.81128 alt.1407m. 
+This was looked at by Chas & Planc in 1983 and doesn't go:
+"big phreatic entrance further east up the valley" from 
+<a href="http://expo.survex.com/years/1983/log.htm">the 1983 logbook</a> entry 1983-07-27.
+<p>Many photos of this area in photo archive 2018/PhilipSargent.
+<p>Survey station lookfutile.23 is apparently in open air due east of cliff top (which extends N-S).
+<p>Water collection system at 115works well: decanted 3.5 litres of rainwater into bottles. About 6 litres
+now stashed in 115, plus a karrimat and one-man does of flapjack and another dose ofmuesli.; also large
+orange plastic survival bag.
+All other gear removed.
+<p>Walked back to L&ouml;ser Hutte where I managed to catch the sunset drinking crowd and got a 
+lift back to Staudnwirt at ~21:00. Lots of big open cliffs, no bunde, grass and camping areas.
+
+<p>Recent emails from very old lags on this:
+<pre style="font-size:small">
+On 18 July 2018 at 19:46, Charles Butcher  wrote:
+
+    Philip
+
+    Thank you. I’m sorry you had trouble finding it. Even the traditional route to the main entrance is quite a slog, 
+    and if you don’t remember it – I certainly couldn’t – you could be in for a real epic. As you probably found. 
+    I hope the server repairs went well.
+
+    Thanks also for the GPS data in your previous message, and to Andy and everyone else who has worked to 
+    preserve this stuff. I’m astonished that we still have good records of all those muddy survey pages 
+    from so long ago. And to see it all connect with Google mapping is really impressive.
+
+    Safe trip home
+
+    Chas
+
+On Sun, 1 Jul 2018, 10:31 Andy Waddington,  wrote:
+
+    Sometime before sending, Philip Sargent typed (and on Sunday 2018-07-01 at 08:46:16 sent):
+
+    > Any comments on the 115 entrances?
+
+    I really can't remember any of this without reading the stuff on the website - but that stuff is available to
+    everyone (unreliable memory is exactly why this stuff was all put there - but in the early days, which would
+    cover the 115 period, we naively thought we would remember everything, that the same people would be
+    going back, and that we didn't need to write everything down - though actual surveys were properly recorded).
+
+    Where survey data was corrected for fridge north, that should be recorded in the survey notes. That was such
+    a bizarre correction that I don't think it would ever have been done without explaining it. The Futility series survey
+    had two compasses, Suunto 422903 and Chas' Silva 15T. Had there been a major discrepancy between them, I
+    think they would have noticed. The bearings seem to be the same in the Survex dataset as in the notebook.
+    ie. the first leg is 8.08 m on 320 at -11.5. That's from the dataset extracted from CVS in 2001 (which is the oldest
+    I can find in a quick search here). I don't think corrections to fridge north would have been made more recently
+    than that... 075 to Trisselberg cross is the same as the notes, and even if the 115 entrance wasn't located
+    precisely, that ought to be enough to show if the error was more than the odd degree or two.
+
+    Not sure if the scans of this notebook are on the site.
+    Notes are a bit muddy, with no passage walls recorded.
+
+    Did Arge not resurvey any of this ?
+
+    Andy
+
+Philip Sargent (Gmail) 	
+to Charles, andrew, mary5waddington
+
+Chas,
+
+[and Mary, please pass on to Andy as I don’t think any email works for him these days],
+
+ 
+Update, as promised.
+
+Through the miracle that is survex, and the diligent curation of data* over decades by 
+Wadders and Wookey, I have recovered the survey points from your surface walk with Pete 
+on 27 July 1983 and attach as a GPX file in modern WGS84 coordinates. You can plot this 
+on top of a GoogleMaps photo using http://www.gpsvisualizer.com/map_input 
+(or select “OSM (TF Landscape)” in the drop-down on the map to see contours).
+
+I will be re-tracing this slog and looking for more entrances in a week or so. 
+A bit lower than you went looks promising from the geology.
+
+[snip]
+ 
+I also attach the Futility series surveyed by us on 26 July 1983 (futility.svx)
+and as resurveyed by Germans on 8th August 1999 (nutzlos.svx). But this is less 
+useful as GPX on Google maps as it is inside the hill of course and you would need 
+to use Survex/Aven itself to see it. They also seemed to have found another entrance 
+in 2000 which drops eventually into the phreatic stuff which they called the 
+Nebukad series (Nebukadnezar) and is now p115b (ent.) in the survey data.
+
+I hope a find a cold draft coming out of rocks at least, even if I can’t dig it out.
+
+Philip
+ 
+* http://expo.survex.com/repositories/home/expo/loser/shortlog/b6c8d59090c3 is an online 
+look at the version control system used for cave data on Loser these days.
+
+From: Philip Sargent (Gmail) 
+Sent: 21 June 2018 17:28
+To: 'Charles Butcher'
+Cc: andrew@pennine; 'Wookey'
+Subject: RE: Aha - futility series entrance search...
+
+Chas,
+ 
+Unbelievably, that surface survey you and Pete did (“lookfutile”) is a standard part of the SMK dataset.
+
+I can see that your final survey position was 11.7m above the drafting hole in Futility 
+(contrary to Andy’s notes in the file below), and 157m away horizontally. Maybe some 
+fridge-north corrections have been done since then.
+
+You were also spot-on the line where the bedding plane of 115 intersects the hillside. 
+So going downhill from there, maintaining a heading of 118 degrees (if possible) would 
+track further down that bedding plane. As I remember, the survey legs may have been 
+ascending, but the passage roof was coming down to the sandy floor. So the draft 
+connection  (“Utility Entrance” ?) would be lower down.
+
+From: Charles Butcher 
+Sent: 16 June 2018 23:11
+To: Philip Sargent
+Cc: andrew@pennine
+Subject: Re: Aha - futility series entrance search...
+
+Thanks Philip. When you told me about your plan the other day it brought back memories of 
+thrashing around on the hillside, but I couldn’t remember what we were looking for.
+
+I do remember that it was harder work than being underground. I suppose a Laplander pocket saw 
+would be frowned on in the Naturschutzgebiet, but useful all the same.
+
+I assume those coordinates are relative to the entrance, or to whatever else we used as a 
+main datum. So if you have an accurate GPS fix for that datum, wouldn't it be quite easy 
+to locate the hole Pete and I made? Not that that is likely to be much use, since it’s 
+probably the one place we know there isn’t an entrance…
+
+Anyway, good luck and keep us posted!
+
+Best
+Chas
+
+You wrote:
+stumbled on this:
+	http://expo.survex.com /years/1983/log.htm
+	 
+	1983-07-27 | Surface survey and Prospecting below 115. | Chas, Pete
+	The aim was to find the end of the Futility Series popping out of the hillside below 115. 
+	We surface surveyed down to a permanent station, marked with bolt hole and lots of red paint: P1983/1. 
+	This was almost directly below 115 and on the edge of the big trees. 
+	It was at E77.2, N-237.3, H -195.8, whereas the end of the Futility Series was at G30: E 139.7, N -54.2, H-187.8. 
+	So we were (!) at the right place, but the cave end was 180m into the hillside. 
+	We had a good look round but didn't find any signs of caves there.
+	So we looked at a big phreatic entrance further east (up the valley) and ~50m higher.
+	This was looked at in 1982, but a bit of proddling released lots of boulders + we were able to 
+	follow up a narrowing bedding plane at ~60°, for 10m until it got too loose/small. 
+	Very difficult descent on scree to the end of the Altausseer See + then the Schniderwirt for Weizen Bier. 
+	Pete
+ 
+and Wookey thinks some Germans had a look around there too in later years
+Unfortunately we use WGS84 GPS lat./long. these days so I’m not sure I’ll be able to find this 
+35-year old red paint.
+ 
+I’m hoping to use better geology and modern surveying to find where the bedding plane intersects 
+the surface this year. I’m going out for 4-5 weeks.
+Philip
+</pre>
+
+
+
+<div class="timeug">T/U: 0 hours</div>
+
+<div class="tripdate" id="t2018-07-28a">2018-07-28</div>
+<div class="trippeople"><u>Philip Sargent</u></div>
+<div class="triptitle">At basecamp - network nerding</div>
+
+<p>
+Tested Wookey's TP-link 200 Mbps HomePlug devices between potato hut & mains socket above 
+the washing machine in the gents' toilet at the Gasthof. It works:
+the 2nd green light lights up indicating communications OK.
+<p>Previously had tested between potato hut mains and socket in potato hut loft - also worked.
+<p>To do: repeat test with a laptop at each end (needs ethernet socket in laptop)
+to test actual useable bandwidth.
+
+<div class="timeug">T/U: 0</div>
+<div class="timeug">T/U: 0 hours</div>
+
+<div class="tripdate" id="t2018-07-30a">2018-07-30</div>
+<div class="trippeople"><u>Paul Fox</u></div>
+<div class="triptitle">At basecamp - expo laptop</div>
+
+<p>mq extension enabled on mercurial by Paul Fox.
+
 <div class="tripdate" id="t2018-08-01a">2018-08-01</div>
 <div class="trippeople"><u>Philip Sargent</u></div>
 <div class="triptitle">Solo walking in Stumern Alm area</div>
 
-
 Attempt to reach Futility Series mythical potential entrance from below.
 
 Cycled to N.end of Altaussee lake (S.route). This took 1 hour from base camp.
 <p>
-Track up is very cyclable to a hut [Stumern Alm, 813m] where it stops & there is a steeply ascending 
+Saw entrance in hillside 30m higher and about 1km on Loser side which might be a wet-weather resurgence.
+<p>
+Track up is very cyclable to a  (locked)hut [Stumern Alm, 813m] where it stops & there is a steeply ascending 
 rough path (signposted to Appelhaus) up the Trisselwand side of the valley. I parked bike.
 <p>
 I decided to go directly up the Loser side: "Oh Yes", I thought, "10-15 minutes 
 and I'll be past those trees and into the clear grass/rock/scree area". 1 hour later
-I was in a rock shelter [wpt C05 942m], still in the trees, and I could now see that the track I should have been on was much higher,
-and I also had no easy safe way on up this side of the valley.
+I was in a rock shelter [wpt C05 in gpslog N 47.660271646 E013.804951357 942m], 
+still in the trees, and I could now see that the track I should have been on was much higher,
+and I also had no easy safe way on up this side of the valley. The dry rock shelter is completely 
+hidden by trees until you are close to it.
 <p>
 The geology is very promising though - at the hut the big face [Pfenningofen] is well-bedded with a couple of useful-looking faults.
 <p>
@@ -301,7 +699,7 @@ Aborted cycle ride home in Bad Aussee for emergency ice cream.
 <p>
 Philip
 <p>
-PS Nettles! Flies !! aarghhh!!!
+PS Nettles! Flies !! aarghhh !!!
 
 PPS The better way to do this approach would be to take a jeep up the correct track (the one that says "No Bicycles") 
 all the way to the road head at Oberwasser Alm at 1353m, and then traverse round to the right area 
@@ -310,5 +708,103 @@ above the tree line but below the bunde line.
 Departed base camp 06:35, returned 13:05
 
 <div class="timeug">T/U: 0 hours</div>
+
+<div class="tripdate" id="t2018-08-03">2018-08-03</div>
+<div class="trippeople"><u>Philip Sargent</u></div>
+<div class="triptitle">"Lookfutile3"</div>
+<p>Walking and scrambling on the hillside/cliff below the main entrance to 115 (Schnellzugh&ouml;hle) 
+to try to find an entrance to the Futily Series (again).
+<p>Up at 6am with Luke and Rachel, hitched back to Bad Aussee at the end of the day and Wookey
+collected me from there.
+<p>On the mountain I finally got tot he right area where it was possible 
+to explore and make progress: several limestone cliffs and benches - all below bunde level - with 
+dappled shade of beeches and pine trees, lots of artfully arranged rocks & short grass & wild flowers.
+<p>Found several dripping slots but no sensible entrances in this area. I don't trust the altitudes (and sometimes the positions) from my GPS
+in this area - which on average is tipped 30 degrees from the vertical - i.e. it's really all just a broken cliff.
+Several game and hunters' tracks. Lots of rillen karren clambering.
+<p>After climbing up a little cliff - easy enough but something I didn't fancy reversing - I found myself in tick bunde. 
+After a bit I tried going underneath the bunde and found myself looking at a tiny entrance which 
+was giving a slight draft [N 47.66729 E013.80959 alt.1526m using my Garmin eTrex Venture Cx]. 
+It is almost possible to get into it but it is only 
+15m east of cucc-ps01-2018. NB it's not the choked pit, it's 5m east of the 
+choked pit, over the edge of a bunde-bedecked ledge.
+<p>I went into cucc-ps01-2018 for 6 minutes to get 20m in (it descends due west (270 M) at 30 degrees from the horizontal)
+vadose relic with lots of boulders. I got to a big rock I couldn't quite be sure of climbing back up. 
+Needs surveying and tagging.
+
+<p>Removed water-collection poly-sheet from 115 ent. Now only has 9 litres of water and some flapjack & museli in it.
+
+<div class="timeug">T/U: 0.1 hours</div>
+
+<img src="logbook21.jpg" width=100%><br>
+<img src="logbook22.jpg" width=100%><br>
+<img src="logbook23.jpg" width=100%><br>
+<img src="logbook24.jpg" width=100%><br>
+<img src="logbook25.jpg" width=100%><br>
+<img src="logbook26.jpg" width=100%><br>
+<br>
+<div class="tripdate" id="t2018-08-03">2018-08-13</div>
+<div class="trippeople"><u>Philip Sargent</u></div>
+<div class="triptitle">"Local contact"</div>
+
+<p>
+<img src="logbook27.jpg" width=50% align=right hspace=20px>Hitched a lift down from the carpark with Helmut Kalss who lives in Altausee (we drive past his house every time we go up to the
+plateau). He is a local and teaches at the agricultural college. He knew about the SMK system but not what we had done - so he gave
+me a lift to the potato hut and I showed him the posters and aven. (He also has a hat with a feather in it.)
+
+
+
+<div class="timeug">T/U: 0 hours</div>
+
+<br><br>
+<div class="tripdate" id="t2018-08-15">2018-08-15</div>
+<div class="trippeople"><u>Chris Holt</u>, Radost, Luke, Max</div>
+<div class="triptitle">"FGH Derig"</div>
+
+<p>
+Derig was going to be a big job.  Tonnes of rope still down several holes, and most people had already buggered off, and a fair few of those still around had buggered themselves in some fashion!  So we had maybe 6 decent cavers to do maybe 20 bags worth of rope from 3 different entrances in two days.  The real hard nuts had done most of Balkonhole on a camp/push/derig the day before, and half of that group were quite deservedly taking a day off.  Ruaridh's broken arm had mysteriously 'Got better, honest' until we made him prove it by climbing into the Animal house, so he was out.  Fishface/Fischgesicht was the next biggest project, with ~300m depth and vague rumours of a drill left at the bottom for the &quot;unclimbable&quot; leads.
+<p>
+I'd always known it was goin to be a little bit cheeky turning up just for the end of Expo and still hoping to get a chance to push something, but as it turned out I wasn't even the most jammy of the lot!  I'd had a couple of days to acclimatise to camp life and reacquaint myself with the hypothermic delights of Alpine caving when Radost finally arrived (Actually, he had been there earlier, but was just showing his Dad around and wasn't caving), making two of us who hadn't pushed anything.  So, the priorities for this trip were to be
+<ul>
+<li>Derig a metric tonne of rope.
+<li> Retrieve the drill
+<li> Check whether the sod who left the drill hadn't left other vital equipment too
+<li> Show me (Christopher) and Rad how to bolt, and do a little bit of surveying
+<li> Maybe do a rigging guide to speed things up next year
+</ul>
+<p>
+Anyway, after the standard intrepid hike across the plateau, all looking super-cool if I don't say so myself, we change and Luke and Rad zip down while Max waited for me to get changed.  Max and I had already been all the way to Ulysses earlier that week, so he assumed I remembered the way and shot ahead.  I have a terrible memory for complex junctions and my light casts a very sharp throw-pattern, so I still got lost a couple of times and found them all taking a leisurely rest at that nice picnic spot, below the free-climb pitchy thing, where left goes to the way on and right to that disgusting traverse across Ulysses (which Max had derigged two days before and left 70m in a pile in case people wanted to bolt leads below).
+<p>
+There was a brief discussion of what we should expect, and we settled on the priorities listed above.  Luke declared 4pm(?) to be our turnaround time. He wasn't keen on taking more rope deeper into the cave, but given Rad's and my keenness to push the two of us decided to pack it anyway once Luke and Max went ahead.  It was only ten minutes later that the shout was relayed to us &quot;Guys! There's more rope down here anyway! DEFINITELY don't bring that other rope!&quot;  I duly returned the bag to its original position and retrieved the survey gear, which I had of course forgotten to put back in the bag.
+<p>
+The lower shaft of Fischgesicht is a truly marvellous black hole - One of those can't-see-the-bottom, can't-see-the-top ones.  In stark contrast to the rest of the cave above, it was extremely poorly rigged.  Well, I suppose it could have been worse, but even on the way down I was thinking &quot;Should I retie that knot?  It really looks like it rubs.  No, it's probably just me being a wuss and it's like that for a reason&quot;.  This was looking at a lop-sided, 2-metre wide Y-hang that required a sort of acrobatic climb down to access.  New rope, at least, though it was quite dry and required a lot of patience to avoid glazing.  Plenty of time to look around the blackness and ponder the geological mysteries of metamorphosed Carboniferous sediments.
+<p>
+We needn't have brought in a drill battery, as together with the drill there were 3 high-capacity ones already there.  Rad informed me that Luke and Max had gone up the slightly more obvious (right turn at both junctions) of the labyrinthine passages in this new horizontal level to check that the dead end really was one - apparently the small climb Max did crapped out very quickly.  We met back at a junction, I picked up the survey gear from the previous junction, and we headed off (left at second junction) to check the other end of this slightly-larger passage.  Everyone agreed that this was a cracking horizontal level.  Very nice walking-sized!
+<p>
+The previous group (whose identity remains to me as nebulous and vague as their cave descriptions) had apparently concluded that &quot;you'll need bolts and rope to push any of the leads&quot;.  Total bollocks.  We did find a quite sketchy looking climb overlooking the virgin passage floor, but there were two different crawling ways to bypass it!  After this initial reccy we reconvened and distributed survey gear.  I was to get to grips with the CHECC disto, entrusted to me by Luke that morning.  Rad wanted to do the drawing.  I had forgotten to pack any station-marking stuff, but luckily Luke had some nail varnish in his pocket.  We reckonned we had an hour and a half to push, and with no bolting necessary, the excitement of potentially hundreds of metres of 3x3m phreatic tube became evident in everyone's voices.  
+<p>
+So, on to the description itself.  The phreatic tube trends uphill, with a vadose trench in the bottom taking the water gradually deeper and out of sight and earshot.  Where the passage jumps up a dodgy climb, the safer way on is through one of two little holes down and to the left - the leftmost a low crawl, and slightly to the right of that a narrowish slot.  After these, a small chamber with boulders on the floor
+<p>
+Crawl.  We managed to shoot the lazer straight through a tiny window, avoiding the need to survey the crooked oxbow crawl round the right.  Now in another small chamber, but open both forwards/left up a slope, and vertically/right into the big tube, where we were later able to survey the loop (seems to be a near-oxbow of the phreas, which was undercut to make this 3-way big junction with a fourth crawly way that we had just come through).  We progressed forwards up the slope, and the 3x3m tube meanders around for   m.  The floor of the tube is covered with sandy mud that seems to have a darkened crust.  Very easy to follow the path established by the first person.  About halfway along Luke dropped his nail-varnish, so we resorted to scratching in the mud on the walls.  There is a bit of a climb up before a steep slide down a sandy slope.  Take care to avoid falling in the hole at the bottom - it looks like a soft landing because of the pile of sand, but I've no idea how you would get out of that chamber - it looks a bit like the whole tube has a false floor in that area.  Anyway, the tube continues, eventually changing in profile to more of a tall 2x5m elipse.  The noise of the stream can now be heard again - far below, but I suppose cascading more steeply and so making a louder sound.  Eventually we reached a sloping-sided hole in the floor, obviously wet at the bottom, QMc, with the same old tube heading up to the right, QMa, and a bottomless traverse on the opposite side of the hole, QMb.  All of these will require either bolting of a traverse across the hole or a spiderman-like grip and balls of steel.  I would prefer the bolted traverse option.
+<p>
+We still had over half an hour to go, so we returned ot one of the side passages we had noticed earlier.  Climbing back up that steep sandy slope was interesting - everyone had a different method; running full pelt, desperate scrambling, chimping up the wall, etc.  Rad was about to zoom off when I called him back - &quot;You do know I won't be able to do anything from up here, don't you?&quot; he observed. &quot;Yes, but I don't want to die alone!&quot;.  Cautiously attempting to disturb the sand as little as possible, I delicately levitated myself to a position of safety.
+<p>
+It was only a couple of legs into the side passage that it started going crazy.  A-leads to the left, A and B-leads to the right, leads below - way too much to do any justice to in the time we had left.  Clearly the polite thing to do was to leave it for some lucky bastard next year.  There's enough down there for two simultaneous survey groups.
+<p>
+Derig - I was to go up the big pitch with one bag of rope, Radost to follow with the drill and batteries, then pass it to me to put in the top of the 70m bag at Ulysses.  I was so mentally beasted from prusiking with a palpable twang on every bounce, at least until I passed the rub-point, and then He-Manning it past that rebelay, that I completely forgot about Rad's bag until I was about to go past Ulysses.  I backtracked and hauled his bag up the little pitch for him, packed it in the top of the rope bag there, and with two heavy bags proceded up the free-climb.  I had a bit of a sense of humour failure at the top, and having overheard Max &quot;so how many bags do you have, Rad?&quot; &quot;At the moment, precisely zero!&quot; I foisted the heavier one back onto him, selfishly thinking that it would be better for the first person to travel light and quick.  Even one bag on that traverse was troublesome, and so when at the top of the next pitch I heard Rad swearing his way through with two, I decided to redeem myself and took back one of them.
+<p>
+It was slow progress up the rest of the cave, barely keeping ahead of the deriggers (Luke and Max).  At another free-climb I reaslised after &gt;10 minutes of struggling that it was much easier to just throw the bags up and then chimp up after them.  At the surface, I debagged and lay looking at the stars for a couple of minutes, before returning to the first pitch to take Rad's bag.  He was decidedly less talkative than usual, and had the look of a man who needs a break - &quot;it's just quite a heavy bag for a first trip&quot; - I was inclined to agree.  I saw another 3 meteors in the space of 20 seconds before going back to sketch a rudimentary diagram of the entrance traverses and take one bag from Max, and then back again for another.  Realistically, it was the easiest bit of the bag carry, but it was hard thinking of Luke and Max doing all that work and  not rying to help out.
+<p>
+The decision to leave all the tackle sacks at the entrance was endorsed unanimously.  I poured myself a large Schnapps and followed everyone in double-curry dinner and falling asleep immediately.</pre>
+<p>
+
+<br>
+<div class="tripdate" id="t2018-07-30z">2018-07-30</div>
+<div class="trippeople"><u>Robert Seebacher</u></div>
+<div class="triptitle">"Receipt for expo members of VfHO for 2018"</div>
+
+<img src="vfho-receipt.jpg" width=100%><br>
+
 </body>
+
 </html>