sorting out 2018-ms-01, 02, 03, 04

This commit is contained in:
Philip Sargent 2023-10-12 15:28:38 +03:00
parent 4354eafd05
commit ba3def102b
13 changed files with 70 additions and 62 deletions

View File

@ -1,5 +1,5 @@
<!DOCTYPE html>
<!-- This file is generated by troggle on Aug. 5, 2023, 7:43 p.m. UTC using the form documented at /handbook/survey/caveentry.html -->
<!-- This file is generated by troggle on Oct. 12, 2023, 11:17 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
@ -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 Aug. 5, 2023, 7:43 p.m. UTC using the form documented at
<b>This file is generated by troggle</b> on Oct. 12, 2023, 11:17 a.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-2023-BL-10</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></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><!-- the CUCC-defined areas shown in http://expo.survex.com/areas.htm -->
<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
@ -45,7 +45,7 @@ code used in the Austrian kataster e.g '1/S +' - https://expo/.survex.com/katast
</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/cavenum/cavnum.svx". (e.g. caves/204/204.svx -->
<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></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. -->

View File

@ -1,5 +1,5 @@
<!DOCTYPE html>
<!-- This file is generated by troggle on Oct. 12, 2023, 10:31 a.m. UTC using the form documented at /handbook/survey/caveentry.html -->
<!-- This file is generated by troggle on Oct. 12, 2023, 12:21 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,16 +10,16 @@ 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 Oct. 12, 2023, 10:31 a.m. UTC using the form documented at
<b>This file is generated by troggle</b> on Oct. 12, 2023, 12:21 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-2018-MS-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' -->
<caveslug>1626-2018-MS-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></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" -->
<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
@ -39,8 +39,8 @@ code used in the Austrian kataster e.g '1/S +' - https://expo/.survex.com/katast
<unofficial_number>2018-MS-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-2018-MS-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-2018-MS-01+1623-2018-MS-01 'Z' == -->
<entranceslug>1626-2018-MS-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-2018-MS-01+1626-2018-MS-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>
@ -70,7 +70,7 @@ Becka, Tom, Mark Shinwell.</notes><!-- Normally empty, but place for anything el
<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/2018-MS-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')-->
<url>1626/2018-MS-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>

View File

@ -1,5 +1,5 @@
<!DOCTYPE html>
<!-- This file is generated by troggle on Oct. 12, 2023, 10:19 a.m. UTC using the form documented at /handbook/survey/caveentry.html -->
<!-- This file is generated by troggle on Oct. 12, 2023, 12:50 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,16 +10,16 @@ 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 Oct. 12, 2023, 10:19 a.m. UTC using the form documented at
<b>This file is generated by troggle</b> on Oct. 12, 2023, 12:50 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-2018-ms-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' -->
<caveslug>1626-2018-ms-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>Blitz Baum Schacht</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" -->
<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
@ -39,8 +39,8 @@ code used in the Austrian kataster e.g '1/S +' - https://expo/.survex.com/katast
<unofficial_number>2018-ms-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>1623-2018-ms-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 1623-2018-ms-02+1623-2018-ms-02 'Z' == -->
<entranceslug>1626-2018-ms-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-2018-ms-02+1626-2018-ms-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>
@ -61,7 +61,7 @@ code used in the Austrian kataster e.g '1/S +' - https://expo/.survex.com/katast
<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/2018-ms-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')-->
<url>1626/2018-ms-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>

View File

@ -1,5 +1,5 @@
<!DOCTYPE html>
<!-- This file is generated by troggle on Oct. 12, 2023, 10:19 a.m. UTC using the form documented at /handbook/survey/caveentry.html -->
<!-- This file is generated by troggle on Oct. 12, 2023, 12:44 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,16 +10,16 @@ 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 Oct. 12, 2023, 10:19 a.m. UTC using the form documented at
<b>This file is generated by troggle</b> on Oct. 12, 2023, 12:44 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-2018-ms-03</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' -->
<caveslug>1626-2018-ms-03</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></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" -->
<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
@ -39,8 +39,8 @@ code used in the Austrian kataster e.g '1/S +' - https://expo/.survex.com/katast
<unofficial_number>2018-ms-03</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-2018-ms-03</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-2018-ms-03+1623-2018-ms-03 'Z' == -->
<entranceslug>1626-2018-ms-03</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-2018-ms-03+1626-2018-ms-03 '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>
@ -60,7 +60,7 @@ code used in the Austrian kataster e.g '1/S +' - https://expo/.survex.com/katast
<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/2018-ms-03.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')-->
<url>1626/2018-ms-03.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>

View File

@ -1,5 +1,5 @@
<!DOCTYPE html>
<!-- This file is generated by troggle on Oct. 12, 2023, 10:20 a.m. UTC using the form documented at /handbook/survey/caveentry.html -->
<!-- This file is generated by troggle on Oct. 12, 2023, 1:14 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,16 +10,16 @@ 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 Oct. 12, 2023, 10:20 a.m. UTC using the form documented at
<b>This file is generated by troggle</b> on Oct. 12, 2023, 1:14 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-2018-ms-04</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' -->
<caveslug>1626-2018-ms-04</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>Zufall h&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><!-- e.g. "1623" -->
<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
@ -39,8 +39,8 @@ code used in the Austrian kataster e.g '1/S +' - https://expo/.survex.com/katast
<unofficial_number>2018-ms-04</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-2018-ms-04</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-2018-ms-04+1623-2018-ms-04 'Z' == -->
<entranceslug>1626-2018-ms-04</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-2018-ms-04+1626-2018-ms-04 '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>
@ -60,7 +60,7 @@ code used in the Austrian kataster e.g '1/S +' - https://expo/.survex.com/katast
<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/2018-ms-04.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')-->
<url>1626/2018-ms-04.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>

View File

@ -1,6 +1,6 @@
<!DOCTYPE html>
<!-- Only put one entrance in this file -->
<!-- This file is generated by troggle on Aug. 5, 2023, 7:35 p.m. UTC using the form documented at handbook/survey/ententry.html -->
<!-- This file is generated by troggle on Oct. 12, 2023, 11:17 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 -->
@ -14,7 +14,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 Aug. 5, 2023, 7:35 p.m. UTC using the form documented at
<b>This file is generated by troggle</b> on Oct. 12, 2023, 11:17 a.m. UTC using the form documented at
<a href="/handbook/survey/ententry.html">handbook/survey/ententry.html</a>
<br>
<entrance>
@ -47,10 +47,9 @@ though, you do not need to do a data import as it happens automatically -->
<findability>S</findability>
<findability_description></findability_description>
<alt></alt>
<northing></northing>
<easting></easting>
<lat_wgs84>47.69268</lat_wgs84>
<long_wgs84>13.81132</long_wgs84>
<tag_station></tag_station>
<exact_station></exact_station>
<other_station></other_station>
<other_description></other_description>
<bearings></bearings>

View File

@ -1,6 +1,6 @@
<!DOCTYPE html>
<!-- Only put one entrance in this file -->
<!-- This file is generated by troggle on Oct. 12, 2023, 10:31 a.m. UTC using the form documented at handbook/survey/ententry.html -->
<!-- This file is generated by troggle on Oct. 12, 2023, 12:21 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 -->
@ -14,12 +14,12 @@ 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 Oct. 12, 2023, 10:31 a.m. UTC using the form documented at
<b>This file is generated by troggle</b> on Oct. 12, 2023, 12:21 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-2018-MS-01</slug> <!-- one entrance and one slug per entrance_data file -->
<slug>1626-2018-MS-01</slug> <!-- one entrance and one slug per entrance_data file -->
<name>2018-MS-01</name>
<entrance_description>Lost - due to garbage GPS numbers</entrance_description>
<explorers></explorers>

View File

@ -1,6 +1,6 @@
<!DOCTYPE html>
<!-- Only put one entrance in this file -->
<!-- This file is generated by troggle on Oct. 12, 2023, 10:19 a.m. UTC using the form documented at handbook/survey/ententry.html -->
<!-- This file is generated by troggle on Oct. 12, 2023, 12:50 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 -->
@ -14,12 +14,12 @@ 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 Oct. 12, 2023, 10:19 a.m. UTC using the form documented at
<b>This file is generated by troggle</b> on Oct. 12, 2023, 12:50 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-2018-ms-03</slug> <!-- one entrance and one slug per entrance_data file -->
<slug>1626-2018-ms-02</slug> <!-- one entrance and one slug per entrance_data file -->
<name></name>
<entrance_description></entrance_description>
<explorers></explorers>
@ -49,7 +49,7 @@ though, you do not need to do a data import as it happens automatically -->
<alt></alt>
<lat_wgs84></lat_wgs84>
<long_wgs84></long_wgs84>
<tag_station>1623.p2018-ms-03</tag_station>
<tag_station>1626.p2018-ms-02</tag_station>
<other_station></other_station>
<other_description></other_description>
<bearings></bearings>

View File

@ -1,6 +1,6 @@
<!DOCTYPE html>
<!-- Only put one entrance in this file -->
<!-- This file is generated by troggle on Oct. 12, 2023, 10:20 a.m. UTC using the form documented at handbook/survey/ententry.html -->
<!-- This file is generated by troggle on Oct. 12, 2023, 12:44 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 -->
@ -14,12 +14,12 @@ 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 Oct. 12, 2023, 10:20 a.m. UTC using the form documented at
<b>This file is generated by troggle</b> on Oct. 12, 2023, 12:44 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-2018-ms-04</slug> <!-- one entrance and one slug per entrance_data file -->
<slug>1626-2018-ms-03</slug> <!-- one entrance and one slug per entrance_data file -->
<name></name>
<entrance_description></entrance_description>
<explorers></explorers>
@ -49,7 +49,7 @@ though, you do not need to do a data import as it happens automatically -->
<alt></alt>
<lat_wgs84></lat_wgs84>
<long_wgs84></long_wgs84>
<tag_station>1623.p2018-ms-04</tag_station>
<tag_station>1626.p2018-ms-03</tag_station>
<other_station></other_station>
<other_description></other_description>
<bearings></bearings>

View File

@ -1,6 +1,6 @@
<!DOCTYPE html>
<!-- Only put one entrance in this file -->
<!-- This file is generated by troggle on Oct. 12, 2023, 10:19 a.m. UTC using the form documented at handbook/survey/ententry.html -->
<!-- This file is generated by troggle on Oct. 12, 2023, 1:14 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 -->
@ -14,16 +14,16 @@ 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 Oct. 12, 2023, 10:19 a.m. UTC using the form documented at
<b>This file is generated by troggle</b> on Oct. 12, 2023, 1:14 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-2018-ms-02</slug> <!-- one entrance and one slug per entrance_data file -->
<slug>1626-2018-ms-04</slug> <!-- one entrance and one slug per entrance_data file -->
<name></name>
<entrance_description></entrance_description>
<explorers></explorers>
<map_description></map_description>
<map_description>1626.p2018-ms-04_LB is 600m away, probably bogus</map_description>
<location_description></location_description>
<lastvisit></lastvisit>
<approach></approach>
@ -44,13 +44,13 @@ though, you do not need to do a data import as it happens automatically -->
S = Surveyed,
L = Lost,
R = Refindable" -->
<findability>?</findability>
<findability>S</findability>
<findability_description></findability_description>
<alt></alt>
<lat_wgs84></lat_wgs84>
<long_wgs84></long_wgs84>
<tag_station>1623.p2018-ms-02</tag_station>
<other_station></other_station>
<tag_station>1626.p2018-ms-04</tag_station>
<other_station>1626.p2018-ms-04_LB</other_station>
<other_description></other_description>
<bearings></bearings>
<url></url>

Binary file not shown.

After

Width:  |  Height:  |  Size: 16 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 106 KiB

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-09-26 17:09 using either the control panel webpage or when editing a logbook entry online
Exported on 2023-10-12 13: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>
@ -76,21 +76,27 @@ Pushed past survey station 14C, found the phreatic tube lead to a small chamber
<hr />
<div class="tripdate" id="2018-07-11a">2018-07-11</div>
<div class="trippeople"><u>Becka Lawson</u>, Tom Crossley, Mark Shinwell, </div>
<div class="trippeople">Tom Crossley, Mark Shinwell, <u>Becka Lawson</u>, </div>
<div class="triptitle">plateau - Prospecting past Fisch Gesicht, beyond the ski pole line</div>
<br /><br />
<h3> All in area 1626 ?!</h3>
After the first spit had been set we realised that we'd forgotten the bolts, doh, so the tags for
these caves have been hammered into cracks and only cucc-2018-ms01 has a hole drilled.
<br />
<img width=30% src="/years/2018/2018-ms-04_etc.jpg">
<br />
<br /><br />
<b>cucc-2018-ms01</b><br />
Becka's phone GPS 33+ 410730 5274320 Alt 1698m Accuracy 4m<br />
<br />[Editorial note: this is a very accurate location of the bier tent in 2018 outside the potato hut, in fact. Not to be confused with a cave on the plateau.]<img width=20% src="/years/2018/2018-ms-01_LB.jpg">
<br />
Description: Rubble slope with snow plug down to a jammed boulder. Wriggle down next to it to a 45°
ramp down. This levels off to a tight squeeze down to a small chamber. Around 30m long with no draft.<br />
Sketch: see notes and photo on Becka's phone at 09:30 on 13/7/18<br />
Notes: tag hammered into crack near to placed spit<br />
Photo: Becka's phone at 14:00<br />
<br />
<br />
<br /><br />
<b>cucc-2018-ms02 Blitz Baum Schacht (Lightening Tree Shaft)</b><br />
Becka's phone GPS 33+ 410635 5283186 Alt 1724m Accuracy 4m (see also Mark's GPS)<br />
@ -98,7 +104,8 @@ Description: Around 30m NNE (say 020) from distinctive, large, dead tree struck
30m+ shaft, rocks rattle for several seconds. Hole ~5m long x 1m wide.<br />
Notes: tag hammered into crack on flat area on long side<br />
Photo: Becka's phone and Mark's phone at 14:56
<br />
<br />
<br /><br />
<b>cucc-2018-ms03 Zufall h&ouml;hle (Coincidence Cave)</b><br />
Becka's phone GPS 33+ 410376 5283124 Alt 1714m Accuracy 3m (see also Mark's GPS)<br />
@ -107,14 +114,16 @@ head of ~7m pitch. Weak draft out. This was re-found by Dickon and Jon later the
said there was also a phreatic tube visible from the pitch head. <br />
Notes: tag hammered into above entrance boulders <br />
Photo: Becka's phone and Mark's phone at 16:10
<br />
<br />
<br /><br />
<b>cucc-2018-ms04 </b><br />
Marks's phone GPS 00409613 5282951 Alt 1680m Accuracy 3m<br />
Description: 10m+ shaft, approx 2m long x 0.5m wide, in a line of similar shafts<br />
Notes: tag hammered into crack <br />
Photo: Mark's phone at 17:00
<br />
<br />
<img src="/years/2018/logbook1.jpg" width=100%>
<div class="timeug">T/U: 4.0 hours</div>
<div class="editentry"><br /><a href="/logbookedit/2018-07-11a">Edit this entry</a><br /></div>