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

Banana cave Boop-Da-Boop

Browse Source
This commit is contained in:
Philip Sargent 2023-10-16 13:38:54 +03:00
parent 94cd283175
commit 0657e16959
6 changed files with 259 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

64
cave_data/1626-2019-HT-01.html Normal file
View File

@ -0,0 +1,64 @@
<!DOCTYPE html>
<!-- This file is generated by troggle on Oct. 16, 2023, 11:33 a.m. UTC using the form documented at /handbook/survey/caveentry.html -->
<!-- Only put one cave in this file -->
<!-- If you edit this 1623-nnn.html file by hand, and manually upload it to the server using git,
make sure you update the database by doing a full data import. If you edit it using the online form
though, you do not need to do a data import as it happens automatically -->
<!-- ALTERNATIVELY you can download an example template from expoweb/templates/cave_data.html -->
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
</head>
<body>
<b>This file is generated by troggle</b> on Oct. 16, 2023, 11:33 a.m. UTC using the form documented at
the form documented at
<a href="/handbook/survey/caveentry.html">handbook/survey/caveentry.html</a>
<br>
<cave>
<non_public>False</non_public><!-- 'False' or 'True'. True if the cave should only be visible to logged-in users. Caves are normally public, so enter 'False' unless you know otherwise. -->
<caveslug>1626-2019-HT-01</caveslug><!--(Required). Internal I.D. used to refer to this cave in entrance data files. Typically the same as the filebase, e.g. '1623-195' -->
<official_name>The Banana Hole</official_name><!-- Name of the cave (normally in German) Use &uuml; for u+Umlaut and &ouml; for o+umlaut eg H&ouml;hle for Hohle and Gl&uuml;ck for Gluck-->
<area>1626</area><!-- e.g. "1623" -->
<kataster_code></kataster_code><!-- 'length-or-depth/type exploration'
code used in the Austrian kataster e.g '1/S +' - https://expo/.survex.com/katast.htm
T Trockenh&ouml;hlen (Dry caves)
W Wasserh&ouml;hlen (Caves with water)
(W) Zeitweilig aktiv Wasserh&ouml;hlen (Caves with seasonal water)
E Eishohlen (Caves with ice formations)
S Schachth&ouml;hlen (Caves with pitches)
H Halbh&ouml;hlen (Rock shelters ?)
- unerforscht (unexplored)
= befahren (visited)
× teilweise vermessen (partly surveyed)
+ erforscht (exploration considered complete)
-->
<kataster_number></kataster_number> <!-- (Either this or unofficial_number is required). Official number in Austrian kataster if one has been allocated -->
<unofficial_number>2019-HT-01</unofficial_number><!-- (Either this or kataster_number is required). Initial temporary cave ID used until kataster number is allocated e.g. '2012-DD-01'-->
<entrance>
<entranceslug>1626-2019-HT-01</entranceslug><!-- Internal ID to refer to each entrance instance in the entrance files (typically the same as that filename (e.g. 1623-161c). Matches the 'slug' field in the entrance file -->
<!-- DEBUG 1626-2019-HT-01+1626-2019-HT-01 'Z' == -->
<letter></letter><!--Leave blank for single-entrance cave. If there is more than one entrace then the letter needs to be given. Generally matches the entranceslug ID. -->
</entrance>
<explorers></explorers><!-- 'CUCC Expo' and year(s) of exploration. To distinguish from caves explored by foreign groups. Individual names can be given too if it was a small cave. -->
<survex_file></survex_file><!-- Name of top-level survey file for this cave. Relative to the 'loser' survex repository. So for most caves that's "caves-162x/cavenum/cavnum.svx". (e.g. caves-1623/204/204.svx -->
<underground_description>a deep pit in a large expanse of sloping limestone pavement up a hill. <p>The bottom is beyond what can be seen with a caving light in day time, but dropping rocks gives roughly 4 seconds of free fall, before ricocheting further down and unknown amount.</underground_description><!-- Underground description. (description of approach and entrance goes in entrance file). For a small cave this will be the entire description. For larger caves it will be the front page of the description, or a short intro, containing links to other pages with the cave description in, or even nothing but a link. -->
<equipment></equipment><!-- For a small cave, summary of gear needed to descend. For longer caves it could be blank, a table, or just refer to the description/topos. Leave blank if this info is in the description. -->
<references>Logbook <a href="/logbookentry/2019-07-20/2019-07-20a">2019-07-20a</a></references><!-- References to documentation. Could be Journal articles or Logbook entries. Can be links if the docs are online. -->
<survey></survey><!-- Drawn-up surveys. Scans of paper surveys or images/PDFs of electronic surveys. Should include HTML to display current plan and elevation, with links to larger versions (See section on URLs and files). Could list links to multiple years of survey, or even a separate survey page if it's complicated enough. -->
<kataster_status></kataster_status>
<underground_centre_line></underground_centre_line><!-- 'In dataset' if it is in the survex dataset. Blank if not, or notes about status such as 'surveyed, but no entrance fix so not yet in dataset'. -->
<notes></notes><!-- Normally empty, but place for anything else that should be noted, such as info on cave maybe being a duplicate, or lost -->
<length></length><!-- Cave length. Can be left blank and system should fill it in automatically from survey data (it doesn't yet) -->
<depth></depth><!--Cave depth. Can be left blank and system should fill it in automatically from survey data (it doesn't yet) -->
<extent></extent>
<description_file></description_file><!-- Path of top-level description file for this cave, when a separate file is used. Otherwise blank. -->
<url>1626/2019-HT-01.html</url><!-- (Required). Relative URL of this cave. i.e the URL this cave appears at on the website, not including 'https://expo.survex.com/. Normally area/cavenum., e.g ('1623/000')-->
</cave>
</body>
</html>

64
cave_data/1626-2019-HT-02.html Normal file
View File

@ -0,0 +1,64 @@
<!DOCTYPE html>
<!-- This file is generated by troggle on Oct. 16, 2023, 11:34 a.m. UTC using the form documented at /handbook/survey/caveentry.html -->
<!-- Only put one cave in this file -->
<!-- If you edit this 1623-nnn.html file by hand, and manually upload it to the server using git,
make sure you update the database by doing a full data import. If you edit it using the online form
though, you do not need to do a data import as it happens automatically -->
<!-- ALTERNATIVELY you can download an example template from expoweb/templates/cave_data.html -->
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
</head>
<body>
<b>This file is generated by troggle</b> on Oct. 16, 2023, 11:34 a.m. UTC using the form documented at
the form documented at
<a href="/handbook/survey/caveentry.html">handbook/survey/caveentry.html</a>
<br>
<cave>
<non_public>False</non_public><!-- 'False' or 'True'. True if the cave should only be visible to logged-in users. Caves are normally public, so enter 'False' unless you know otherwise. -->
<caveslug>1626-2019-HT-02</caveslug><!--(Required). Internal I.D. used to refer to this cave in entrance data files. Typically the same as the filebase, e.g. '1623-195' -->
<official_name>Boop-Boo-Da-Boop-Da-Boop</official_name><!-- Name of the cave (normally in German) Use &uuml; for u+Umlaut and &ouml; for o+umlaut eg H&ouml;hle for Hohle and Gl&uuml;ck for Gluck-->
<area>1626</area><!-- e.g. "1623" -->
<kataster_code></kataster_code><!-- 'length-or-depth/type exploration'
code used in the Austrian kataster e.g '1/S +' - https://expo/.survex.com/katast.htm
T Trockenh&ouml;hlen (Dry caves)
W Wasserh&ouml;hlen (Caves with water)
(W) Zeitweilig aktiv Wasserh&ouml;hlen (Caves with seasonal water)
E Eishohlen (Caves with ice formations)
S Schachth&ouml;hlen (Caves with pitches)
H Halbh&ouml;hlen (Rock shelters ?)
- unerforscht (unexplored)
= befahren (visited)
× teilweise vermessen (partly surveyed)
+ erforscht (exploration considered complete)
-->
<kataster_number></kataster_number> <!-- (Either this or unofficial_number is required). Official number in Austrian kataster if one has been allocated -->
<unofficial_number>2019-HT-02</unofficial_number><!-- (Either this or kataster_number is required). Initial temporary cave ID used until kataster number is allocated e.g. '2012-DD-01'-->
<entrance>
<entranceslug>1626-2019-HT-02</entranceslug><!-- Internal ID to refer to each entrance instance in the entrance files (typically the same as that filename (e.g. 1623-161c). Matches the 'slug' field in the entrance file -->
<!-- DEBUG 1626-2019-HT-02+1626-2019-HT-02 'Z' == -->
<letter></letter><!--Leave blank for single-entrance cave. If there is more than one entrace then the letter needs to be given. Generally matches the entranceslug ID. -->
</entrance>
<explorers></explorers><!-- 'CUCC Expo' and year(s) of exploration. To distinguish from caves explored by foreign groups. Individual names can be given too if it was a small cave. -->
<survex_file></survex_file><!-- Name of top-level survey file for this cave. Relative to the 'loser' survex repository. So for most caves that's "caves-162x/cavenum/cavnum.svx". (e.g. caves-1623/204/204.svx -->
<underground_description>The Boop-Boo-Da-Boop-Da-Boop [exact spelling pending confirmation] [2019-HT-02] complex is an area of multiple very large holes surrounding a small flat expanse of karst, half surrounded by cliffs. <p>Two of the entrances are extremely appealing, with one a few meters wide and unknown depth (again, the rocks take long to go down, a disto would've been helpful), and another similarly wide and quite deep and clearly going diagonally into the hillside, reducing likelihood of being choked.</underground_description><!-- Underground description. (description of approach and entrance goes in entrance file). For a small cave this will be the entire description. For larger caves it will be the front page of the description, or a short intro, containing links to other pages with the cave description in, or even nothing but a link. -->
<equipment></equipment><!-- For a small cave, summary of gear needed to descend. For longer caves it could be blank, a table, or just refer to the description/topos. Leave blank if this info is in the description. -->
<references>Logbook <a href="/logbookentry/2019-07-20/2019-07-20a">2019-07-20a</a></references><!-- References to documentation. Could be Journal articles or Logbook entries. Can be links if the docs are online. -->
<survey></survey><!-- Drawn-up surveys. Scans of paper surveys or images/PDFs of electronic surveys. Should include HTML to display current plan and elevation, with links to larger versions (See section on URLs and files). Could list links to multiple years of survey, or even a separate survey page if it's complicated enough. -->
<kataster_status></kataster_status>
<underground_centre_line></underground_centre_line><!-- 'In dataset' if it is in the survex dataset. Blank if not, or notes about status such as 'surveyed, but no entrance fix so not yet in dataset'. -->
<notes></notes><!-- Normally empty, but place for anything else that should be noted, such as info on cave maybe being a duplicate, or lost -->
<length></length><!-- Cave length. Can be left blank and system should fill it in automatically from survey data (it doesn't yet) -->
<depth></depth><!--Cave depth. Can be left blank and system should fill it in automatically from survey data (it doesn't yet) -->
<extent></extent>
<description_file></description_file><!-- Path of top-level description file for this cave, when a separate file is used. Otherwise blank. -->
<url>1626/2019-HT-02.html</url><!-- (Required). Relative URL of this cave. i.e the URL this cave appears at on the website, not including 'https://expo.survex.com/. Normally area/cavenum., e.g ('1623/000')-->
</cave>
</body>
</html>

8
cave_data/pendingcaves.txt
View File

@ -1,2 +1,6 @@
1626-Boop-Boo-Da-Boop ; IDs listed here will have a Cave object created in troggle,
1626-Banana ; and the Cave Description will be pre-filled with instructions of how
; to find and update the information needed to do it properly.
; example (without the initial semicolon of course):
;1626-2019-HT-01 ; Banana

59
entrance_data/1626-2019-HT-01.html Normal file
View File

@ -0,0 +1,59 @@
<!DOCTYPE html>
<!-- Only put one entrance in this file -->
<!-- This file is generated by troggle on Oct. 16, 2023, 11:33 a.m. UTC using the form documented at handbook/survey/ententry.html -->
<!-- If you edit this file by hand, and manually upload it to the server using git,
make sure you update the database by doing a full data import. If you edit it using the online form
though, you do not need to do a data import as it happens automatically -->
<!-- See http://expo.survex.com/handbook/survey/caveentryfields.html for current details on filling in this form -->
<!-- there is 1 required field: slug. The entrance will not appear without that. -->
<!-- ALWAYS use &uuml; for u+Umlaut and &ouml; for o+umlaut eg H&ouml;hle for Hohle and Gl&uuml;ck for Gluck-->
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
</head>
<body>
<b>This file is generated by troggle</b> on Oct. 16, 2023, 11:33 a.m. UTC using the form documented at
<a href="/handbook/survey/ententry.html">handbook/survey/ententry.html</a>
<br>
<entrance>
<non_public>False</non_public>
<slug>1626-2019-HT-01</slug> <!-- one entrance and one slug per entrance_data file -->
<name></name>
<entrance_description></entrance_description>
<explorers></explorers>
<map_description></map_description>
<location_description></location_description>
<lastvisit></lastvisit>
<approach></approach>
<underground_description></underground_description>
<photo></photo>
<!-- marking options: P = Paint,
P? = Paint (?),
T = Tag,
T? = Tag (?),
R = Retagged,
S = Spit,
S? = Spit (?),
U = Unmarked,
? = Unknown" -->
<marking>U</marking>
<marking_comment></marking_comment>
<!-- findability options: ? = To be confirmed ...,
S = Surveyed,
L = Lost,
R = Refindable" -->
<findability>L</findability>
<findability_description>On Jon's GPS tracklog, which we don't have</findability_description>
<alt></alt>
<lat_wgs84></lat_wgs84>
<long_wgs84></long_wgs84>
<tag_station></tag_station>
<other_station></other_station>
<other_description></other_description>
<bearings></bearings>
<url></url>
</entrance>
</body>
</html>

59
entrance_data/1626-2019-HT-02.html Normal file
View File

@ -0,0 +1,59 @@
<!DOCTYPE html>
<!-- Only put one entrance in this file -->
<!-- This file is generated by troggle on Oct. 16, 2023, 11:34 a.m. UTC using the form documented at handbook/survey/ententry.html -->
<!-- If you edit this file by hand, and manually upload it to the server using git,
make sure you update the database by doing a full data import. If you edit it using the online form
though, you do not need to do a data import as it happens automatically -->
<!-- See http://expo.survex.com/handbook/survey/caveentryfields.html for current details on filling in this form -->
<!-- there is 1 required field: slug. The entrance will not appear without that. -->
<!-- ALWAYS use &uuml; for u+Umlaut and &ouml; for o+umlaut eg H&ouml;hle for Hohle and Gl&uuml;ck for Gluck-->
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
</head>
<body>
<b>This file is generated by troggle</b> on Oct. 16, 2023, 11:34 a.m. UTC using the form documented at
<a href="/handbook/survey/ententry.html">handbook/survey/ententry.html</a>
<br>
<entrance>
<non_public>False</non_public>
<slug>1626-2019-HT-02</slug> <!-- one entrance and one slug per entrance_data file -->
<name></name>
<entrance_description></entrance_description>
<explorers></explorers>
<map_description></map_description>
<location_description></location_description>
<lastvisit></lastvisit>
<approach></approach>
<underground_description></underground_description>
<photo></photo>
<!-- marking options: P = Paint,
P? = Paint (?),
T = Tag,
T? = Tag (?),
R = Retagged,
S = Spit,
S? = Spit (?),
U = Unmarked,
? = Unknown" -->
<marking>U</marking>
<marking_comment></marking_comment>
<!-- findability options: ? = To be confirmed ...,
S = Surveyed,
L = Lost,
R = Refindable" -->
<findability>L</findability>
<findability_description>On JOn's GPS 2019 tracklog, which we don't have</findability_description>
<alt></alt>
<lat_wgs84></lat_wgs84>
<long_wgs84></long_wgs84>
<tag_station></tag_station>
<other_station></other_station>
<other_description></other_description>
<bearings></bearings>
<url></url>
</entrance>
</body>
</html>

17
years/2019/logbook.html
View File

@ -14,7 +14,7 @@ maintain half a dozen parser functions.
Sorry about all the crap that surrounds the image tags which has been imported along with the content Sorry about all the crap that surrounds the image tags which has been imported along with the content
when UK Caving blogs have been parsed. when UK Caving blogs have been parsed.
Exported on 2023-10-05 08:10 using either the control panel webpage or when editing a logbook entry online Exported on 2023-10-16 11:10 using either the control panel webpage or when editing a logbook entry online
See troggle/code/views/other.py and core.models/logbooks.py writelogbook(year, filename) See troggle/code/views/other.py and core.models/logbooks.py writelogbook(year, filename)
--> -->
<body> <body>
@ -253,7 +253,6 @@ That's all for now,<br />
<br /> <br />
Tom Crossley (11/07/2019)</div> Tom Crossley (11/07/2019)</div>
</div> </div>
</div> </div>
@ -405,7 +404,6 @@ Me and Michael H also found a pretty snake guarding a cave entrance:<br />
<br /> <br />
The weather is due to improve after the weekend, and pushing trips are planned into Homecoming, Balcony, and into Happy Butterfly which hasn't been touched since 2017. Happy Butterfly is likely to connect with Fish Face and allow us to bypass the new snowplug, and reclaim what was lost.</div> The weather is due to improve after the weekend, and pushing trips are planned into Homecoming, Balcony, and into Happy Butterfly which hasn't been touched since 2017. Happy Butterfly is likely to connect with Fish Face and allow us to bypass the new snowplug, and reclaim what was lost.</div>
</div> </div>
</div> </div>
@ -439,7 +437,6 @@ Callout 23:00 @ basecamp
<br /><br /><!-- blog post --> <br /><br /><!-- blog post -->
As Crossley stated [in previous UK Caving blog post], he, Dickon, and I rigged to the pushing front of Heimkommen on July 10th. <br /><br /> As Crossley stated [in previous UK Caving blog post], he, Dickon, and I rigged to the pushing front of Heimkommen on July 10th. <br /><br />
<div class="bbImageWrapper js-lbImage" title="dickon-rigging-homecoming.jpg" data-src="http://expo.survex.com/expofiles/photos/2019/BlogPostPhotos/dickon-rigging-homecoming.jpg" data-lb-sidebar-href="" data-lb-caption-extra-html="" data-single-image="1"> <div class="bbImageWrapper js-lbImage" title="dickon-rigging-homecoming.jpg" data-src="http://expo.survex.com/expofiles/photos/2019/BlogPostPhotos/dickon-rigging-homecoming.jpg" data-lb-sidebar-href="" data-lb-caption-extra-html="" data-single-image="1">
<img src="/years/2019/blogimages/dickon-rigging-homecoming.jpg" data-url="http://expo.survex.com/expofiles/photos/2019/BlogPostPhotos/dickon-rigging-homecoming.jpg" class="bbImage" data-zoom-target="1" style="" alt="dickon-rigging-homecoming.jpg" title="" width="" height="" loading="lazy"> <img src="/years/2019/blogimages/dickon-rigging-homecoming.jpg" data-url="http://expo.survex.com/expofiles/photos/2019/BlogPostPhotos/dickon-rigging-homecoming.jpg" class="bbImage" data-zoom-target="1" style="" alt="dickon-rigging-homecoming.jpg" title="" width="" height="" loading="lazy">
</div> </div>
@ -938,8 +935,8 @@ Now for the last challenge: to retrieve and sensibly rig the rope. Rad rigged th
<hr /> <hr />
<div class="tripdate" id="2019-07-20a">2019-07-20</div> <div class="tripdate" id="2019-07-20a">2019-07-20</div>
<div class="trippeople"><u>Daniel Heins</u>, Jon Toft, </div> <div class="trippeople">Jon Toft, <u>Daniel Heins</u>, </div>
<div class="triptitle">plateau - Prospecting beyond Homecoming</div> <div class="triptitle">plateau - Prospecting beyond Homecoming</div>
<br /><br /><b>Sat Jul 20 </b> <br /><br /><b>Sat Jul 20 </b>
<br /><br /> <br /><br />
As I had not done any prospecting this expo and Jon wanted to feel warmth again, we decided to head west to prospect on the plateau beyond Homecoming. Much As I had not done any prospecting this expo and Jon wanted to feel warmth again, we decided to head west to prospect on the plateau beyond Homecoming. Much
@ -947,16 +944,17 @@ bunder bashing and karst scrambling was done, and many chocked holes and snow pl
promising prospects in need of dropping. Jon has photos and a more clear understanding of location (as he logged them on the GPS), but as he is still up the promising prospects in need of dropping. Jon has photos and a more clear understanding of location (as he logged them on the GPS), but as he is still up the
plateau I will describe them in brief. plateau I will describe them in brief.
<br /><br /> <br /><br />
The Banana Hole is a deep pit in a large expanse of sloping limestone pavement up a hill. The bottom is beyond what can be seen with a caving light in day The Banana Hole [2019-HT-01] is a deep pit in a large expanse of sloping limestone pavement up a hill. The bottom is beyond what can be seen with a caving light in day
time, but dropping rocks gives roughly 4 seconds of free fall, before ricocheting further down and unknown amount. time, but dropping rocks gives roughly 4 seconds of free fall, before ricocheting further down and unknown amount.
<br /><br /> <br /><br />
The Boop-Boo-Da-Boop-Da-Boop [exact spelling pending confirmation] complex is an area of multiple very large holes surrounding a small flat expanse of karst, The Boop-Boo-Da-Boop-Da-Boop [exact spelling pending confirmation] [2019-HT-02] complex is an area of multiple very large holes surrounding a small flat expanse of karst,
half surrounded by cliffs. Two of the entrances are extremely appealing, with one a few meters wide and unknown depth (again, the rocks take long to go down, a half surrounded by cliffs. Two of the entrances are extremely appealing, with one a few meters wide and unknown depth (again, the rocks take long to go down, a
disto would've been helpful), and another similarly wide and quite deep and clearly going diagonally into the hillside, reducing likelihood of being choked. disto would've been helpful), and another similarly wide and quite deep and clearly going diagonally into the hillside, reducing likelihood of being choked.
<br /><br /> <br /><br />
Both of these leads really require photos to better explain (and someone with more awareness to convey their geography) but represent very exciting prospects Both of these leads really require photos to better explain (and someone with more awareness to convey their geography) but represent very exciting prospects
in a fairly untouched region of the plateau. in a fairly untouched region of the plateau.
<br />
<br />
<br /><br /> [Not on Blog - where does htis text fragment come from?]<br /> <br /><br /> [Not on Blog - where does htis text fragment come from?]<br />
A brief foray into Happy Butterfly found a Y-hang with a dangling hangar, and we could not locate the hilti to screw it back into, and so we turned back around A brief foray into Happy Butterfly found a Y-hang with a dangling hangar, and we could not locate the hilti to screw it back into, and so we turned back around
to avoid descenting a one-bolt-wonder. to avoid descenting a one-bolt-wonder.
@ -1233,7 +1231,6 @@ All the best,<br />
<br /> <br />
Crossley</div> Crossley</div>
</div> </div>
</div> </div>