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

Merge stuff moved outof noinfo with lots of other changes

Browse Source
This commit is contained in:
Wookey 2019-03-26 21:24:12 +00:00
commit 83d5f93067
177 changed files with 9194 additions and 1217 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
1623/0.htm
View File

@ -35,6 +35,7 @@ spring", it seems more appropriate to use "Steinwandquelle", as suggested
by John Cordingley.</p>
<hr />
<div id="menu">
<ul id="links">
<li><a href="index.html">Area description</a></li>
<li><a href="../indxal.htm">Full Index to 1623</a></li>
@ -42,5 +43,6 @@ by John Cordingley.</p>
<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>
</div>
</body>
</html>

3
1623/107/l/107.htm
View File

@ -16,6 +16,7 @@ which had to be dug, at the western edge of the plateau.</p>
<!-- Kodachrome 25 slide K494, Photo-CD 6121 1651 2353 img 21 -->
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><a href="../../107.htm">Gemsh&ouml;hle description</a></li>
<li><a href="../../index.html">Plateau description</a></li>
@ -30,5 +31,7 @@ which had to be dug, at the western edge of the plateau.</p>
</ul></li>
<li><a href="../../../../index.htm">Back to CUCC Home page</a></li>
</ul>
</div>
</body>
</html>

2
1623/145/histry.htm
View File

@ -60,6 +60,7 @@
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><a href="../../index.htm">Back to Expedition Intro page</a></li>
<li><a href="../../infodx.htm">Index to info/topic pages</a></li>
@ -67,5 +68,6 @@
<li><a href="../../indxal.htm">Full Index to 1623 caves</a></li>
<li><a href="../../../index.htm">Back to CUCC Home page</a></li>
</ul>
</div>
</body>
</html>

2
1623/145/l145.htm
View File

@ -16,6 +16,7 @@ Wolfh&ouml;hle entrance
<!-- Photo K522, Photo-CD 6121 1651 2353 img 22 -->
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><a href="145.html">Wolfh&ouml;hle description</a></li>
<li><a href="../index.html">Plateau description</a></li>
@ -30,5 +31,6 @@ Wolfh&ouml;hle entrance
</ul></li>
<li><a href="../../../index.htm">Back to CUCC Home page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/136desc.htm
View File

@ -328,6 +328,7 @@ log book.</p>
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><a href="names.htm">Glossary of passage names</a></li>
<li><a href="top.htm">Kaninchenh&ouml;hle</a> Cave Description - Overview</li>
@ -337,5 +338,6 @@ log book.</p>
<li><a href="../../indxal.htm">Full Index to 1623 caves</a></li>
<li><a href="../../../index.htm">Back to CUCC Home page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/a-z.htm
View File

@ -62,6 +62,7 @@
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><b>Kaninchenh&ouml;hle</b> Cave Description -
<ul>
@ -76,5 +77,6 @@
</ul></li>
<li><a target="_main" href="../../../index.htm">Back to CUCC Home page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/bsains.htm
View File

@ -148,6 +148,7 @@ east), and the <a href="rhr.htm#rhroute">Right Hand Route</a> to the right
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><a href="names.htm">Glossary of passage names</a></li>
<li><a href="top.htm">Kaninchenh&ouml;hle</a> Cave Description - Overview</li>
@ -157,5 +158,6 @@ east), and the <a href="rhr.htm#rhroute">Right Hand Route</a> to the right
<li><a href="../../indxal.htm">Full Index to 1623 caves</a></li>
<li><a href="../../../index.htm">Back to CUCC Home page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/chile.htm
View File

@ -476,6 +476,7 @@ obvious passage continuing above the surface. The sump is <b>Totality</b>, at
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><a href="names.htm">Glossary of passage names</a></li>
<li><a href="top.htm">Kaninchenh&ouml;hle</a> Cave Description - Overview</li>
@ -485,5 +486,6 @@ obvious passage continuing above the surface. The sump is <b>Totality</b>, at
<li><a href="../../indxal.htm">Full Index to 1623 caves</a></li>
<li><a href="../../../index.htm">Back to CUCC Home page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/deepwy.htm
View File

@ -317,6 +317,7 @@ about 12 cm in diameter.
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><a href="names.htm">Glossary of passage names</a></li>
<li><a href="top.htm">Kaninchenh&ouml;hle</a> Cave Description - Overview</li>
@ -326,5 +327,6 @@ about 12 cm in diameter.
<li><a href="../../indxal.htm">Full Index to 1623 caves</a></li>
<li><a href="../../../index.htm">Back to CUCC Home page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/dream.htm
View File

@ -81,6 +81,7 @@ a few metres before <a href="rhr.htm#poxyp">Bungalow Pitch</a>.
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><a href="names.htm">Glossary of passage names</a></li>
<li><a href="top.htm">Kaninchenh&ouml;hle</a> Cave Description - Overview</li>
@ -90,5 +91,6 @@ a few metres before <a href="rhr.htm#poxyp">Bungalow Pitch</a>.
<li><a href="../../indxal.htm">Full Index to 1623 caves</a></li>
<li><a href="../../../index.htm">Back to CUCC Home page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/drunk.htm
View File

@ -115,6 +115,7 @@ passages at the bottom of Left Hand Route.
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><a href="names.htm">Glossary of passage names</a></li>
<li><a href="top.htm">Kaninchenh&ouml;hle</a> Cave Description - Overview</li>
@ -124,5 +125,6 @@ passages at the bottom of Left Hand Route.
<li><a href="../../indxal.htm">Full Index to 1623 caves</a></li>
<li><a href="../../../index.htm">Back to CUCC Home page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/farnth.htm
View File

@ -372,6 +372,7 @@ name="qC1993-161-02">C1993-161-02</a>], at a depth of -269m from 161a (Alt. 1517
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><a href="names.htm">Glossary of passage names</a></li>
<li><a href="top.htm">Kaninchenh&ouml;hle</a> Cave Description - Overview</li>
@ -381,5 +382,6 @@ name="qC1993-161-02">C1993-161-02</a>], at a depth of -269m from 161a (Alt. 1517
<li><a href="../../indxal.htm">Full Index to 1623 caves</a></li>
<li><a href="../../../index.htm">Back to CUCC Home page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/fbl136.htm
View File

@ -188,6 +188,7 @@ Probably needs another look, draughty, but not terribly promising
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><a href="names.htm">Glossary of passage names</a></li>
<li><a href="top.htm">Kaninchenh&ouml;hle</a> Cave Description - Overview</li>
@ -197,5 +198,6 @@ Probably needs another look, draughty, but not terribly promising
<li><a href="../../indxal.htm">Full Index to 1623 caves</a></li>
<li><a href="../../../index.htm">Back to CUCC Home page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/fbland.htm
View File

@ -221,6 +221,7 @@ Traverse</a>.
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><a href="names.htm">Glossary of passage names</a></li>
<li><a href="top.htm">Kaninchenh&ouml;hle</a> Cave Description - Overview</li>
@ -230,5 +231,6 @@ Traverse</a>.
<li><a href="../../indxal.htm">Full Index to 1623 caves</a></li>
<li><a href="../../../index.htm">Back to CUCC Home page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/france.htm
View File

@ -188,6 +188,7 @@ a small subsidiary dry chamber.
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><a href="names.htm">Glossary of passage names</a></li>
<li><a href="top.htm">Kaninchenh&ouml;hle</a> Cave Description - Overview</li>
@ -197,5 +198,6 @@ a small subsidiary dry chamber.
<li><a href="../../indxal.htm">Full Index to 1623 caves</a></li>
<li><a href="../../../index.htm">Back to CUCC Home page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/frtotp.htm
View File

@ -150,6 +150,7 @@ way to the 161d</a> (Scarface) entrance.
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><a href="names.htm">Glossary of passage names</a></li>
<li><a href="top.htm">Kaninchenh&ouml;hle</a> Cave Description - Overview</li>
@ -159,5 +160,6 @@ way to the 161d</a> (Scarface) entrance.
<li><a href="../../indxal.htm">Full Index to 1623 caves</a></li>
<li><a href="../../../index.htm">Back to CUCC Home page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/icelnd.htm
View File

@ -178,6 +178,7 @@ chamber.</p>
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><a href="names.htm">Glossary of passage names</a></li>
<li><a href="top.htm">Kaninchenh&ouml;hle</a> Cave Description - Overview</li>
@ -187,5 +188,6 @@ chamber.</p>
<li><a href="../../indxal.htm">Full Index to 1623 caves</a></li>
<li><a href="../../../index.htm">Back to CUCC Home page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/kctotp.htm
View File

@ -128,6 +128,7 @@ access from the 161d entrance.
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><a href="names.htm">Glossary of passage names</a></li>
<li><a href="top.htm">Kaninchenh&ouml;hle</a> Cave Description - Overview</li>
@ -137,5 +138,6 @@ access from the 161d entrance.
<li><a href="../../indxal.htm">Full Index to 1623 caves</a></li>
<li><a href="../../../index.htm">Back to CUCC Home page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/l/161a89.htm
View File

@ -17,6 +17,7 @@ when even more gear than usual was strewn around.
<!-- Photo BK425, Photo-CD 6121 1651 2353 img 91 -->
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><b>More photos:</b>
<ul>
@ -30,5 +31,6 @@ when even more gear than usual was strewn around.
<li><a href="../../../areas.htm">Other Areas</a></li>
<li><a href="../../../index.htm">Back to Expedition Intro page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/l/161d.htm
View File

@ -15,6 +15,7 @@ which holds up a cuddly top at the 161d entrance.
<!-- Photo-CD 6121 1651 2353 img 6 -->
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><b>Picture pages:</b>
<ul>
@ -31,5 +32,6 @@ which holds up a cuddly top at the 161d entrance.
<li><a href="../../../areas.htm">Other Areas</a></li>
<li><a href="../../../index.htm">Back to Expedition Intro page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/l/161d2.htm
View File

@ -14,6 +14,7 @@ Kaninchenh&ouml;hle: Scarface entrance
<br><font size=-1>Photo &copy; Duncan Collis, 1996</font>
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><b>Picture pages:</b>
<ul>
@ -30,5 +31,6 @@ Kaninchenh&ouml;hle: Scarface entrance
<li><a href="../../../areas.htm">Other Areas</a></li>
<li><a href="../../../index.htm">Back to Expedition Intro page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/l/3wisea.htm
View File

@ -21,6 +21,7 @@ End", and the current end of exploration (last visited in 1994).
<!-- Photo scanned on Coolscan 600x800 at 675 dpi, 1997.08.12, AERW -->
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><a href="../pixrh.htm#id3wise">Visual tour of 161</a></li>
<li><b>Another photo:</b>
@ -33,5 +34,6 @@ End", and the current end of exploration (last visited in 1994).
<li><a href="../../../areas.htm">Other Areas</a></li>
<li><a href="../../../index.htm">Back to Expedition Intro page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/l/3wiseb.htm
View File

@ -22,6 +22,7 @@ in 1994).
<!-- Photo scanned on Coolscan 600x800 at 675 dpi, 1997.08.12, AERW -->
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><a href="../pixrh.htm#id3wise">Visual tour of 161</a></li>
<li><b>Another photo:</b>
@ -34,5 +35,6 @@ in 1994).
<li><a href="../../../areas.htm">Other Areas</a></li>
<li><a href="../../../index.htm">Back to Expedition Intro page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/l/autodr.htm
View File

@ -17,6 +17,7 @@ Sainsbury's, looking back towards the Basement (bottom of the
<!-- Photo-CD 6121 1651 2353 img 95 -->
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><a href="../pixrh.htm#autodr">Back to visual tour of 161</a></li>
<li><a href="../bsains.htm#autodoors">Back to cave description</a></li>
@ -25,5 +26,6 @@ Sainsbury's, looking back towards the Basement (bottom of the
<li><a href="../../../areas.htm">Other Areas</a></li>
<li><a href="../../../index.htm">Back to Expedition Intro page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/l/bcunt.htm
View File

@ -18,6 +18,7 @@ Triassic Park from Flat France below the 161b and 161c entrances.
<!-- Photo-CD 6121 1651 2353 img 8 -->
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li>Back to <a href="../pixsf.htm#bcunt">visual tour of 161</a></li>
<li>Back to cave description:
@ -30,5 +31,6 @@ Triassic Park from Flat France below the 161b and 161c entrances.
<li><a href="../../../areas.htm">Other Areas</a></li>
<li><a href="../../../index.htm">Back to Expedition Intro page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/l/bhclmb.htm
View File

@ -14,6 +14,7 @@ the furthest north parts of <span lang="de">Kaninchenh&ouml;hle.</span>
<!-- Photo scanned on coolscan, 600x900 at 675dpi, 1997.08.12, AERW -->
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><a href="../pixrh.htm#beehivec">Visual tour of 161</a></li>
<li>Back to <a href="../farnth.htm#repton2">cave description</a></li>
@ -22,5 +23,6 @@ the furthest north parts of <span lang="de">Kaninchenh&ouml;hle.</span>
<li><a href="../../../areas.htm">Other Areas</a></li>
<li><a href="../../../index.htm">Back to Expedition Intro page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/l/bldaly.htm
View File

@ -18,6 +18,7 @@ as the rift drops down the head of the Knossos pitch.
<!-- Photo scanned on Coolscan 600x900 at 675 dpi, 1997.08.08, AERW -->
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><a href="../pixrh.htm#balley">Visual tour of 161</a></li>
<li><a href="../rhr.htm#balley">Back to cave description</a></li>
@ -26,5 +27,6 @@ as the rift drops down the head of the Knossos pitch.
<li><a href="../../../areas.htm">Other Areas</a></li>
<li><a href="../../../index.htm">Back to Expedition Intro page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/l/boltin.htm
View File

@ -17,6 +17,7 @@ electric drill had died early in the exploration of this series.
<!-- Photo by video from print -->
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><a href="../pixrh.htm">Visual tour of 161</a></li>
<li>Back to <a href="../offrhr.htm#vestab">cave description</a></li>
@ -27,5 +28,6 @@ guide, bolting section</a></li>
<li><a href="../../../areas.htm">Other Areas</a></li>
<li><a href="../../../index.htm">Back to Expedition Intro page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/l/boltp1.htm
View File

@ -21,6 +21,7 @@ at least the exit, when knackered, is somewhat less daunting).
<!-- Photo scanned on Coolscan, 1997.08.xx, AERW -->
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><a href="../pixrh.htm#boltp1">Visual tour of 161</a></li>
<li><a href="../bsains.htm#id161a">Back to cave description</a></li>
@ -29,5 +30,6 @@ at least the exit, when knackered, is somewhat less daunting).
<li><a href="../../../areas.htm">Other Areas</a></li>
<li><a href="../../../index.htm">Back to Expedition Intro page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/l/bottom.htm
View File

@ -18,6 +18,7 @@ time), the bottom of Flapjack II - Splatdown,
<!-- Photo-CD 6121 1651 2353 img 65 -->
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><a href="../pixrh.htm#bottom">Visual tour of 161</a></li>
<li><a href="../deepwy.htm#splatd">Back to cave description</a></li>
@ -26,5 +27,6 @@ time), the bottom of Flapjack II - Splatdown,
<li><a href="../../../areas.htm">Other Areas</a></li>
<li><a href="../../../index.htm">Back to Expedition Intro page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/l/bsains.htm
View File

@ -15,6 +15,7 @@ this large passage is the key to all the main routes in the "old" cave.
<br><font size=-1>Photo &copy; Mark Fearon</font>
<!-- Photo-CD 6121 1651 2353 img 67 --><hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><a href="../pixrh.htm#bsains">Visual tour of 161</a></li>
<li><a href="../bsains.htm">Back to cave description</a></li>
@ -23,5 +24,6 @@ this large passage is the key to all the main routes in the "old" cave.
<li><a href="../../../areas.htm">Other Areas</a></li>
<li><a href="../../../index.htm">Back to Expedition Intro page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/l/bugger.htm
View File

@ -16,6 +16,7 @@ up-climb that stopped exploration at the end of Triassic Park in 1995.
<!-- Photo AE004, Photo-CD 6121 1651 2353 img 56 -->
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><a href="../pixsf.htm#bugger">Visual tour of 161</a></li>
<li><a href="../offtp3.htm#bugger">Back to cave description</a></li>
@ -24,5 +25,6 @@ up-climb that stopped exploration at the end of Triassic Park in 1995.
<li><a href="../../../areas.htm">Other Areas</a></li>
<li><a href="../../../index.htm">Back to Expedition Intro page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/l/bunglw.htm
View File

@ -18,6 +18,7 @@ seen in the hading wall of the rift.
<!-- Photo-CD 6121 1651 2353 img 93 -->
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><a href="../pixrh.htm#bunglw">Visual tour of 161</a></li>
<li><a href="../rhr.htm#poxyp">Back to cave description</a></li>
@ -26,5 +27,6 @@ seen in the hading wall of the rift.
<li><a href="../../../areas.htm">Other Areas</a></li>
<li><a href="../../../index.htm">Back to Expedition Intro page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/l/cfour.htm
View File

@ -18,6 +18,7 @@ the cave.
<!-- Scanned on Nikon Coolscan II 900x600 at 675dpi, 1997.08.08, AERW -->
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><a href="../pixrh.htm#cfour">Visual tour of 161</a></li>
<li><a href="../sibria.htm#carrefour">Back to cave description</a></li>
@ -26,5 +27,6 @@ the cave.
<li><a href="../../../areas.htm">Other Areas</a></li>
<li><a href="../../../index.htm">Back to Expedition Intro page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/l/chunlp.htm
View File

@ -17,6 +17,7 @@ off is reached by a slightly greasy scramble down (traverse line).
<!-- Photo AL192, Photo-CD 6121 1651 2353 img 92 -->
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><a href="../pixrh.htm#chunlp">Visual tour of 161</a></li>
<li><a href="../rhr.htm#chunnel">Back to cave description</a></li>
@ -25,5 +26,6 @@ off is reached by a slightly greasy scramble down (traverse line).
<li><a href="../../../areas.htm">Other Areas</a></li>
<li><a href="../../../index.htm">Back to Expedition Intro page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/l/dewdrp.htm
View File

@ -16,6 +16,7 @@ convenient route of access for the Right Hand Route.
<!-- Photo-CD 6121 1651 2353 img 96 -->
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><a href="../pixrh.htm#dewdrop">Visual tour of 161</a></li>
<li><a href="../bsains.htm#snotp">Back to cave description</a></li>
@ -24,5 +25,6 @@ convenient route of access for the Right Hand Route.
<li><a href="../../../areas.htm">Other Areas</a></li>
<li><a href="../../../index.htm">Back to Expedition Intro page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/l/dh1-03.htm
View File

@ -16,6 +16,7 @@ in the Wheelchair Access Series off Triassic Park (discovered 1996).
<!-- Photo scanned on Coolscan at 1350 dpi, 1997.10, AERW -->
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><a href="../pixlw.htm#dlw">Visual tour of 161 Lost World</a></li>
<li><b>More photos:</b>
@ -28,5 +29,6 @@ in the Wheelchair Access Series off Triassic Park (discovered 1996).
<li><a href="../../../areas.htm">Other Areas</a></li>
<li><a href="../../../index.htm">Back to Expedition Intro page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/l/dh1-13.htm
View File

@ -14,6 +14,7 @@ Kaninchenh&ouml;hle Lost World: Downstream chamber
<!-- Photo scanned 1800x1200 on Coolscan at 1350 dpi, 1997.10, AERW -->
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><a href="../pixlw.htm#fdlw">Visual tour of 161 Lost World</a></li>
<li><b>More photos:</b>
@ -26,5 +27,6 @@ Kaninchenh&ouml;hle Lost World: Downstream chamber
<li><a href="../../../areas.htm">Other Areas</a></li>
<li><a href="../../../index.htm">Back to Expedition Intro page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/l/dh1-17.htm
View File

@ -16,6 +16,7 @@ in the Wheelchair Access Series off Triassic Park (discovered 1996).
<!-- Photo scanned 1800x1200 on Coolscan at 1350 dpi, 1997.10, AERW -->
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><a href="../pixlw.htm#dlw">Visual tour of 161 Lost World</a></li>
<li><b>More photos:</b>
@ -28,5 +29,6 @@ in the Wheelchair Access Series off Triassic Park (discovered 1996).
<li><a href="../../../areas.htm">Other Areas</a></li>
<li><a href="../../../index.htm">Back to Expedition Intro page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/l/dh1-18.htm
View File

@ -14,6 +14,7 @@ in the Wheelchair Access Series off Triassic Park (discovered 1996).
<!-- Photo scanned on Coolscan at 1350 dpi, 1997.10, AERW -->
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><a href="../pixlw.htm#dlw">Visual tour of 161 Lost World</a></li>
<li><b>More photos:</b>
@ -26,5 +27,6 @@ in the Wheelchair Access Series off Triassic Park (discovered 1996).
<li><a href="../../../areas.htm">Other Areas</a></li>
<li><a href="../../../index.htm">Back to Expedition Intro page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/l/dh1-21.htm
View File

@ -14,6 +14,7 @@ Kaninchenh&ouml;hle Lost World: Pteramacsuit Chamber
<!-- Photo scanned on Coolscan at 1350 dpi, 1997.10, AERW -->
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><a href="../pixlw.htm#ptera">Visual tour of 161 Lost World</a></li>
<li><b>More photos:</b>
@ -26,5 +27,6 @@ Kaninchenh&ouml;hle Lost World: Pteramacsuit Chamber
<li><a href="../../../areas.htm">Other Areas</a></li>
<li><a href="../../../index.htm">Back to Expedition Intro page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/l/dh2-03.htm
View File

@ -16,6 +16,7 @@ Flats in Upstream Lost World, Kaninchenh&ouml;hle.
<!-- Photo scanned on Coolscan at 1350 dpi, 1997.10, AERW -->
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><a href="../pixlw.htm#bcf">Visual tour of 161 Lost World</a></li>
<li><b>More photos:</b>
@ -28,5 +29,6 @@ Flats in Upstream Lost World, Kaninchenh&ouml;hle.
<li><a href="../../../areas.htm">Other Areas</a></li>
<li><a href="../../../index.htm">Back to Expedition Intro page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/l/dh2-14.htm
View File

@ -15,6 +15,7 @@ at the far eastern end of Upstream Lost World.
<!-- Photo scanned on Coolscan at 1350 dpi, 1997.10, AERW -->
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><a href="../pixlw.htm#fulw">Visual tour of 161 Lost World</a></li>
<li><b>More photos:</b>
@ -27,5 +28,6 @@ at the far eastern end of Upstream Lost World.
<li><a href="../../../areas.htm">Other Areas</a></li>
<li><a href="../../../index.htm">Back to Expedition Intro page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/l/dh2-18.htm
View File

@ -17,6 +17,7 @@ passage, in Kaninchenh&ouml;hle.
<!-- Photo scanned 1200x1600 on Coolscan at 1350 dpi, 1997.10, AERW -->
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><a href="../pixlw.htm#id5mp">Visual tour of 161 Lost World</a></li>
<li><b>More photos:</b>
@ -29,5 +30,6 @@ passage, in Kaninchenh&ouml;hle.
<li><a href="../../../areas.htm">Other Areas</a></li>
<li><a href="../../../index.htm">Back to Expedition Intro page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/l/dh2-22.htm
View File

@ -17,6 +17,7 @@ series from Wheelchair Access, off Triassic Park in Kaninchenh&ouml;hle.
<!-- Photo scanned 1200x1600 on Coolscan at 1350 dpi, 1997.10, AERW -->
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><a href="../pixlw.htm#kzr">Visual tour of 161 Lost World</a></li>
<li><b>More photos:</b>
@ -29,5 +30,6 @@ series from Wheelchair Access, off Triassic Park in Kaninchenh&ouml;hle.
<li><a href="../../../areas.htm">Other Areas</a></li>
<li><a href="../../../index.htm">Back to Expedition Intro page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/l/dh2-31.htm
View File

@ -17,6 +17,7 @@ Kaninchenh&ouml;hle.
<!-- Photo scanned 1200x1200 on Coolscan at 1350 dpi, 1997.10, AERW -->
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><a href="../pixlw.htm#dh231">Visual tour of 161 Lost World</a></li>
<li><b>More photos:</b>
@ -29,5 +30,6 @@ Kaninchenh&ouml;hle.
<li><a href="../../../areas.htm">Other Areas</a></li>
<li><a href="../../../index.htm">Back to Expedition Intro page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/l/dh2-33.htm
View File

@ -16,6 +16,7 @@ Kaninchenh&ouml;hle.
<!-- Photo scanned 1200x1600 on Coolscan at 1350 dpi, 1997.10, AERW -->
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><a href="../pixlw.htm#wap">Visual tour of 161 Lost World</a></li>
<li><b>More photos:</b>
@ -28,5 +29,6 @@ Kaninchenh&ouml;hle.
<li><a href="../../../areas.htm">Other Areas</a></li>
<li><a href="../../../index.htm">Back to Expedition Intro page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/l/dh3-06.htm
View File

@ -16,6 +16,7 @@ Kaninchenh&ouml;hle.
<!-- Photo scanned 1800x1200 on Coolscan at 1350 dpi, 1997.10, AERW -->
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><a href="../pixsf.htm#penguin">Visual tour of 161d</a></li>
<li><b>More photos:</b>
@ -28,5 +29,6 @@ Kaninchenh&ouml;hle.
<li><a href="../../../areas.htm">Other Areas</a></li>
<li><a href="../../../index.htm">Back to Expedition Intro page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/l/dh3-11.htm
View File

@ -16,6 +16,7 @@ Unfortunately, we're not yet quite sure where...
<!-- Photo scanned on Coolscan at 1350 dpi, 1997.10, AERW -->
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><a href="../pixsf.htm#akinph">Visual tour of 161 Lost World</a></li>
<li><b>More photos:</b>
@ -28,5 +29,6 @@ Unfortunately, we're not yet quite sure where...
<li><a href="../../../areas.htm">Other Areas</a></li>
<li><a href="../../../index.htm">Back to Expedition Intro page</a></li>
</ul>
</div>
</body>
</html>

2
1623/161/l/dh_dns.htm
View File

@ -16,6 +16,7 @@ constricted head of an as-yet-unidentified pitch.
<!-- Scanned on Coolscan 600x900 at 675dpi, 1997.08.08, AERW -->
<hr />
<!-- LINKS -->
<div id="menu">
<ul id="links">
<li><a href="../drunk.htm">Back to cave description</a></li>
<li><a href="../../index.html#id161">Schwarzmooskogel ridge area</a></li>
@ -23,5 +24,6 @@ constricted head of an as-yet-unidentified pitch.
<li><a href="../../../areas.htm">Other Areas</a></li>
<li><a href="../../../index.htm">Back to Expedition Intro page</a></li>
</ul>
</div>
</body>
</html>

64
1623/161/pixrh.htm
View File

@ -8,23 +8,20 @@ Kaninchenh&ouml;hle Picture gallery - "old" cave thumbnails
<link rel="stylesheet" type="text/css" href="../../css/main2.css" />
</head>
<body>
<p><center><a href="top.htm"><img alt="Overview "
src="../../../icons/ovview.png" width=40 height=40></a>
<a href="pixsf.htm"><img alt=" New Cave "
src="../../../icons/vtour.png" width=40 height=40></a>
<img alt="Rigging" src="../../../icons/rigbut.png" width=40 height=40>
<a href="names.htm"><img alt=" Glossary "
src="../../../icons/idx161.png" width=40 height=40></a>
<a href="../index.html#id161"><img alt=" Desc "
src="../../../icons/desc.png" width=40 height=40></a>
<a href="../../index.htm"><img alt=" Expo "
src="../../../icons/ausbut.png" width=40 height=40></a>
<a href="../../infodx.htm"><img alt=" Topics "
src="../../../icons/index.png" width=40 height=40></a>
<a href="../../indxal.htm"><img alt=" Index "
src="../../../icons/indxal.png" width=40 height=40></a>
<a href="../../../index.htm"><img alt=" CUCC"
src="../../../icons/cucc.png" width=40 height=40></a></center>
<p>
<center>
<a href="top.htm"><img alt="Overview " src="../../../icons/ovview.png" width=40 height=40></a>
<a href="pixsf.htm"><img alt=" New Cave " src="../../../icons/vtour.png" width=40 height=40></a>
<img alt="Rigging" src="../../../icons/rigbut.png" width=40 height=40>
<a href="names.htm"><img alt=" Glossary " src="../../../icons/idx161.png" width=40 height=40></a>
<a href="../index.html#id161"><img alt=" Desc " src="../../../icons/desc.png" width=40 height=40></a>
<a href="../../index.htm"><img alt=" Expo " src="../../../icons/ausbut.png" width=40 height=40></a>
<a href="../../infodx.htm"><img alt=" Topics " src="../../../icons/index.png" width=40 height=40></a>
<a href="../../indxal.htm"><img alt=" Index " src="../../../icons/indxal.png" width=40 height=40></a>
<a href="../../../index.htm"><img alt=" CUCC" src="../../../icons/cucc.png" width=40 height=40></a>
</center>
</p>
<h1>Kaninchenh&ouml;hle Picture gallery<br>
The Right Hand Route - from 161a</h1>
@ -33,7 +30,7 @@ The Right Hand Route - from 161a</h1>
description, but are also gathered together here for a visual tour of
Kaninchenh&ouml;hle. Clicking on an image will take you to a bigger version
with descriptive caption and links back to web pages relevant to that
picture.
picture.</p>
<h2>The Right Hand Route - from 161a</h2>
@ -201,20 +198,23 @@ The <a href="pixss.htm">Steinschlagschacht</a> (1623/136) route
<hr />
<!-- LINKS -->
<ul id="links">
<li><b>More Pictures:</b>
<ul>
<li><a href="../../gallery/cave.htm">Underground</a> in some of our other caves</li>
<li><a href="../../gallery/ents.htm">Entrance</a> portraits</li>
<li><a href="../../gallery/surf.htm">Surface</a> routes and views</li>
<li><a href="../../gallery/low.htm">Base camp and non-caving</a> activities</li>
</ul></li>
<li><a href="top.htm">Kaninchenh&ouml;hle</a> Cave Description - Overview</li>
<li><a href="../../index.htm">Back to Expedition Intro page</a></li>
<li><a href="../../infodx.htm">Index to info/topic pages</a></li>
<li><a href="../../areas.htm">Area/subarea descriptions</a></li>
<li><a href="../../../index.htm">Back to CUCC Home page</a></li>
</ul>
<div id="menu">
<ul id="links">
<li><b>More Pictures:</b>
<ul>
<li><a href="../../gallery/cave.htm">Underground</a> in some of our other caves</li>
<li><a href="../../gallery/ents.htm">Entrance</a> portraits</li>
<li><a href="../../gallery/surf.htm">Surface</a> routes and views</li>
<li><a href="../../gallery/low.htm">Base camp and non-caving</a> activities</li>
</ul>
</li>
<li><a href="top.htm">Kaninchenh&ouml;hle</a> Cave Description - Overview</li>
<li><a href="../../index.htm">Back to Expedition Intro page</a></li>
<li><a href="../../infodx.htm">Index to info/topic pages</a></li>
<li><a href="../../areas.htm">Area/subarea descriptions</a></li>
<li><a href="../../../index.htm">Back to CUCC Home page</a></li>
</ul>
</div>
</body>
</html>

4261
caves-tabular.htm Normal file
View File

File diff suppressed because it is too large Load Diff

52
css/cavetables.css Normal file
View File

@ -0,0 +1,52 @@
body {
all: initial;
font-size: 100%;
}
div#inputf {
display: inline-block;
width: 300px;
text-align: justify;
margin-top: 0px;
margin-bottom: 5px
}
.menu, ul#links{
display: none;
}
table {
border-spacing: 0;
width: 100%;
border: 1px solid #ddd;
font-family: monospace;
}
th {
cursor: pointer;
background-color: #bbb
}
th, td {
padding: 16px;
max-height: 40px;
}
tr:nth-child(even) {
background-color: #f2f2f2
}
p {
margin-right: 80px;
margin-left: 80px;
}
button {
width: 300px
}
span#mono {
font-family: monospace;
background-color: #eee;
font-size: 120%;
}

22
css/main2.css
View File

@ -5,6 +5,7 @@
#008787 darker blue for fonts
#004C4C very dark
*/
body {
background: #fff url(../images/style/bg-cambridge-caving-expedition.png) repeat-x 0 0;
color: #000;
@ -13,8 +14,9 @@ body {
margin-left: 275px;
margin-right: 100px;
text-align: justify;
max-width: 800px;
/*max-width: 800px;*/
}
body#homepage {
background: #008787 url(../images/style/homebackground.jpg) no-repeat 0 0;
background-size: 140% auto;
@ -303,6 +305,8 @@ textarea#id_html {
}
/*RULES OVERRIDING JQUERY CSS FOR CAVES DESCRIPTION*/
/*This method is faster but less efficient. These would better be directly written in the jquery css file currently in http://expo.survex.com/site_media/css/redmond/jquery-ui-1.8.14.custom.css*/
@ -379,3 +383,19 @@ body .ui-state-default a:link:hover,
body .ui-state-default a:visited:hover {
color: #E17009;
}
/*Narrow screens support*/
/*Added 2019-02-22 by Radost Waszkiewicz*/
@media only screen and (max-width: 600px), screen and (max-aspect-ratio: 5/4)
{
ul#links {
position: static;
}
body {
margin-left: 100px;
margin-right: 100px;
}
}

2
folk/author.htm
View File

@ -80,7 +80,7 @@
<p>The large mass of cave descriptions have been taken from guidebook descriptions or exploration reports by the above authors, or translated from publications of groups listed under <a href="../others/index.htm">Other Groups</a>. We'd like to thank the librarian of the F&eacute;d&eacute;ration Belgique de Sp&eacute;l&eacute;ologie for supplying photocopies of articles, and Jill Gates (ULSA and NPC) for help with translation.</p>
<p>Certain parts of the <a href="../handbook/index.htm">Expedition Handbook</a> are derived from earlier documents used by other clubs, most especially the <a href="http://www.oucc.org.uk/">Oxford University Caving Club</a>. This particularly includes the <a href="../handbook/rescue.htm">Rescue guide</a>, which owes much to Gavin Lowe. <!--If you are browsing locally, you may also find a mirror of the well-illustrated <a href="../handbook/3rdparty/sherry/srtrig.htm" _mce_href="../handbook/3rdparty/sherry/srtrig.htm">SRT rigging guide</a> produced by Sherry Mayo with contributions from Mark Bown. If that link doesn't work, (which it won't if you are browsing over the "real" internet), then the original is <a href="http://www.cavepage.magna.com.au/cave/SRTrig.html" _mce_href="http://www.cavepage.magna.com.au/cave/SRTrig.html">here</a>.--> <!-- For some reason the server hosting that site is case-sensitive for file names. Yes, I know this is ludicrous. --></p>
<p>The editors would like to thank the discoverers of Kaninchenh&ouml;hle for finding a cave so complex that hypertext seemed the only way to build a usable guidebook description. Without the start that this gave, the website might never have come about. Andy Waddington started the major rewrite of the description in an effort to understand the cave without having to make the sacrifice of going underground. The endless questions that this provoked stimulated Wookey and others to join the work. HTML provides the means to keep linking in new bits of material interminably and Wookey provided the stimulus to make it more cohesive by finding the space on a real web site. We'd also like to thank everyone who has browsed these pages and made constructive comments or reported bugs.</p>
<p><a name="maintainers"></a>Finally, both exploration and documentation continue. The editors welcome your <!-- a href="../../fdback.htm" -->feedback on the existing site or contributions of writing or photographs of the area. In recent years maintenance of the website has been to some extent devolved, so that members of the expedition have responsibility for documenting their own finds; see the <a href="../update.htm">updates</a> page. Nonetheless all the kudos for creating the edifice should go to the two original editors, both of whom are still working on the site:</p>
<p><a name="maintainers"></a>Finally, both exploration and documentation continue. The editors welcome your <!-- a href="../../fdback.htm" -->feedback on the existing site or contributions of writing or photographs of the area. In recent years maintenance of the website has been to some extent devolved, so that members of the expedition have responsibility for documenting their own finds; see the <a href="../handbook/onlinesystems.html">updates</a> page. Nonetheless all the kudos for creating the edifice should go to the two original editors, both of whom are still working on the site:</p>
<p>Andy Waddington<br /> mail: &lt;expo (at) pennine.ddns.me.uk&gt;<br /> Andy's own <a href="http://www.pennine.ddns.me.uk/blog/andrew">blog pages</a></p>
<p>Wookey<br /> mail: &lt;Wookey (at) aleph1.co.uk&gt;<br /> Wookey's own <a href="http://wookware.org/">homepage</a></p>
<hr />

52
gallery/0.htm
View File

@ -16,30 +16,34 @@ tried to gather together logical groups of pictures for visual tours of
CUCC's caving area.</p>
<!-- LINKS -->
<ul id="links">
<li><b>The Pictures:</b>
<ul>
<li><b>Kaninchenh&ouml;hle</b>
<ul>
<li><a href="../1623/161/pixrh.htm">Virtual tour</a>
from <b>top entrance - 161a</b></li>
<li><a href="../1623/161/pixsf.htm">Virtual tour</a>
from <b>Scarface entrance - 161d</b></li>
<li>the <a href="../1623/161/pixlw.htm">Lost World</a>
and Wheelchair Access;</li>
<li>the new way into the Forbidden Land via
<a href="../1623/161/pixss.htm">Steinschlagschacht</a>.</li>
</ul></li>
<li><a href="cave.htm">Underground</a> in some of our other caves</li>
<li><a href="ents.htm">Entrance</a> portraits</li>
<li><a href="surf.htm">Surface</a> routes and views</li>
<li><a href="low.htm">Base camp and non-caving</a> activities</li>
</ul></li>
<li><a href="../index.htm">Back to Expedition Intro page</a></li>
<li><a href="../infodx.htm">Index to info/topic pages</a></li>
<li><a href="../areas.htm">Area/subarea descriptions</a></li>
<li><a href="../../index.htm">Back to CUCC Home page</a></li>
</ul>
<div id="menu">
<ul id="links">
<li><b>The Pictures:</b>
<ul>
<li><b>Kaninchenh&ouml;hle</b>
<ul>
<li><a href="../1623/161/pixrh.htm">Virtual tour</a>
from <b>top entrance - 161a</b></li>
<li><a href="../1623/161/pixsf.htm">Virtual tour</a>
from <b>Scarface entrance - 161d</b></li>
<li>the <a href="../1623/161/pixlw.htm">Lost World</a>
and Wheelchair Access;</li>
<li>the new way into the Forbidden Land via
<a href="../1623/161/pixss.htm">Steinschlagschacht</a>.</li>
</ul>
</li>
<li><a href="cave.htm">Underground</a> in some of our other caves</li>
<li><a href="ents.htm">Entrance</a> portraits</li>
<li><a href="surf.htm">Surface</a> routes and views</li>
<li><a href="low.htm">Base camp and non-caving</a> activities</li>
</ul>
</li>
<li><a href="../index.htm">Back to Expedition Intro page</a></li>
<li><a href="../infodx.htm">Index to info/topic pages</a></li>
<li><a href="../areas.htm">Area/subarea descriptions</a></li>
<li><a href="../../index.htm">Back to CUCC Home page</a></li>
</ul>
</div>
</body>
</html>

2
handbook/abbrev.htm
View File

@ -41,7 +41,7 @@ use this abbreviation.</td></tr>
<li><a href="survey/index.htm">Surveying guide</a> - Overview</li>
<li><a href="look4.htm">Prospecting guide</a> &ndash; Overview
<li><a href="rescue.htm">Rescue guide</a></li>
<li><a href="rigit.htm">Rigging guide</a></li>
<li><a href="rig/rigit.html">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>

2
handbook/bankofexpo.html
View File

@ -33,7 +33,7 @@ Here is the <a href="bocdoc.pdf">the original documentation</a> (PDF). It's a b
<li><a href="survey/index.htm">Surveying guide</a> - Overview</li>
<li><a href="look4.htm">Prospecting guide</a> &ndash; Overview</li>
<li><a href="rescue.htm">Rescue guide</a></li>
<li><a href="rigit.htm">Rigging guide</a></li>
<li><a href="rig/rigit.html">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>

183
handbook/c21bs.html Normal file
View File

@ -0,0 +1,183 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<title>CUCC Website Genesis</title>
<link rel="stylesheet" type="text/css" href="../css/main2.css" />
</head>
<body>
<h2 id="tophead">CUCC Expedition Handbook - Expo Website Genesis</h2>
<h1>Taking Expo Bullshit into the 21st Century</h1>
<p align="center"><em>Cambridge Underground 1996, pp 61-62</em></p>
<p><b><i>by AERW</i></b></center>
<p>[This article was published in CU 1996, shortly after the site was put
on the web. The text is reproduced without change, but the URLs were
updated (in 2006) to reflect the then location of these pages.]
<p>For many years, the only documentation of CUCC's activities in Austria
comprised the Log Books written "in the field" and an article or two in the
annual "Cambridge Underground". A few write ups appeared in "BCRA Caves and
Caving" or "Descent", and occasionally a lecture would occur at the BCRA
Conference. The standard of underground surveying was poor and, for the most
part, surface surveying was non-existant. Often the only way to find some of
the earlier cave discoveries was to collar the people who found them and get
them to show you. Regrettably, even this didn't always work. Looking for
going leads often involved grovelling on the floor of the Potato Hut to
find an old logbook in a tatty cardboard box, then wading through it to
find the relevant write up and trying to make some sense of it. All this
before even going underground !
<p>Today, we exchange survey data with other groups working in the area, and
all of CUCC's internal and published documentation is available in a few
minutes anywhere in the world. Logbook write-ups are linked to cave
descriptions, maps, and even colour photos, and "every" going lead or
prospect is cross-referenced to the cave description. What on earth
happened to bring this all about&nbsp;?
<p>Two things - technology, and Kaninchenh&ouml;hle. The technology made it
all possible, and Kaninchenh&ouml;hle provided the stimulus to do it.
<p>To explain: for many years, Andy had been quietly sticking all of CUCC's
cave descriptions, together with what translations of Austrian ones I could
get/make, into a catalogue of caves which was supposed to be useful in
Austria to prevent duplication of effort, and to avoid losing caves
completely. A printed version occupied a very hefty ring-binder and was not
found tremendously useful, particularly as maps were somewhat lacking. Trying
to get the information to keep it any less than about five years out of date
was also a losing battle. Some of the cave descriptions are inevitably quite
complex, and Kaninchenh&ouml;hle, in particular, has so many side leads and
connections between main routes that the description was becoming impossible
to understand.
<p>It is a feature of complex cave descriptions that the main route becomes
hard to follow as more and more side passages get into the description.
If the side passages are instead described somewhere else, then it is equally
difficult to follow the route to the going leads at their ends. There doesn't
seem to be an effective solution to this in a printed guidebook, but by
writing the description in hyper-text, the side passage descriptions can
be removed from the main route without making them inaccessible. At each
junction, the passage is merely noted, and the main description continues.
But the note includes a LINK which can instead be followed to read the
full description of the side passage.
<p>This approach was adopted for the KH description and proved rather
successful. However, the resulting description lacked context, and soon links
appeared to various other text files, which in turn were turned into
hypertext. The process gradually took off, until by last year's (1995)
expedition, all the cave descriptions were in this form, with additional
material to describe each area on the surface and the approaches to use to
get there. There were also a few photographs in the archive, though hardly
enough to be useful.
<p>A few journal articles and some of the older logbooks were also on disc,
and it immediately became obvious that the value of these could be
enhanced by adding links to the other material. Hence a cave description
could have a link to the trip which discovered it; trips could be linked
to the previous and subsequent trips to the same place (not necessarily
in the same logbook) and journal articles could likewise be linked to
the relevant cave description.
<p>As the process took off, the gaps became more obvious, so progressively
more logbooks have been transcribed and journal articles either retrieved
from mouldering floppies or typed in afresh. Some early (and painful)
attempts to represent logbook sketches in ascii text have been superceded
by scanned-in material and the archive continued to build.
<p>All of this represented a considerable amount of work, and the danger with
such things is always that it will get lost, neglected or fall into disuse.
However, stuff on disc can always be distributed to many people, in the
hope that even if disaster befalls one copy of the archive, someone else
will have an intact copy. In this way, hundreds of kilobytes of updated
descriptions were soon passing backwards and forwards by email between
Andy and Wookey each week. But the material was still only available to
a tiny handful of people.
<p>The format in which all this work had been carried out was, from the very
start, the very same format which was needed to make it widely available
on the Internet in the form of World-Wide-Web pages. Soon, Wookey managed
to find us a server which would put it all up for global access. This
revealed a very large number of problems with the system, but a couple
of weeks work fixed most of these. A Cambridge University Caving Club
home page was created, and the expedition archive (by now around five
hundred separate files) hung below this. The CUCC pages are still a bit
limited (the Home page, a brief description of the club and one of exCS,
and an (old) version of the Novice's Guide to CUCC). However, it is
hoped that CUCC itself will provide up-to-the-minute pages covering current
club activities and perhaps even a weekly copy of the club newsletter&nbsp;?
<p>It is hoped that by the time you are reading this, all the extant logbooks
and all the Cambridge Underground articles will be on the server, together
with fully up-to-date descriptions of all CUCC's caves that we still have
info for. The "Expedition slide set" which has been in gestation for over
five years might even come together this year, in which case a Photo-CD
can be made and a lot of much more useful pictures added to the archive.
This is by no means the end of the road however. There are still many
surveys and logbook sketches to scan, and we have a clickable map of the
surface to take you straight to the cave descriptions (but unfortunately
the server does not yet support this). There is foreign material from other
groups in the area to add, and we have links to another web site being run
by one of the German groups working in the area. The format allows for
things like video clips and sound, as well as text and photos so we have
the tantalising prospect of bringing a load of drunken students singing
"Wild Caver" to your computer screen...
<p>However, like the caves themselves, the web site is not easy to describe
in printed text. We hope you'll try it for yourself, get enthused about expo,
and want to come along and contribute. We hope it's structured so that you
can find your way about fairly easily - if you have problems, please let us
know so that we can fix it during the ongoing process of development. To ease
your way, here are a few selected entry points. Note that the names are
case-sensitive, and that the initial "cucc" is lower case.
<p>[<em>All those links are now incorrect and don't work. They have been commented-out. Press ctrl-U if you want to see them.</em>]
<!--
<dl>
<dt>CUCC Home page
<dd><a href="index.htm">http://www.chaos.org.uk/cucc/</a>
<dt>Expo Home page
<dd><a href="expo/">http://www.chaos.org.uk/cucc/expo/index.htm</a>
<dt>Colour pictures
<dd><a href="expo/gallery/0.htm">http://www.chaos.org.uk/cucc/expo/gallery/0.htm</a>
<dt>Kaninchenh&ouml;hle
<dd><a href="expo/smkridge/161/top.htm">http://www.chaos.org.uk/cucc/expo/smkridge/161/top.htm</a>
<dt>New entrance
<dd><a href="expo/smkridge/161/sftotp.htm">http://www.chaos.org.uk/cucc/expo/smkridge/161/sftotp.htm</a>
<dt>Stellerweg etc.
<dd><a href="expo/smkridge/41/41.htm">http://www.chaos.org.uk/cucc/expo/smkridge/41/41.htm</a>
<dt>LogBooks
<dd>http://www.chaos.org.uk/cucc/expo/years/&lt;year&gt;/log.htm
where &lt;year&gt; is 1976, 1977, ... 1995
<dt>Index of articles
<dd><a href="expo/pubs.htm">http://www.chaos.org.uk/cucc/expo/pubs.htm</a>
<dt>Index of caves
<dd><a href="expo/indxal.htm">http://www.chaos.org.uk/cucc/expo/indxal.htm</a>
<dt>Recent changes
<dd><a href="expo/update.htm">http://www.chaos.org.uk/cucc/expo/update.htm</a>
</dl>
-->
<p>If there's anything you think is wrong, anything you think is missing, or
anything you have to offer to add, please get in touch at
<p>Andy Waddington (mailbox 'Austria' on site 'pennine.demon.co.uk')<br>
Wookey (mailbox 'Wookey' on site 'aleph1.co.uk')
<p>and finally, the entire web edifice will be out in Austria [in 1997] on one or more
machines in the Potato hut for expo members to browse through (and add to)
to answer all your questions about the caves of the Loser Plateau&nbsp;! If
enough interest is shown, and enough photographs digitised, the current
"state-of-the-art" may be put onto CD-ROM. The site has outgrown floppies,
but can still be fitted onto a ZIP disc so, for the time being, if you
haven't got Internet connectivity, the edifice can be supplied on disc.
<p>Andy Waddington
<p><hr>
</body>
</html>

2
handbook/checkin.htm
View File

@ -29,7 +29,7 @@ hg push<br/></body>
<li><a href="survey/index.htm">Surveying guide</a></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="rig/rigit.html">Rigging guide</a></li>
<li><a href="photo.htm">Photography guide</a></li>
</ul></li>
<li><a href="../infodx.htm">Index to info/topics</a></li>

2
handbook/cockup.htm
View File

@ -93,7 +93,7 @@ other caves.</p>
<li><a href="look4.htm">Prospecting guide</a> &ndash; Overview
<li><a href="rescue.htm">Rescue guide</a></li>
<li><a href="rigit.htm">Rigging guide</a></li>
<li><a href="rig/rigit.html">Rigging guide</a></li>
<li><a href="photo.htm">Photography guide</a></li>
</ul></li>

2
handbook/computer.html
View File

@ -52,7 +52,7 @@ are advised to use the <em>Expo laptop</em> first to see how it all works.</p>
<p>Either the <em>Expo laptop</em> or your own laptop will use the version control system to
synchronise cave data. It's easier to use the <em>Expo laptop</em> as the software is already set up.
But if you set up your own computer then you will get a more familiar environment. See
the <a href="update.htm">Expo Online Systems Manual</a> for info on how to do that.</p>
the <a href="onlinesystems.html">Expo Online Systems Manual</a> for info on how to do that.</p>
<P>Through the miracle of the distributed version control system, everyone can edit the
data on multiple laptops at the same time and it should all get merged.</p>

58
handbook/computing/datamgt.html Normal file
View File

@ -0,0 +1,58 @@
<html>
<head>
<title>CUCC Expo Handbook - Data Management</title>
<link rel="stylesheet" type="text/css" href="../css/main2.css" />
</head>
<body>
<h2 id="tophead">CUCC Expedition Handbook - Data Management</h2>
<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
data. Aside from the data collection requirements of the game itself, setting up a game (an
expedition) of cave exploration often involves collection of personal information ranging from
dates available to medical information to the desire to purchase an expedition t-shirt.
<p>
If an expedition will only happen once, low-tech methods are usually adequate to record
information. Any events that need to be recorded can go in a logbook. Survey notes must be
turned into finished cave sketches, without undue concern for the future expansion of those sketches.
<p>
However, many caving expeditions are recurring, and managing their data is a more challenging
task. For example, let us discuss annual expeditions. Every year, for each cave explored, a list
of unfinished leads (which will be called "Question Marks" or "QMs" here) must be maintained to
record what has and has not been investigated. Each QM must have a unique id, and information
stored about it must be easily accessible to future explorers of the same area. Similarly, on
the surface, a "prospecting map" showing which entrances have been investigated needs to be
produced and updated at least after every expedition, if not more frequently.
<p>
These are only the minimum requirements for systematic cave exploration on an annual expedition.
There is no limit to the set of data that would be "nice" to have collected and organized
centrally. An expedition might collect descriptions of every cave and every passage within every
cave. Digital photos of cave entrances could be useful for re-finding those entrances. Scans of
notes and sketches provide good backup references in case a question arises about a finished
survey product, and recording who did which survey work when can greatly assist the workflow,
for example enabling the production of a list of unfinished work for each expedition member. The
expedition might keep an inventory of their equipment or a catalog of their library. Entering
the realm of the frivolous, an expedition might store mugshots and biographies of its members,
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 />
</body>
</html>

98
handbook/computing/essentials.html Normal file
View File

@ -0,0 +1,98 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<title>Essential GPS information</title>
<link rel="stylesheet" type="text/css" href="../css/main2.css" />
</head>
<body>
<h2 id="tophead">CUCC Expedition Handbook</h2>
<h1>Essential GPS information</h1>
<p>We have a regularly-updated file of all the cave entrances for the entire Schvartzmoosk&ouml;gel system (SMK).
This file also includes the tracks of the paths we regularly take: from Loser Alm car park to the col and to top camp,
and from top camp to Fisch Gesicht H&ouml;hle and to Tunnocks's, Balkonh&ouml;hle and Organh&ouml;hle.
<h3><a href="#down">Download the data from the expo server</a></h3>
<h3><a href="#up">Upload the data to your device</a></h3>
<h2 id="down">Download the GPS essentials file from the expo server</h2>
<p>
We regularly create a new version of this essential data as the expo progresses and as expoers discover new entrances and
devise new routes to reach them.
<p>
To get the most recent version you will need to ask someone who is competent in using the version control system
(it's in loser/gpx/ and is generated from the survex data by a script). A fairly recent copy (17 July 2018)
can be downloaded from here: <a href="essentials.gpx" download>essentials.gpx</a> (190K).
Phones have a problem with a simple link like that. So with a phone you may need to try this link
<a href="https://www.wikiloc.com/outdoor-trails/carpark-stonebridge-27029006&utm_source=social&utm_medium=twitter.com&utm_campaign=badge">
Wikilocs</a>
from where you can download a short version of the file (track and one waypoint at StoneBridge only) or a Google Earth trail (you need to create a Wikiloc account first <em>and be logged-in</em> when you click on this). Or here is another <a href="https://www.wikiloc.com/wikiloc/download.do?id=27029006">direct download link</a>.
<h2 id="up">Upload the GPS essentials file to your device</h2>
<p>
This is where it gets tricky because every device and phone app does this differently.
<h3>GPS phone apps</h3>
<p>
This should work the same way whether you have an iPhone or an Android phone.
<p>We do not have a recommended app as there is nothing we have found which quite does quite what we need. We are using
<a href="http://www.gpsessentials.com/">www.gpsessentials.com</a> and <a href="https://osmand.net/">OsmAnd</a> so try one of these first. If you discover a good app, tell everyone about it.
<p>
Visit the <a href="http://www.gpsessentials.com/">www.gpsessentials.com</a> website and read the manual (top left, on the menu bar: "Manual") for how to do this.
Except that the manual doesn't tell you.
<p>The OsmAnd documentation says:
<ul>
<li>"The simplest way to view a track you've downloaded is to tap on it in your device's file manager and choose to open it in OsmAnd. After that, you'll see the track in My places - My tracks or in the Dashboard - My tracks."
</ul>
<p>
More documentation on this to follow...
<h3>Modern Garmin handheld GPS devices</h3>
<p>
Connect the GPS device to your laptop (or the expo laptop) using the USB cable. A folder will open on the laptop showing the contents
of the device.
You will see a subfolder called "GARMIN". Open the folder "GARMIN" and copy the file essentials.gpx which you
downloaded into that folder.
<h3>Old Garmin handheld GPS devices</h3>
<p>
These need the Garmin communication protocol to import cave entrance locations (waypoints) and paths (tracks). You can't do it by simply copyingfiles.
This means that you need special software on your laptop in addition to a USB cable that connects your laptop to the Garmin device.
<p>
<figure><a href="https://www.cablestogo.com/learning/connector-guides/usb">
<img src="t/usb-minib-5pin-m-c.jpg"'
alt="mini-USB socket"
/></a>
<figcaption><em>mini-USB b socket</em></figcaption>
</figure>
If your Garmin has a <b>mini</b>-USB socket, rather than the usual micro-USB found in phones, then you might have an "old" Garmin handheld, but some modern handhelds still use this old socket.
<p>Once you have the right cable and connected your handheld to your laptop:
<ul>
<li>On a Windows machine, use "GPSbabel for Windows" which has an easy to use graphical user interface:
<a href="https://www.gpsbabel.org/download.html">download GPS Babel</a>
<li>On a Linux machine the core gpsbabel command line utility is probably already installed;
but there is no simple, easy to use graphical interface.
Instead you must use other software such as QGIS or Viking (download using your usual Linux software installer)
which uses gpsbabel to talk to your device.
If this doesn't work then there are no useful error messages from Viking.
</ul>
<hr />
<ul id="links">
<li><a href="index.htm">Expedition Handbook</a>
<ul>
<li><a href="survey/index.htm">Surveying guide</a> - Overview</li>
<li><a href="look4.htm">Prospecting guide</a> &ndash; Overview</li>
<li><a href="rescue.htm">Rescue guide</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>

31
handbook/computing/exposerver.html Normal file
View File

@ -0,0 +1,31 @@
<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 Cambridge</h1>
<p>The server hosts
<a href="http://expo.survex.com">expo.survex.com</a>.
<p>It lives (2018) under Sam Wenham's desk. Sam works for the University Computing Service (UCS), University of Cambridge,
so this is a secure place.
<p>We interact with it using:
<ul>
<li>TortoiseHg - communicating with hg running on the server - for the DVCS
<a href="../../repositories">repositories</a> expoweb, loser, tunnelx, tunneldata.
<li>FTP - mostly for uploading to /expofiles/
<li>ssh - occasionally, by experts,to fix things when something goes wrong or for major site reconfiguration.
</ul>
Now readthe <a href="manual.html#manual">Expo data management systems manual</a>.
<hr />
<ul id="links">
<li><a href="index.htm">Expedition Handbook</a>
</ul>
</body>
</html>

68
handbook/computing/ftpusage.html Normal file
View File

@ -0,0 +1,68 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>CUCC Expedition Handbook: Uploading files/photos</title>
<link rel="stylesheet" type="text/css" href="../css/main2.css" />
</head>
<body>
<h2 id="tophead">CUCC Expedition Handbook</h2>
<p>There are essentially two ways of using expo server: one is just FTP, second using version controll.
<strong>If you can handle version controll use that!</strong> Find detailed instructions on <a href="repousage.html">repo usage</a> page.</p>
<h1>Using expo server via FTP connection</h1>
<h2>Configure connection on Windows</h2>
<ul>
<li>Get <a href="https://winscp.net/eng/download.php">WinScp</a> application to handle uploads or similar:<br>
<img src="./tutorialimgs/winscp.jpg" width="500"></li>
<li>Click 'New site' in the popup window and fill in the data.<br>
<b>hostname:</b><i>expo.survex.com</i><br>
<b>user:</b><i>expo</i><br>
<b>password:</b>[contact your expedition leader for password]<br>
<img src="./tutorialimgs/newsite.jpg" width="500"></li>
<li>Click 'Login' to connect. You should be able to upload files now.</li>
</ul>
<hr>
<h2>Configure connection on Android phone</h2>
<ul>
<li>Get <a href="https://play.google.com/store/apps/details?id=com.cxinventor.file.explorer&hl=en">'Cx File Explorer'</a>:<br>
<img src="./tutorialimgs/cx_file_explorer.png" height="500">
</li>
<li>Press 'Network':<br>
<img src="./tutorialimgs/cx_network.png" height="500">
</li>
<li>Press 'plus' and 'remote':<br>
<img src="./tutorialimgs/cx_add.png" height="500">
</li>
<li>Press 'SFTP':</li>
<li>Fill in the data:<br>
<b>Host:</b><i>expo.survex.com</i><br>
<b>Port:</b><i>22</i><br>
<b>Username:</b><i>expo</i><br>
<b>Password:</b>[contact your expedition leader for password]<br>
<img src="./tutorialimgs/cx_sftp.png" height="500">
</li>
<li>Navigate to the image you want to upload. Then long press to select and press 'copy'<br>
<img src="./tutorialimgs/cx_copy.png" height="500">
</li>
<li>Navigate to expo.survex.com/home/expo/expofiles/uploads to avoid mess ;)<br>
<img src="./tutorialimgs/cx_paste.png" height="500">
</li>
<li>Press 'Paste' to finalize upload.</li>
<li>Done!</li>
</ul>
<hr>
<h2>Configure connection on Linux/Unix</h2>
<ul>
<li>You can upload files using 'scp' command (to upload localfile.file to expofiles/uploads/remotename.file)<br>
<pre>
scp loacalfile.file expo@expo.survex.com:~/expofiles/uploads/remotename.file
</pre>
</li>
</ul>
</body>
</html>

68
handbook/computing/getsurvex.html Normal file
View File

@ -0,0 +1,68 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<title>CUCC Expedition Handboo - Survey software</title>
<link rel="stylesheet" type="text/css" href="../css/main2.css" />
</head>
<body>
<h2 id="tophead">CUCC Expedition Handbook</h2>
<h1>Installing surveying tools</h1>
<h2>Survex</h2>
<p>The main software we use to process cave data and surface surveys is <b>survex</b>
which has been written over several decades by CUCC cavers.
The first version was written during the 1990 Expo in Austria in the (old) potato hut.
A <a href="survexhistory96.htm">history of survex</a> article was published in Cambridge Underground 1996. It covers the period 1988-1996.
<p>Download the survex package here: <a href="https://survex.com/">www.survex.com</a> and install it.
<p>You will discover that the application installed is actually called "aven" but do not be concerned.
This is what you will use to visualise .svx files as beautiful cave centre-line surveys.
<p>If you are entering new survey data from a new cave, you will also need either
<a href="https://bitbucket.org/goatchurch/tunnelx/wiki/Home">TunnelX</a> or
<a href="https://therion.speleo.sk/">Therion</a> to
convert your sketches into actual plan and elevation presentation-quality surveys.
<h2>TunnelX</h2>
<p>Tunnel was written by <a href="http://expo.survex.com/folk/l/jtodd.htm">Julian Todd</a> (18 Austrian expos since 1989). It allows the generation of full 3D models of cave passages which can be viewed using a VRML browser.
<p>
<a href="https://bitbucket.org/goatchurch/tunnelx/wiki/Home">TunnelX intro</a>.
<p>
<a href="https://bitbucket.org/goatchurch/tunnelx/wiki/Installing_and_Running">TunnelX installation and running</a>.
<p>
<a href="http://expo.survex.com/expofiles/tunnelwiki/wiki/pages/Tunnel.html">TunnelX detailed wiki documentation (old)</a>.
<h2>Therion</h2>
<p>
<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 />
</body>
</html>

103
handbook/computing/gpxupload.html Normal file
View File

@ -0,0 +1,103 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>CUCC Expedition Handbook: Uploading files/photos</title>
<link rel="stylesheet" type="text/css" href="../css/main2.css" />
</head>
<body>
<h2 id="tophead">CUCC Expedition Handbook</h2>
<h1>Uploading GPS tracks and locations</h1>
<h2>The end-result you are trying to achieve</h2>
What you are trying to do is to get your recorded locations (waypoints) and wanderings (tracks)
(a) are recorded somewhere, (b) eventually appear properly in the cave survey database and. You have to upload
the tracks and waypoints in a GPX file to the right place.
<p>If you are really lazy (or really a beginner) you can use the simple upload method, but there are some
unavoidable complexities in getting the GPX file out of your device.
<p><em>(If you are looking for how to upload some photos instead, those instructions are
<a href="uploading.html">here</a>)</em>.
<h3>Instructions: contents</h3>
<ol>
<li><a href="#getgpx">Get the GPX file</a> that holds your locations and wanderings from your phone.
<li><a href="#uploadgpx">Upload the GPX file</a> to the proper place.
</ol>
<h2 id="getgpx">Getting the GPX data out of your phone or device</h2>
<ol>
<li>Use the "Wikilocs" app (or another app with GPS tracking function) to record your track as you walk across the plateau.
<li>When you have finished your walk and are back on the internet, publish your track using the app.
<li>In the app,there is an option to "share" your track by email:
<ul>
<li>Share it with yourself i.e. email it to your own email address.
<li>Share it with someone who knows how to do the GPX thing and upload it properly.
</ul>
<li>On your laptop (or possibly on your phone) look at the email and visit the web page by clicking on the link.
<li>The web page has a "Download" button: click on it.
<li>It may give you options such as "Garmin", or "File". Choose "File".
<li>It will ask for a filename to use. Pick something like "northplat-asmith-2018-07-29" (if your name is Aaron Smith)
<li>A GPX file "northplat-asmith-2018-07-29.gpx" will be downloaded to the Downloads folder on your laptop.
</ol>
<p>
Congratulations. You now have your track recorded using GPS as a GPX file.
<h2 id="uploadgpx">Upload instructions</h2>
<h3>Simple upload instructions</h3>
<ol>
<li>Email the public link from the app to someone who knows how to do it. <br>
<li>Email the GPX file to someone who knows how to do it. <br>
GPX files are small enough for email systems, so don't be shy of adding them as attachments.
</ol>
<p>If you can't find someone who knows how to do it, find the most extreme nerd you can find and point them at the
<a href="#expert">Expert instructions</a> below.
<h3>Slightly less simple upload instructions</h3>
<p>Using your own laptop on expo, or after you return from expo,
use the "more complex" instructions for <a href="uploading.html">uploading photos</a> to /uploads/,
but upload your GPX files instead.
<h2 id="expert">Experts only</h2>
<p>
GPX data is stored in two places.
<ul>
<li>initially in <em>expofiles/gpslogs/...</em>
<li>some key selected tracks are later stored in the cave survey repository <em>::loser::</em>
</ul>
<p>
GPS tracks are voluminous and we also get a lot of repetition
as people tend to follow the same routes for part of their walks. So the initial raw data is kept in
<pre>
expofiles/gpslogs/&lt;year&gt;/&lt;MyName&gt;/
</pre>
e.g.
<pre>
expofiles/gpslogs/2018/PhilipSargent/
</pre>
<p>and you can create sub-folders for raw data and edited data, or for different parts of the plateau. You should always
keep the raw, untouched data as well as any hand-edited data.
<p>The process for uploading the GPX files to a specific folder <em>expofiles/gpslogs/...</em> is exactly the
same as for uploading photographs, so go to <a href="uploading.html#morecomplex">these "more complex" instructions</a>
to learn how to do it.
<p>Note the naming convention for this folder created by Philip Sargent in 2018.
Human names in folders in expofiles are written in CamelCase; not lower-case letters.
This is for consistency with the naming for
<a href="uploading.html#experienced">uploading photos</a>.
<p>
If you have edited GPS tracks and waypoints with no extraneous data
then, after agreeing this with other people as to its qualityand appropriateness,
it will go into the <a href="http://expo.survex.com/repositories/home/expo/loser/graph/">Loser DVCS repository</a>
in folder <em>/gpx/&lt;year&gt;/</em> e.g. <br>
<em>::loser::/2018/stone-bridge-to-fischgesicht_aday-2018-07-12.gpx</em><br>
<p>Note the naming convention for this file created by Anthony Day on July 12th 2018.
Everything in any repository is always named using lower-case letters.
<hr />
</body>
</html>

125
handbook/computing/logbooks.html Normal file
View File

@ -0,0 +1,125 @@
<html>
<head>
<title>CUCC Expedition Handbook: The Website</title>
<link rel="stylesheet" type="text/css" href="../css/main2.css" />
</head>
<body>
<h2 id="tophead">CUCC Expedition Handbook</h2>
<h1>Logbooks</h1>
<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.
<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>
<b>DO NOT</b> take a copy of the logbook.html file from the expo laptop,
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 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="onlinesystems.html#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>
<p>Do whatever you like to try and represent the logbook in html. The only rigid structure is the markup to allow troggle to parse the files into 'trips':</p>
<pre>
&lt;div class="tripdate" id="t2007-07-12B"&gt;2007-07-12&lt;/div&gt;
&lt;div class="trippeople"&gt;&lt;u&gt;Jenny Black&lt;/u&gt;, Olly Betts&lt;/div&gt;
&lt;div class="triptitle"&gt;Top Camp - Setting up 76 bivi&lt;/div&gt;
&lt;div class="timeug"&gt;T/U 10 mins&lt;/div&gt;
</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 (6 minutes would be "0.1 hours").
<hr />
<h3>Historical logbooks</h3>
<p>Older logbooks (prior to 2007) were stored as logbook.txt with just a bit of consistent markup to allow troggle parsing.</p>
<p>The formatting was largely freeform, with a bit of markup ('===' around header, bars separating date, <place> - <description>, and who) which allows the troggle import script to read it correctly. The underlines show who wrote the entry. There is also a format for time-underground info so it can be automagically tabulated.</p>
<p>So the format should be:</p>
<pre>
===2009-07-21|204 - Rigging entrance series| Becka Lawson, Emma Wilson, Jess Stirrups, Tony Rooke===
&lt;Text of logbook entry&gt;
T/U: Jess 1 hr, Emma 0.5 hr
</pre>
<hr />
<ul id="links">
<li><a href="index.htm">Expedition Handbook</a>
</ul>
</body>
</html>

32
handbook/computing/nerd.html Normal file
View File

@ -0,0 +1,32 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<title>Handbook placeholder page</title>
<link rel="stylesheet" type="text/css" href="../css/main2.css" />
</head>
<body>
<h2 id="tophead">CUCC Expedition Handbook</h2>
<h1>Placeholder</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 />
<div id="menu">
<ul id="links">
<li><a href="index.htm">Expedition Handbook</a>
<ul>
<li><a href="rig/rigit.html">Rigging guide</a></li>
<li><a href="survey/index.htm">Surveying guide</a></li>
<li><a href="look4.htm">Prospecting guide</a></li>
<li><a href="rescue.htm">Rescue guide</a></li>
</ul></li>
<li><a href="../infodx.htm">Main index</a></li>
<li><a href="../index.htm">Expo Home</a></li>
<li><a href="../../index.htm">CUCC Home</a></li>
</ul>
</div>
</body>
</html>

8
handbook/update.htm → handbook/computing/onlinesystems.html
View File

@ -19,7 +19,7 @@ handbook and public website are constructed and managed.
It contains material which will be merged into this online systems manual.
<p>These pages listed below have been reviewed recently (2018), and a
fuller list of "How do I..." instruction pages are on <a href="index.html">the handbook opening page</a>.
fuller list of "How do I..." instruction pages are on <a href="index.htm">the handbook opening page</a>.
<ul>
<li><a href="uploading.html">Uploading your photos</a></li>
@ -28,7 +28,7 @@ fuller list of "How do I..." instruction pages are on <a href="index.html">the h
<li><a href="survey/newcave.html">Recording a new cave discovery</a></li>
<li><a href="survey/status.html">Monitoring the status cave survey workflow during and after expo</a></li>
</ul>
<p>But the systems Manual is still being actively edited to extract and simplify documentaiton. At the moment
<p>But the systems Manual is still being actively edited to extract and simplify documentation. At the moment
it is the only documentation we have for:
<ul>
<li><a href="manual.html#update">Manual: Creating a new 'year' in the system</a></li>
@ -137,8 +137,8 @@ This is the "Edit this page" capability; see <a href="#editthispage">above for
how to use it</a> and how to tidy up afterwards.
</ol>
<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.
<p>See the <a href="troggle-ish.html">notes on troggle</a> page
for how and why it was developed and what needs to be done.
<hr />

43
handbook/computing/repousage.html Normal file
View File

@ -0,0 +1,43 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>CUCC Expedition Handbook: Uploading files/photos</title>
<link rel="stylesheet" type="text/css" href="../css/main2.css" />
</head>
<body>
<h2 id="tophead">CUCC Expedition Handbook</h2>
<p>There are essentially two ways of using expo server: one is just FTP, second using version controll.
<strong>If you can handle version controll use that!</strong>. Currently we're using HG wich is like GIT but a litte retarded.
<h1>Using expo server via version controll software connection</h1>
<h2>Configure on Windows</h2>
<ul>
<li>Get <a href="https://tortoisehg.bitbucket.io/">TortoiseHG</a> application to handle mercurial repo:<br>
<img src="./tutorialimgs/tortoisehg.png" width="300"></li>
<li>Install and open the app. The click 'clone':<br>
<img src="./tutorialimgs/hg_win_clone.png" width ="300">
</li>
<li>Configure as:<br>
<b>source:</b><i>ssh://expo@expo.survex.com/<b>expoweb</b></i>
(you can replace 'expoweb' with one of four repos we have on the server c.f. <a href="http://expo.survex.com/repositories">repositories</a>)<br>
<b>destination:</b> pick location on the local machine<br>
<img src="./tutorialimgs/hg_win_setup.png" width="300">
</li>
<li>Press 'clone'</li>
<li>You should now have a copy of the repo on your machine. Use commands 'commit','pull','push' as in any version controll system. (This page is not meant as version controll tutorial, pls just websearch something)</li>
</ul>
<hr>
<h2>Configure on Linux</h2>
<ul>
<li>Instal mercurial:<br>
<pre>sudo apt-get install mercurial</pre></li>
<li>Clone database:<br>
<pre>hg clone ssh://expo@expo.survex.com/expoweb ~/localdirofyourchoice</pre></li>
<li>You should now have a copy of the repo on your machine. Use commands 'commit','pull','push' as in any version controll system. (This page is not meant as version controll tutorial, pls just websearch something)</li>
</ul>
</body>
</html>

BIN
handbook/computing/tutorialimgs/cx_add.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 66 KiB

BIN
handbook/computing/tutorialimgs/cx_copy.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 84 KiB

BIN
handbook/computing/tutorialimgs/cx_file_explorer.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 209 KiB

BIN
handbook/computing/tutorialimgs/cx_network.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 70 KiB

BIN
handbook/computing/tutorialimgs/cx_paste.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 39 KiB

BIN
handbook/computing/tutorialimgs/cx_sftp.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 83 KiB

BIN
handbook/computing/tutorialimgs/hg_win_clone.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 12 KiB

BIN
handbook/computing/tutorialimgs/hg_win_setup.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 10 KiB

BIN
handbook/computing/tutorialimgs/newsite.jpg Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 57 KiB

BIN
handbook/computing/tutorialimgs/tortoisehg.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 167 KiB

BIN
handbook/computing/tutorialimgs/winscp.jpg Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 126 KiB

121
handbook/computing/uploading.html Normal file
View File

@ -0,0 +1,121 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>CUCC Expedition Handbook: Uploading files/photos</title>
<link rel="stylesheet" type="text/css" href="../css/main2.css" />
</head>
<body>
<h2 id="tophead">CUCC Expedition Handbook</h2>
<h1>Uploading Photos</h1>
<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.
<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>
<ol>
<li>Email a photo or two to someone who knows how to do it. <br>
(If you are doing more than a few photos, email will be clunky, so use another method).
<li>Use the Expo laptop in the tatty hut. Get someone to show you how to do it.
</ol>
<p>That's it. There used to be other ways of doing it using browser extensions but these either don't work anymore [since 2017] or the instructions to install them properly have become too complicated.
<p>Beginners should always put all their files into the folder <b>/home/expo/expofiles/uploads/</b> and ask an admin to move them to the right place.
<p>Now go to <a href="#init">using Filezilla initially</a> - still using the Expo laptop.
<h2 id="morecomplex">More complex instructions</h2>
<p>Using your own laptop on expo, or after you return from expo:
<ol>
<li>Download and install <b>Filezilla</b>.
</ol>
<p>You do need to know the expo password.</p>
<h3 id="install">Installing Filezilla</h3>
<p>This software works identically on both Windows and Linux.
<p>Filezilla is an "FTP client". This means that it connects to servers using a venerable service called "file transfer protocol" i.e. FTP. It looks a bit like copying files from one folder to another on your desktop but it works between different machines.
<ul>
<li> Download the software from here <a href="https://filezilla-project.org/download.php?show_all=1">Filezilla Downloads</a>. ( Obviously Linux users will use their usual package management system instead of doing this download.)
<li>Now install the software following <a href="https://wiki.filezilla-project.org/Client_Installation">the instructions here</a>.
<li>Now configure it to connect to the expo server using the instructions <a href="fzconfig.html">on this expo handbook page</a>
</ul>
<h2 id="init">Using Filezilla initially</h2>
<p>The expo website has a big section under 'home/expo/expofiles/' that is <b>not under version control</b>. This is dangerous as there is no backup. If you overwrite some important files with your holiday snaps then we are in big trouble. This is where we store big files that we don't want to keep multiple versions of which is why it is not under verson control.
<p>So beginners should always put all their files into the folder
<pre>/home/expo/expofiles/uploads/</pre> and then ask an admin to move them to the right place. The configuration which you just did (if you followed <a href="fzconfig.html">the instructions</a>) will set you up pointing at the correct folder automatically.
<p>
To make the admin's life easier, create your own folder in <pre>/home/expo/expofiles/uploads/</pre> with your name like this: <pre>/home/expo/expofiles/uploads/YourName/</pre> and put your files into that folder. ("YourName" should have no spaces, hyphens or underline characters.) So that the admin knpows who is responsible. And for goodness sake please don't upload lots of duplicate photos: cull them first to just the good ones.
<h2 id="experienced">Experienced users</h2>
<p>OK the admin/nerd you have been asking to move the files to the right place is getting fed up and now wants you to put the uploaded photos in the right place yourself. This is where they go:
<pre>
directory: /home/expo/expofiles/<b>photos</b>/2018/YourName/
</pre>
or, for GPS logs (GPX files):
<pre>
directory: /home/expo/expofiles/<b>gpslogs</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 "<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
at <a href="http://expo.survex.com/photos/">http://expo.survex.com/photos/</a> immediately. An update script needs to be run. This should run automatically once/day around midnight UTC (2017 and earlier) or a couple of minutes after you do the upload to the right place (2018 if Wookey gets this sorted out in time) but may be broken. Prod a web admin if nothing is updated by the next morning..</p>
<h2>Experts only</h2>
<p>If you have been using FTP since the last century or are particularly keen on doing everything using the command-line, read on.
<h3>Using scp</h3>
<p>Works on Windows (using winscp), Linux (using scp), and no doubt
mac and android with other tools. If you have Windows 10 and <a href="https://msdn.microsoft.com/en-gb/commandline/wsl/about">have installed bash</a>, then you can use scp.</p>
<p>If you don't have winscp installed you can get it from here:
<a href="http://winscp.net/eng/index.php">http://winscp.net/eng/</a>.</p>
<p>quick start guide:
<a href="http://winscp.net/eng/docs/getting_started">http://winscp.net/eng/docs/getting_started</a></p>
<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>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 />
</body>
</html>

2
handbook/cpne.htm
View File

@ -67,7 +67,7 @@ expedition cavers.</p>
<ul>
<li><a href="look4.htm">Prospecting guide</a></li>
<li><a href="survey/index.htm">Surveying guide</a></li>
<li><a href="rigit.htm">Rigging guide</a></li>
<li><a href="rig/rigit.html">Rigging guide</a></li>
<li><a href="photo.htm">Photography guide</a></li>
</ul></li>
<li><a href="../indxal.htm">Full Index to area 1623</a></li>

0
handbook/druginfo.htm → handbook/druginfo.html
View File

1
handbook/essentials.gpx
View File

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

2
handbook/findit.htm
View File

@ -98,7 +98,7 @@ identified the summits on the views with complete certainty :-)</p>
<li><a href="look4.htm">Prospecting guide</a></li>
<li><a href="survey/index.htm">Surveying guide</a></li>
<li><a href="rescue.htm">Rescue guide</a></li>
<li><a href="rigit.htm">Rigging guide</a></li>
<li><a href="rig/rigit.html">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>

2
handbook/getsurvex.html
View File

@ -11,6 +11,8 @@
<p>The main software we use to process cave data and surface surveys is <b>survex</b>
which has been written over several decades by CUCC cavers.
The first version was written during the 1990 Expo in Austria in the (old) potato hut.
A <a href="survexhistory96.htm">history of survex</a> article was published in Cambridge Underground 1996. It covers the period 1988-1996.
<p>Download the survex package here: <a href="https://survex.com/">www.survex.com</a> and install it.
<p>You will discover that the application installed is actually called "aven" but do not be concerned.
This is what you will use to visualise .svx files as beautiful cave centre-line surveys.

45
handbook/index.htm
View File

@ -36,16 +36,23 @@ Need to get in touch with someone? Look here.
<h2>Computing</h2>
This is a scientific expedition - the Austrian government allows us to wander around the plateau in exchange for cave surveys. Learn how to contribute!
<ul>
<li><a href="essentials.html">Cave locations</a> - How to download locations of known caves.</li>
<li><a href="gpxupload.html">Phone GPS</a> - How to upload location of the cave you've found.</li>
<li><a href="computing/ftpusage.html">Basic FTP setup</a> - Instructions for Windows, Android and Linux on <strong>how to upload files (and photos)</strong> to expo server.</li>
<li><a href="uploading.html">Uploading photos</a> - More detailed description on photos management.</li>
<li><a href="computing/repousage.html">Basic repositories setup</a> - Instructions for Windows and Linux on repository setup.</li>
<li><a href="getsurvex.html">Getting software</a> - How to get and set-up survey creation software.</li>
<li><a href="survey/newcave.html">Recording newly found caves</a> - What and how to record. (important!)</li>
<li><a href="logbooks.html">Logbook</a> - Adding trip notes and cave descriptions.</li>
<li><a href="datamgt.html">Cave data management</a> - General guidelines about keeping records.</li>
<li><a href="getsurvex.html">Getting Survex</a> - How to set-up centerline preview software.</li>
<li><a href="uploading.html">Uploading photos</a> - How to add visuals to your trips.</li>
<li><a href="exposerver.html">Expo Server</a> - Master archive of expo data and webpage.</li>
<li><a href="nerd.html">Experienced computing setup</a> - Surveying, data management, version control etc.</li>
<li><a href="update.htm">Gandalf-grade computing info</a> - Online Systems and Data: Catalog structure, access and update.</li>
<li><a href="onlinesystems.html">Expo online systems</a> - Overview of expo server capabilites.</li>
<i>Broken:
<li><a href="essentials.html">Cave locations</a> - How to download locations of known caves.</li>
<li><a href="gpxupload.html">Phone GPS</a> - How to upload location of the cave you've found.</li>
</i>
<br>
<li><a href="survey/status.html">Trip report status</a> - Missing .svx's, missing tunnel drawings etc.</li>
</ul>
@ -54,6 +61,9 @@ This is a scientific expedition - the Austrian government allows us to wander ar
<h2>Topcamp info</h2>
Things that are likely to be relevant at topcamp.
<ul>
<li><a href="1staid.html">FIRST AID</a> - What is kept at top camp</li>
<li><a href="druginfo.html">Painkillers etc.</a> - simple drugs on expo</li>
<li><a href="rig/rigit.html">SRT Rigging</a> - How to bolt and rig caves on expo.</li>
<li><a href="charging.html">Drill battery charging</a> - How to charge drill batts. (important! you could break them)</li>
<li><a href="look4.htm">Prospecting - first steps</a> - How to check out a possible entrance safely.</li>
<li><a href="/prospecting_guide/">Prospecting guide</a> - Maps of known entrances and potential locations of interest.</li>
@ -63,10 +73,6 @@ Things that are likely to be relevant at topcamp.
<li><a href="solar.html">Solar Panels</a> - Set-up and put-away info.</li>
<li><a href="bivirig.html">Bivi Rigging</a> - Bivvi rigging guide for topcamp.</li>
<li><a href="photo.htm">Cave photography</a> - Very brief photograpy handbook.</li>
<li><a href="rigit.htm">SRT Rigging</a> - How to rig caves on expo.</li>
<li><a href="rig/intro.htm">SRT Rigging - Introduction</a> - Jump to: Introduction.</li>
<li><a href="rig/boltin.htm">Placing bolts</a> - Guide to putting bolts.</li>
<li><a href="1staid.html">First Aid</a> - Guide to First Aid.</li>
</ul>
<hr>
@ -91,28 +97,29 @@ Things that are likely to be relevant at basecamp.
<h2>Misc</h2>
<ul>
<li><a href="datamgt.html">Cave data management</a> - Paragraph long corporate philosophy blurb.</li>
<li><a href="vocab.htm">Travelling cavers phrases</a> - Vocabulary in (German, Spanish, French).</li>
<li><a href="planning.html">Expo Planning Guide</a> - How to plan and orgnise expo.</li>
<li><a href="leader.htm">Expo leader checklist</a> - For leaders: check these before you leave UK.</li>
<li><a href="treasurer.html">Expo treasurer's guide</a> - For treasurers: tasks, tips.</li>
</ul>
<hr>
<hr />
<div id="menu">
<ul id="links">
<li><a href="index.htm">Expedition Handbook</a>
<ul>
<li><a href="rig/rigit.html">Rigging guide</a></li>
<li><a href="survey/index.htm">Surveying guide</a></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</a></li>
<li><a href="../index.htm">Back to Expedition Intro</a></li>
<li><a href="../../index.htm">Back to CUCC Home</a></li>
<li><a href="../infodx.htm">Main index</a></li>
<li><a href="../index.htm">Expo Home</a></li>
<li><a href="../../index.htm">CUCC Home</a></li>
</ul>
</div>
</body>
</html>

30
handbook/l/bosch.htm → handbook/l/bosch.html
View File

@ -1,4 +1,3 @@
<!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" />
@ -24,26 +23,29 @@ rebelays are needed, and especially on bolted climbs or traverses such as "<a
href="../../1623/161/l/3wisea.htm">Three Wise Men</a>". The drill was in
such demand for this type of rigging that a second one was bought (and a third
may be borrowed...), and a number of members of the club have invested in
drills for their own use.</p>
drills for their own use [1990].</p>
<p class="caption">Photo &copy; Andy Atkinson, 1990</p>
<!-- Photo scanned on Coolscan 600x600 at 675 dpi, 1997.08.09 , AERW -->
<!-- It's a bloody awful photo. I'd better take a decent one this summer.
DL 2004/04/22. -->
<hr style="clear: both" />
<hr />
<div id="menu">
<ul id="links">
<li><a href="../index.htm">Expedition Handbook</a> - Intro
<li><a href="../index.htm">Expedition Handbook</a>
<ul>
<li><a href="../rigit.htm">Rigging guide (old page)</a></li>
<li><a href="../rig/index.htm">New Rigging Guide</a>:
<ul>
<li><a href="../rig/boltin.htm">Placing bolts</a></li>
</ul></li>
<li><a href="../rig/rigit.html">Rigging guide</a></li>
<li><a href="../survey/index.htm">Surveying guide</a></li>
<li><a href="../look4.htm">Prospecting guide</a></li>
<li><a href="../rescue.htm">Rescue guide</a></li>
<li><a href="../photo.htm">Photography guide</a></li>
</ul></li>
<li>Cambridge Underground 1991 <a href="../../years/1990/drill.htm">Drill
Report</a></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="../../infodx.htm">Main index</a></li>
<li><a href="../../index.htm">Expo Home</a></li>
<li><a href="../../../index.htm">CUCC Home</a></li>
</ul>
</div>
</body>
</html>
</html>

36
handbook/l/rbelay.htm → handbook/l/rbelay.html
View File

@ -1,4 +1,3 @@
<!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" />
@ -6,31 +5,42 @@
<link rel="stylesheet" type="text/css" href="../../css/main2.css" />
</head>
<body>
<div class="onleft"><img src="../i/rbelay.jpg" width="300" height="600" alt="Approaching a rebelay" /></div>
<h2 id="tophead">CUCC Expo Rigging Handbook</h2>
<h1>Approaching a typical rebelay</h1>
<div class="onleft"><img src="../i/rbelay.jpg" width="300" height="600" alt="Approaching a rebelay" /></div>
<!-- Photo scanned on Coolscan 450x900 at 675 dpi, 1997.08.08 , AERW -->
<p>Tina White approaching a typical rebelay from below in Kaninchenh&ouml;hle.
Note that there is little slack in the rope above the rebelay, though there
is no doubt that a lot will appear once the rope is loaded. This is something
Note that there is too little slack in the rope above the rebelay, though there
is no doubt that a lot will appear once the rope is loaded.
<p>This is something
to watch out for on the descent: when the slack disappears as the upper rope
is unloaded, it is possible to find that you can't remove your descender from
the rope without attaching an ascender to re-load it.</p>
<p>This is an mild example of an unnecesarily acrobatic rig which should be re-done on any route with heavy traffic.
<p class="caption">Photo &copy; Mark Dougherty, 199x</p>
<!-- Photo scanned on Coolscan 450x900 at 675 dpi, 1997.08.08 , AERW -->
<p>This photo is to illustrate the (as yet unwritten) Expo Rigging Guide.</p>
<hr style="clear: both" />
<hr />
<div id="menu">
<ul id="links">
<li><a href="../index.htm">Expedition Handbook</a> - Intro
<li><a href="../index.htm">Expedition Handbook</a>
<ul>
<li><a href="../rigit.htm">Rigging guide</a></li>
<li><a href="../rig/rigit.html">Rigging guide</a></li>
<li><a href="../survey/index.htm">Surveying guide</a></li>
<li><a href="../look4.htm">Prospecting guide</a></li>
<li><a href="../rescue.htm">Rescue guide</a></li>
<li><a href="../photo.htm">Photography guide</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="../../infodx.htm">Main index</a></li>
<li><a href="../../index.htm">Expo Home</a></li>
<li><a href="../../../index.htm">CUCC Home</a></li>
</ul>
</div>
</body>
</html>
</html>

0
handbook/l/rltyrl.htm → handbook/l/rltyrl.html
View File

2
handbook/leader.htm
View File

@ -308,7 +308,7 @@ the Austrian Cavers to get new kataster numbers.</li>
<li><a href="survey/index.htm">Surveying guide</a> &ndash; Overview</li>
<li><a href="look4.htm">Prospecting guide</a> &ndash; Overview</li>
<li><a href="rescue.htm">Rescue guide</a></li>
<li><a href="rigit.htm">Rigging guide</a></li>
<li><a href="rigit.html">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>

2
handbook/logbooks.html
View File

@ -69,7 +69,7 @@ copy it by email or USB stick to another laptop, edit it there and then copy it
<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.
<li><a href="onlinesystems.html#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>

2
handbook/look4.htm
View File

@ -221,7 +221,7 @@ net pages) to other groups with a bona fide need.</p>
<ul>
<li><a href="survey/index.htm">Surveying guide</a> - Overview
<li><a href="rescue.htm">Rescue guide</a></li>
<li><a href="rigit.htm">Rigging guide</a></li>
<li><a href="rigit.html">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>

7
handbook/manual.html
View File

@ -18,7 +18,7 @@ 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.
<p>Note that to display the survey data you will need a copy of the <a href="getsurvex.html">survex</a> software.
<h3>Contents</h3>
@ -41,7 +41,7 @@ processes that a maintainer would want to do.</p>
</ol>
Appendices:
<ul>
<li><a href="data management system-history.html">History of the data management system</a></li>
<li><a href="c21bs.html">Taking Expo Bullshit into the 21st Century</a> - a history of the data management system up to 1996</li>
</ul>
<h3><a id="usernamepassword">Getting a username and password</a></h3>
@ -62,7 +62,7 @@ expo.survex.com. This is currently hosted on a server at the university. We use
<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/troggle/graph/">troggle</a> - the database-driven part of the data management system - see <a href="troggle-ish.html">notes on troggle</a> for further explanation</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>
@ -301,6 +301,7 @@ http://expo.survex.com/expo/surveys/surveytable.html http://expo.survex.com/surv
<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.
<p>A history of the expo website and software was published in Cambridge Underground 1996. A copy of this article <a href="c21bs.html">Taking Expo Bullshit into the 21st Century</a> is archived here.
<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>

14
handbook/nerd.html
View File

@ -6,23 +6,27 @@
</head>
<body>
<h2 id="tophead">CUCC Expedition Handbook</h2>
<h1>Placeholder</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 />
<div id="menu">
<ul id="links">
<li><a href="index.htm">Expedition Handbook</a>
<ul>
<li><a href="survey/index.htm">Surveying guide</a> - Overview</li>
<li><a href="look4.htm">Prospecting guide</a> &ndash; Overview</li>
<li><a href="rig/rigit.html">Rigging guide</a></li>
<li><a href="survey/index.htm">Surveying guide</a></li>
<li><a href="look4.htm">Prospecting guide</a></li>
<li><a href="rescue.htm">Rescue guide</a></li>
</ul></li>
<li><a href="../infodx.htm">Main index</a></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">Expo Home</a></li>
<li><a href="../../index.htm">CUCC Home</a></li>
</ul>
</div>
</body>
</html>

147
handbook/onlinesystems.html Normal file
View File

@ -0,0 +1,147 @@
<html>
<head>
<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 - Online systems</h2>
<h1>Expo Online Systems Overview</h1>
<p>The online data and web publishing system (i.e. "the website") 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.
<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.
<p>These pages listed below have been reviewed recently (2018), and a
fuller list of "How do I..." instruction pages are on <a href="index.htm">the handbook opening page</a>.
<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="survey/newcave.html">Recording a new cave discovery</a></li>
<li><a href="survey/status.html">Monitoring the status cave survey workflow during and after expo</a></li>
</ul>
<p>But the systems Manual is still being actively edited to extract and simplify documentation. At the moment
it is the only documentation we have for:
<ul>
<li><a href="manual.html#update">Manual: Creating a new 'year' in the system</a></li>
<li><a href="manual.html#update">Manual: Updating the cave guidebook descriptions</a></li>
<li><a href="manual.html#manual">Manual: Expo software and server maintenance manual</a></li>
</ul>
<h2><a id="update">Updating the online systems - overview</a></h2>
<h3>Experts short cut</h3>
<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>
<h3>Autogenerated pages</h3>
<p>Some key sections of the online webpages are autogenerated by scripts or 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="edithandbook">Editing this handbook and historic expo documentation</h3>
<p>The primary and recommended way of editing this handbook (and the website generally) is to use
a laptop which has the <a href="#mercurial">Distributed Version Control System</a> software installed. The
person editing needs to know how to use this software, and also needs to know how to edit raw HTML files
using a text editor.
<p>The <em>Expo laptop</em> has the software installed, so it is best to learn how to do this
when sitting at that laptop.
<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>The recommended editing workflow is to (a) use the DVCM to synchronise your local laptop copy of the
website files with that on the server; (b) edit a set of .html files on your laptop so that all links between them are consistent,
save the files locally, and "commit" them locally;
(c) "push" the collection of changes to the expo online server as a single action.
<p>See the <a href="manual.html#manual">Expo data management systems manual</a> for a fuller description of the DVCM
repositories and how to install and use the software.
<h3 id="editthispage">Using "Edit this page"</h3>
<p>You can update a single webpage
online via a browser. This is best used for urgent edits to a single page, e.g.
if the emergency phone at top-camp has to use a new SIM with a different phone number.
If you are a logged-on user you will see "Edit this page" on the menu on the left of this page. It appears on
nearly all pages in this website. If you click on it you will be able to edit the raw HTML of the page - so you need
to know how to do that.
<p>After doing the page editing and saving your work, 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 id="mercurial">DVCS - version control</a></h3>
<p>We use a distributed revision control system (DVCS) for all the important data.
This means that many people can edit and merge their changes with the expo
server in Cambridge at the same time: inlcuding people still on expo in the Tatty Hut
and those who have returned to the UK. Also anyone who is up
to date can take their laptop somewhere and enter data even if they have no internet access,
and the updates will be merged when they get back to civilization.
</p>
<p>In principle, survey notes can be typed into a laptop up on the plateau which would
then get synchronised when it next gets internet access.
</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>
<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 publish it on the web.
<p>Only a small part of troggle's original plan was fully implemented and deployed.
Many of the things it was intended to replace are still operating as a motley collection written by many different people in
several languages (but mostly perl and python; we won't talk about the person who likes to use OCamL).
Today troggle is used for only three things:
<ol>
<li>Reformatting all the visible webpages such that they have a coherent style and have a contents list at the top-left
hand corner. This is particularly true of the handbook you are reading now and the historic records of past expeditions.
<li>Publishing the "guidebook descriptions" of caves. The user who is creating a new guidebook description
can do this by filling-in some online forms.
<li>Providing a secondary way of editing individual pages of the handbook and historic records pages
for very quick and urgent changes.
This is the "Edit this page" capability; see <a href="#editthispage">above for
how to use it</a> and how to tidy up afterwards.
</ol>
<p>See the <a href="troggle-ish.html">notes on troggle</a> page
for how and why it was developed and what needs to be done.
<hr />
</body>
</html>

93
handbook/rig/boltin.htm → handbook/rig/boltin.html
View File

@ -7,7 +7,7 @@
</head>
<body>
<h2 id="tophead"> CUCC Expo Rigging Handbook</h2>
<h1>Bolt belays - placing</h1>
<h1>Bolt belays - Hand-drilling and placing spits</h1>
<p>Once you've decided where to put your bolt, you have to actually physically
place and set it. The methods used differ substantially depending on whether
@ -15,11 +15,13 @@ you are using hand bolts (spits) or Hilti HKDS's.</p>
<p>Before you actually start drilling, it is wise to flatten the surface of the
rock around the bolt site. This allows the hanger to lie flat against the rock.
<p>
Different types of hanger have different footprints; bollards have almost no
footprint at all, rings and bends somewhat more, and twists a great deal.
Remember, of course, that the next person who rigs the pitch may well use a
different type of hanger from the one you happen to have handy, and that the
club only has about ten bollards left! When dressing the rock, use the pointed
different type of hanger from the one you happen to have handy.
<p>
When dressing the rock, use the pointed
end of the hammer and tap gently, so as not to crack the rock below the
surface.</p>
@ -27,8 +29,8 @@ surface.</p>
<div class="onleft" style="clear: left"> <a
href="../../1623/161/l/boltin.htm"><img alt="(36k image)"
src="../../1623/161/t/boltin.jpg" width="113" height="152" /></a> <p
class="caption">Bolting by Hand</p> </div>
src="../../1623/161/t/boltin.jpg" width="113" height="152" /></a></br><span
class="caption">Bolting by Hand</br>(click to enlarge)</span> </div>
<p>Old-style hand-drilled spits are self-drilling; the spit sleeve functions
both as a drill bit and as an anchor. Screw it firmly onto the driver and tap
it gently against the surface of the rock, turning it around slightly between
@ -70,84 +72,23 @@ hanger, and Bob's your uncle.</p>
<h2>Power-drills and Hilti anchors</h2>
<div class="onleft"><a href="../l/bosch.htm"><img
alt="(73k image)" src="../t/bosch.jpg" width="200" height="200" /></a><p
class="caption">Using the Drill</p></div>
<p>Since the first cordless hammer drills made an appearance on Expo 1990
thanks to sponsorship from Bosch, drills have been enthusiastically adopted as
the best solution for large-scale bolting tasks; some of the fun and games of
recent years, like the 21-bolt traverse over Gaffered to the Walls in 2003,
would be unthinkable with hand bolts. However, drills are not suited to use
with ordinary spits, as the setting process depends critically on the bottom of
the hole being flat. It is possible to drill a hole part-way with a power drill
and finish it off by hand, but this is tedious.</p>
<p>Hence we have found it easier to use Hilti anchors, which are specifically
designed for use in drilled holes.</p>
<div style="text-align: center">
<a href="../../years/1990/hilti1-300.png"><img
alt="before setting - 1k png" width="530" height="90" style="margin: 10pt"
src="../../years/1990/hilti1-100.png" /></a><br />
<b>Hilti HDK spits before and after setting.</b><br />
<a href="../../years/1990/hilti2-300.png"><img alt="after setting - 1k png"
width="220" height="94"
src="../../years/1990/hilti2-100.png" style="margin: 10pt" /></a></div>
<p>There are two versions of these bolts, the HKD and the HKDS. The latter are
easier to use, as they have a "shoulder" around the top of the bolt which sits
against the rock, meaning that the depth of the hole is not important.</p>
<p>To place a HKDS, drill the hole in the obvious manner until it is deep
enough for the bolt to sit in without touching the bottom. If in doubt, drill
it deep! When the hole is deep enough, grab a setting tool and start bashing it.</p>
<p>Start with very gentle taps. The reason for this is so the shoulder can hold
the bolt in position until it begins to grip the sides of the hole; if you
start by smashing it with all your might, the shoulder will bend and the bolt
will disappear, useless, into the depths of the hole. Once it has some grip you
can start hitting a bit harder.</p>
<p>It is very important to hit the Hilti setting tools exactly square, as they
are made of very hard steel which is rather brittle and hence it is easy to
shear the end off. When the bolt is fully set, you should be able to see marks
on the shoulder of the spit from the four little teeth on the collar of the
driver; don't worry if you can't see all four setting marks, but aim for two at
least - one can easily be a consequence of leaning the driver over too far to
one side.</p>
<p>Sometimes, in particularly hard rock, it can be impossible to get the
setting marks. Use your judgement; if you're not making any progress despite
sustained hammering, it's probably OK to stop!</p>
<hr />
<div id="menu">
<ul id="links">
<li><a href="../index.htm">Expedition Handbook</a> - Contents
<li><a href="../index.htm">Expedition Handbook</a>
<ul>
<li><a href="index.htm">Rigging Guide</a>
<ul>
<li><a href="intro.htm">Introduction</a></li>
<li><a href="boltplace.html">Choosing bolt locations</a></li>
<li>The mechanics of placing a bolt</li>
<li><a href="exporig.html">Expo-specific rigging tricks</a></li>
</ul></li>
<li><a href="../look4.htm">Prospecting guide</a></li>
<li><a href="../rig/rigit.html">Rigging guide</a></li>
<li><a href="../survey/index.htm">Surveying guide</a></li>
<li><a href="../look4.htm">Prospecting guide</a></li>
<li><a href="../rescue.htm">Rescue 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="../../infodx.htm">Main index</a></li>
<li><a href="../../index.htm">Expo Home</a></li>
<li><a href="../../../index.htm">CUCC Home</a></li>
</ul>
</div>
</body>
</html>

Some files were not shown because too many files have changed in this diff Show More