expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2025-01-18 00:42:38 +00:00
Code Issues Packages Projects Releases Wiki Activity

add/correct links to newer 264 surveys

Browse Source
This commit is contained in:
expo 2016-06-16 23:21:55 +01:00
parent 51ccfc16cd
commit 3fe1b659ec
1 changed files with 7 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
noinfo/cave_data/1623-264.html
View File

@ -1,6 +1,6 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
<!-- Only put one cave in this file -->
<!-- If you edit this file, make sure you update the website database -->
<!-- If you edit this file, make sure you update the websites database -->
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
@ -13,7 +13,7 @@
<area>1623</area>
<area>2d</area>
<kataster_code>1/S =</kataster_code>
<kataster_number>264</kataster_number>
<kataster_number>264</kataster_number>
<unofficial_number>2005-05</unofficial_number>
<entrance>
@ -22,13 +22,14 @@
</entrance>
<explorers>Entrance noted CUCC 2002 (Duncan). Refound + partially explored CUCC 2005 (Peter + Phil). Explored to ~3km in 2014.</explorers>
<underground_description><a href="../../1623/264/ent.html">ent</a>
<underground_description><a href="../../1623/264/ent.html">ent</a>
</underground_description>
<equipment>5m handline and ~120m for entrance shaft</equipment>
<references>Brief description and sketch in 2002#31; <a href="../../years/2005/logbook.html#t2005-08-10A">2005 log book</a>.</references>
<survey> <a href="/expofiles/surveys/264/2015/area-plan-elv.png">Survey 2015</a>
</survey>
<survey><a href="/expofiles/surveys/264/2015/area-plan-elv.png">Survey 2015</a>
<a href="http://expo/expofiles/surveys/264/balconyhohle.png>Balcony survey</a>(2MB)</survey>
<kataster_status></kataster_status>
<underground_centre_line></underground_centre_line>
<notes>The original ID 2005-05 was also used (briefly) for another entrance, which was found the next day to connect to 204, and designated as 204G. The number was reused due to an acute tag shortage.</notes>