mirror of
https://expo.survex.com/repositories/expoweb/.git/
synced 2024-11-21 14:51:54 +00:00
Online edit of cave 1623-285
This commit is contained in:
parent
61684de0a1
commit
0fbad90dba
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE html>
|
||||
<!-- This file is generated by troggle on Nov. 2, 2023, 8:15 p.m. UTC using the form documented at /handbook/survey/caveentry.html -->
|
||||
<!-- This file is generated by troggle on Feb. 21, 2024, 1:50 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,
|
||||
<!-- 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
|
||||
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 -->
|
||||
@ -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 Nov. 2, 2023, 8:15 p.m. UTC using the form documented at
|
||||
<b>This file is generated by troggle</b> on Feb. 21, 2024, 1:50 a.m. UTC using the form documented at
|
||||
the form documented at
|
||||
<a href="/handbook/survey/caveentry.html">handbook/survey/caveentry.html</a>
|
||||
<br>
|
||||
@ -36,11 +36,10 @@ code used in the Austrian kataster e.g '1/S +' - https://expo/.survex.com/katast
|
||||
+ erforscht (exploration considered complete)
|
||||
-->
|
||||
<kataster_number>285</kataster_number> <!-- (Either this or unofficial_number is required). Official number in Austrian kataster if one has been allocated -->
|
||||
<unofficial_number>2006-08</unofficial_number><!-- (Either this or kataster_number is required). Initial temporary cave ID used until kataster number is allocated e.g. '2012-DD-01'-->
|
||||
<unofficial_number>2006-08</unofficial_number><!-- (This is any name. 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-285</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-285+1623-285 '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>
|
||||
|
||||
@ -48,17 +47,14 @@ code used in the Austrian kataster e.g '1/S +' - https://expo/.survex.com/katast
|
||||
<survex_file>caves-1623/285/285.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>Boulder slope leading to impenetrable choke after 12m</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>None required</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>2006 logbook</references><!-- References to documentation. Could be Journal articles or Logbook entries. Can be links if the docs are online. -->
|
||||
<references><a href="/logbookentry/2006-08-07/2006-08-07a">2006 logbook</a></references><!-- References to documentation. Could be Journal articles or Logbook entries. Can be links if the docs are online. -->
|
||||
<survey></p><div class="centre"><img src="plan.jpg" /> <img src="elev.jpg" /></div><p>Notes in 2006#33</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>In dataset</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>English translation: Knackered Tacklesack Cave</notes><!-- Normally empty, but place for anything else that should be noted, such as info on cave maybe being a duplicate, or lost -->
|
||||
<notes>English translation: Knackered Tacklesack Cave</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) -->
|
||||
<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/285/285.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>
|
||||
|
Loading…
Reference in New Issue
Block a user