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

Online edit of cave 1623-2024-JC-01

Browse Source
This commit is contained in:
Expo on server 2024-09-27 01:37:47 +01:00
parent d5d67fd9c1
commit cffb8a6f26
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
cave_data/1623-2024-jc-01.html
View File

@ -1,5 +1,5 @@
<!DOCTYPE html>
<!-- This file is generated by troggle on Sept. 11, 2024, 3:54 a.m. UTC using the form documented at /handbook/survey/caveentry.html -->
<!-- This file is generated by troggle on Sept. 27, 2024, 1:37 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,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 Sept. 11, 2024, 3:54 a.m. UTC using the form documented at
<b>This file is generated by troggle</b> on Sept. 27, 2024, 1:37 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,7 +36,7 @@ code used in the Austrian kataster e.g '1/S +' - https://expo/.survex.com/katast
+ 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>2024-jc-01</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'-->
<unofficial_number>2024-JC-01</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-2024-jc-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 -->
@ -48,7 +48,7 @@ code used in the Austrian kataster e.g '1/S +' - https://expo/.survex.com/katast
<underground_description>No cave description created yet.</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="/walletedit/2024:15">2024#15</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. -->
<survey>1623/2024-JC-01/2024-JC-01.pdf</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><pre>
;GPS point GPSed for 35mins (but track contained no data for this
; period probably due to filtering, so start and stop locations (which matched nicel used)