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

Online edit of cave 1623-2014-867

Browse Source
This commit is contained in:
Philip Sargent 2024-07-15 10:04:29 +01:00
parent d8ddd8ddd9
commit 50d7840bdd
1 changed files with 8 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
cave_data/1623-2014-867.html
View File

@ -1,5 +1,5 @@
<!DOCTYPE html>
<!-- This file is generated by troggle on Nov. 21, 2023, 4:47 p.m. UTC using the form documented at /handbook/survey/caveentry.html -->
<!-- This file is generated by troggle on July 15, 2024, 10:04 a.m. UTC using the form documented at /handbook/survey/caveentry.html -->
<!-- Only put one cave in this file -->
<!-- If you edit this 162x-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,14 +10,14 @@ 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 Nov. 21, 2023, 4:47 p.m. UTC using the form documented at
<b>This file is generated by troggle</b> on July 15, 2024, 10:04 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>1623-2014-867</caveslug><!--(Ignored). Internal I.D. formerlly used. Using filename'' -->
<!--<caveslug></caveslug>--> <!-- Ignored. No longer required, we use the filename instead e.g. 1623-315 for 1623-315.html -->
<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" -->
<kataster_code></kataster_code><!-- 'length-or-depth/type exploration'
@ -40,7 +40,7 @@ code used in the Austrian kataster e.g '1/S +' - https://expo/.survex.com/katast
<entrance>
<entranceslug>1623-2014-867</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 -->
<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. -->
<letter></letter><!--Leave blank for single-entrance cave. If there is more than one entrance then the letter needs to be given. Must match 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. -->
@ -48,7 +48,10 @@ code used in the Austrian kataster e.g '1/S +' - https://expo/.survex.com/katast
<underground_description>TO DO 2014-BL-01
<p><a href='/1623/2014-867/l/notes-1-876.html'><img width=70% src='/1623/2014-867/i/notes-1-876.jpg' /></a></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>Wallet <a href="/walletedit/2014:24">2014#24</a><p>Probably this logbook entry <a href="/logbookentry/2014-08-01/2014-08-01c">2014 08 01</a> "After a few hours found only one good lead (2014-777) and decided to turn for home, travelled S back to the end of the cairned route but found a more promising hole (2014-888)" so 867 is presumably between 777 and 888.</references><!-- References to documentation. Could be Journal articles or Logbook entries. Can be links if the docs are online. -->
<references>Wallet <a href="/walletedit/2014:24">2014#24</a>
<p>Definitely this logbook entry: <a href="/logbookentry/2014-07-29/2014-07-29a">29th July 2014</a>
<p>Probably this logbook entry <a href="/logbookentry/2014-08-01/2014-08-01c">2014 08 01</a> "After a few hours found only one good lead (2014-777) and decided to turn for home, travelled S back to the end of the cairned route but found a more promising hole (2014-888)" so 867 is presumably between 777 and 888.</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. -->
<notes>'867' is the sort of number that indicates a Waypoint in a GPS track.</notes><!-- Normally empty, but place for anything else that should be noted, such as info on cave maybe being a duplicate, or lost, and whether a kataster form has been sent to Austria for this cave -->
<length></length><!-- Cave length. Can be left blank and system should fill it in automatically from survey data (it doesn't yet) -->