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

2017-AMS-01 and ent fixes

Browse Source
This commit is contained in:
Philip Sargent 2023-10-18 00:17:49 +03:00
parent fda39ca7d1
commit 5fd137e1ee
8 changed files with 176 additions and 27 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

64
cave_data/1623-2017-AMS-01.html Normal file
View File

@ -0,0 +1,64 @@
<!DOCTYPE html>
<!-- This file is generated by troggle on Oct. 17, 2023, 6:45 p.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. 17, 2023, 6:45 p.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>1623-2017-AMS-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>Delicate Bridge Cave</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>1623</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>2017-AMS-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>1623-2017-AMS-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 1623-2017-AMS-01+1623-2017-AMS-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>Adam, Aidan, Philip - Corin &mp;Adam bottomed it the next day. No written up detils.</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>Hanging death loose bridge over entrance. Entrance pitch a few metres, leading to more depth.</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><a href="/logbookentry/2017-08-07/2017-08-07b">Logbook 2017-08-07b</a> and GPS track log</references><!-- References to documentation. Could be Journal articles or Logbook entries. Can be links if the docs are online. -->
<survey>none</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>1623/2017-AMS-01</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>

11
cave_data/1623-271.html
View File

@ -1,5 +1,5 @@
<!DOCTYPE html>
<!-- This file is generated by troggle on June 8, 2023, 10:06 a.m. UTC using the form documented at /handbook/survey/caveentry.html -->
<!-- This file is generated by troggle on Oct. 17, 2023, 9:24 p.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
@ -10,7 +10,7 @@ though, you do not need to do a data import as it happens automatically -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
</head>
<body>
<b>This file is generated by troggle</b> on June 8, 2023, 10:06 a.m. UTC using the form documented at
<b>This file is generated by troggle</b> on Oct. 17, 2023, 9:24 p.m. UTC using the form documented at
the form documented at
<a href="/handbook/survey/caveentry.html">handbook/survey/caveentry.html</a>
<br>
@ -19,7 +19,7 @@ the form documented at
<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>1623-271</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>Korokoroh&ouml;hle</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>1623</area><area>1d</area><!-- the CUCC-defined areas shown in http://expo.survex.com/areas.htm -->
<area>1623</area><!-- e.g. "1623" -->
<kataster_code>2/T x</kataster_code><!-- 'length-or-depth/type exploration'
code used in the Austrian kataster e.g '1/S +' - https://expo/.survex.com/katast.htm
@ -40,21 +40,24 @@ code used in the Austrian kataster e.g '1/S +' - https://expo/.survex.com/katast
<entrance>
<entranceslug>1623-271a</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 1623-271+1623-271a 'Z' =a= -->
<letter>a</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>
<entrance>
<entranceslug>1623-271b</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 1623-271+1623-271b 'Z' =b= -->
<letter>b</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>
<entrance>
<entranceslug>1623-271c</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 1623-271+1623-271c 'Z' =c= -->
<letter>c</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>CUCC 2007, 2015 (Jenny + Olly)</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>caves-1623/271/271.svx</survex_file><!-- Name of top-level survey file for this cave. Relative to the 'loser' survex repository. So for most caves that's "caves/cavenum/cavnum.svx". (e.g. caves/204/204.svx -->
<survex_file>caves-1623/271/271.svx</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><p>Low drafty entrance at base of small cliff quickly becomes walking/stooping passage. On the right is a 1m climb down to an undescended pitch (07-01B), next to this is another way on which leads to another undescended pitch (07-02C) with a passage appearing to continue beyond. A few metres further along the main passage is 271b, a skylight entrance (free-climbable). Continuing on leads to a small chamber and four way junction. The passage on the right soon chokes. The passage on the left quickly becomes very small and can be followed to pop out on a ledge part way down a shakehole (271c), there is a sound connection between a rift in the SE corner of this shakehole and 97. The main pitch in the shakehole is unexplored (15-03C). The passage continuing straight on from the chamber is bigger and soon reaches a drop which can be traversed over (crawling sized passage continues beyond, 15-01B), the drop is initially free-climbable, but then bells out (15-02B).</p></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></references><!-- References to documentation. Could be Journal articles or Logbook entries. Can be links if the docs are online. -->

59
entrance_data/1623-2017-AMS-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. 17, 2023, 6:45 p.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. 17, 2023, 6:45 p.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>1623-2017-AMS-01</slug> <!-- one entrance and one slug per entrance_data file -->
<name></name>
<entrance_description>hanging death over entrance: loose looking rock bridge</entrance_description>
<explorers></explorers>
<map_description></map_description>
<location_description></location_description>
<lastvisit>2017-07-18</lastvisit>
<approach>Close to ski pole (old ski pole used to belay ent pitch)</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>T</marking>
<marking_comment>tagged, but Adam lost the notes so we don't know what it was tagged with.</marking_comment>
<!-- findability options: ? = To be confirmed ...,
S = Surveyed,
L = Lost,
R = Refindable" -->
<findability>S</findability>
<findability_description></findability_description>
<alt></alt>
<lat_wgs84></lat_wgs84>
<long_wgs84></long_wgs84>
<tag_station>1623.p2017-ams-01</tag_station>
<other_station></other_station>
<other_description></other_description>
<bearings></bearings>
<url></url>
</entrance>
</body>
</html>

23
entrance_data/1623-271b.html
View File

@ -1,19 +1,31 @@
<!DOCTYPE html>
<!-- Only put one entrance in this file -->
<!-- If you edit this file, make sure you update the websites database -->
<!-- This file is generated by troggle on Oct. 17, 2023, 9:24 p.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. 17, 2023, 9:24 p.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>1623-271b</slug>
<slug>1623-271b</slug> <!-- one entrance and one slug per entrance_data file -->
<name>1623-271b</name>
<entrance_description>Skylight entrance. Unpromising looking entrance down a gryke in some limestone pavement. Discovered from the inside.</entrance_description>
<explorers>CUCC: Olly Betts and Jenny Black</explorers>
<map_description></map_description>
<location_description>Plateau</location_description>
<lastvisit></lastvisit>
<approach>From 97 or 2007-71a</approach>
<underground_description></underground_description>
<photo><p><a href="../expofiles/photos/2015/OllyJenny/jenny-bolting-at-271b_20828661702_o.jpg"><img src="271/jenny-bolting-at-271b_20828661702_small.jpg"></a></p><p>Photo &copy; Olly Betts 2015</p></photo>
@ -35,10 +47,9 @@
<findability>S</findability>
<findability_description></findability_description>
<alt></alt>
<northing></northing>
<easting></easting>
<tag_station>1623.p271</tag_station>
<exact_station></exact_station>
<lat_wgs84></lat_wgs84>
<long_wgs84></long_wgs84>
<tag_station>1623.p271b</tag_station>
<other_station></other_station>
<other_description></other_description>
<bearings></bearings>

23
entrance_data/1623-271c.html
View File

@ -1,19 +1,31 @@
<!DOCTYPE html>
<!-- Only put one entrance in this file -->
<!-- If you edit this file, make sure you update the websites database -->
<!-- This file is generated by troggle on Oct. 17, 2023, 9:24 p.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. 17, 2023, 9:24 p.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>1623-271c</slug>
<slug>1623-271c</slug> <!-- one entrance and one slug per entrance_data file -->
<name>1623-271c</name>
<entrance_description>Small unpromising looking tube from ledge part way down NW wall of large snow filled doline. Discovered from the inside.</entrance_description>
<explorers>CUCC: Olly Betts and Jenny Black</explorers>
<map_description></map_description>
<location_description>Plateau</location_description>
<lastvisit></lastvisit>
<approach>From 97</approach>
<underground_description></underground_description>
<photo><p><a href="../expofiles/photos/2015/OllyJenny/jenny-at-271c_20651320329_o.jpg"><img src="271/jenny-at-271c_20651320329_small.jpg"></a></p><p>Photo &copy; Olly Betts 2015</p></photo>
@ -35,10 +47,9 @@
<findability>S</findability>
<findability_description></findability_description>
<alt></alt>
<northing></northing>
<easting></easting>
<tag_station>1623.p271</tag_station>
<exact_station></exact_station>
<lat_wgs84></lat_wgs84>
<long_wgs84></long_wgs84>
<tag_station>1623.p271c</tag_station>
<other_station></other_station>
<other_description></other_description>
<bearings></bearings>

3
entrance_data/1623-78d.html
View File

@ -47,12 +47,9 @@ though, you do not need to do a data import as it happens automatically -->
<findability>S</findability>
<findability_description></findability_description>
<alt>1666</alt>
<northing></northing>
<easting></easting>
<lat_wgs84></lat_wgs84>
<long_wgs84></long_wgs84>
<tag_station></tag_station>
<exact_station></exact_station>
<other_station>1623.p78d</other_station>
<other_description></other_description>
<bearings></bearings>

9
handbook/survey/gps.htm
View File

@ -30,14 +30,13 @@ accurate) fixes on each entrance.</p>
<p>We now (2018) have differential GPS which is much more accurate than
in the past (e.g. Wookey's 1996 article) but altitudes are often very inaccurate
and GPOS devices don't tell you how inaccurate the altitude is.
and GPS devices don't generally tell you how inaccurate the altitude is.
<h3>Taking the fix</h3>
<p>Once you have chosen your point, mark it in some way (could be a spit hole
or a cairn, for example - we aren't supposed to use paint any more) and place
the GPS on the point. If you build a cairn, make it wide rather than high -
tall cairns are knocked down by the depth of snow each winter. Give it a
the GPS on the point. Don't build a cairn, they don't last for decades and we have survey stations that old. Give the GPS device a
couple of minutes to get a fairly good fix (the first figure reported may be
quite a way out, but after a couple of minutes things should settle). Then mark
the point as a waypoint. If you're feeling really keen, you can set it up for
@ -45,9 +44,7 @@ the point as a waypoint. If you're feeling really keen, you can set it up for
support this automatically, and with others you can just leave it recording a
track log, then record another waypoint at the same place just before you leave
so it's clear to someone examining the track log when you actually left.
(Averaging was once crucial to getting any kind of remotely close fix, but is
somewhat less important these days now that Selective Availability has been
turned off.)</p>
Averaging the readings like this is vital if you want an even vaguely accurate altitude reading.</p>
<p>While the GPS is recording your location, you can do something useful
(like rigging the cave, doing a surface survey from the GPS point to the

11
years/2017/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
when UK Caving blogs have been parsed.
Exported on 2023-10-17 16:10 using either the control panel webpage or when editing a logbook entry online
Exported on 2023-10-17 20: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)
-->
<body>
@ -24,6 +24,7 @@ See troggle/code/views/other.py and core.models/logbooks.py writelogbook(year, f
<p>
Back to index: <a href="index.html">Expo 2022 Reports</a>
Back to index: <a href="index.html">Expo 2022 Reports</a>
Back to index: <a href="index.html">Expo 2022 Reports</a>
<hr />
@ -951,7 +952,13 @@ Blog Author: nobrotson
<div class="tripdate" id="2017-08-07b">2017-08-07</div>
<div class="trippeople">Adam Aldridge, Aidan Marks, <u>Philip Sargent</u>, </div>
<div class="triptitle">plateau - Prospecting beyond FGH and GSH</div>
<ul> <li>GPS track recorded for whole walk (used Brendan’s GPS)</li> <li>Altitudes done (GPS) for FGH and GSH</li> <li>3 reasonable holes found</li> </ul> <br /><br /><i>#1 ‘Delicate Bridge Hole’: </i>near skipole, rigged from natural and steelpole section to snowslope, 40m. Tagged. <br /><img width=30% src="/years/2017/delicate-bridge.jpg"><br />[Adam and Corin returned to this the next day and crapped it out). <br /><br />#2 and 3: three big holes and pit, see survey notes. [WALLET?] <br/><img width=50% src="/years/2017/2017-08-07-track.jpg"><br /><br />[Editors note: Adam managed to mislay all the notes of this trip, including the numbers of the tags made and left in the caves; and the notes were not found on the 2018 or 2019 expos despite looking for them. They never went near a wallet apparently.]
<ul> <li>GPS track recorded for whole walk (used Brendan’s GPS)</li> <li>Altitudes done (GPS) for FGH and GSH</li> <li>3 reasonable holes found</li> </ul> <br /><br /><i>#1 ‘Delicate Bridge Hole’ [2017-AMS-01]: </i>near skipole, rigged from natural and steelpole section to snowslope, 40m. Tagged. <br /><img width=30% src="/years/2017/delicate-bridge.jpg"><br />[Adam and Corin returned to this the next day and crapped it out). <br /><br />#2 and 3: three big holes and pit, see survey notes. [LOST !]<br />
<pre>
lat="47.692963919" lon="13.808749951"
ele 1677.613525
name=080
comment=3 BIG HOLES
</pre> <br/><img width=50% src="/years/2017/2017-08-07-track.jpg"><br /><br />[Editors note: Adam managed to mislay all the notes of this trip, including the numbers of the tags made and left in the caves; and the notes were not found on the 2018 or 2019 expos despite looking for them. They never went near a wallet apparently.]
<br />
<br />One of our caves at 078 was re-found and pushed by Becka as 2023-BL-11 in 2023]
<div class="timeug">T/U: 0.0 hours</div>