Online edit of entrance 1623-2023-mg-03c

This commit is contained in:
Philip Sargent 2023-10-06 23:58:36 +01:00
parent 38e823fa9a
commit d07652185b
2 changed files with 17 additions and 12 deletions

View File

@ -1,5 +1,5 @@
<!DOCTYPE html> <!DOCTYPE html>
<!-- This file is generated by troggle on July 13, 2023, 11:13 p.m. UTC using the form documented at /handbook/survey/caveentry.html --> <!-- This file is generated by troggle on Oct. 6, 2023, 11:58 p.m. UTC using the form documented at /handbook/survey/caveentry.html -->
<!-- Only put one cave in this file --> <!-- 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 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 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"/> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
</head> </head>
<body> <body>
<b>This file is generated by troggle</b> on July 13, 2023, 11:13 p.m. UTC using the form documented at <b>This file is generated by troggle</b> on Oct. 6, 2023, 11:58 p.m. UTC using the form documented at
the form documented at the form documented at
<a href="/handbook/survey/caveentry.html">handbook/survey/caveentry.html</a> <a href="/handbook/survey/caveentry.html">handbook/survey/caveentry.html</a>
<br> <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. --> <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-mg-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>1623-2023-mg-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>Kaltsalamanderhoehle</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--> <official_name>Kaltsalamanderhoehle</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' <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 code used in the Austrian kataster e.g '1/S +' - https://expo/.survex.com/katast.htm
@ -38,29 +38,32 @@ code used in the Austrian kataster e.g '1/S +' - https://expo/.survex.com/katast
<kataster_number></kataster_number> <!-- (Either this or unofficial_number is required). Official number in Austrian kataster if one has been allocated --> <kataster_number></kataster_number> <!-- (Either this or unofficial_number is required). Official number in Austrian kataster if one has been allocated -->
<unofficial_number>2023-mg-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'--> <unofficial_number>2023-mg-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-2023-mg-03c</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-2023-mg-03+1623-2023-mg-03c '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>
<entrance> <entrance>
<entranceslug>1623-2023-mg-03a</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 --> <entranceslug>1623-2023-mg-03a</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-2023-mg-03+1623-2023-mg-03a '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. --> <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>
<entrance> <entrance>
<entranceslug>1623-2023-mg-03b</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 --> <entranceslug>1623-2023-mg-03b</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-2023-mg-03+1623-2023-mg-03b '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. --> <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>
<entrance>
<entranceslug>1623-2023-mg-03c</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>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>
<entrance> <entrance>
<entranceslug>1623-2023-mg-03d</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 --> <entranceslug>1623-2023-mg-03d</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-2023-mg-03+1623-2023-mg-03d 'Z' =d= -->
<letter>d</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>d</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>
<explorers>Martin Green, Janis Huns, Zac Woodford</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. --> <explorers>Martin Green, Janis Huns, Zac Woodford</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/2023-mg-03/2023-mg-03.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/2023-mg-03/2023-mg-03.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>Cold Salamander Cave is formed along an obvious surfacee weakness going from SW to NE. In 2023 the most south westely entrance (A), could be down climbed for 2m to a snow pile. This was descended with the aid of a handline into a significant chamber. A few metres to the North East another shaft (B) also entered but with a pitch down to the snow slope. The chamber is deorated with several 4m long icicles and a stationary Salamander.</p> <underground_description><p>Cold Salamander Cave is formed along an obvious surfacee weakness going from SW to NE. In 2023 the most south westely entrance (A), could be down climbed for 2m to a snow pile. This was descended with the aid of a handline into a significant chamber. A few metres to the North East another shaft (B) also entered but with a pitch down to the snow slope. The chamber is deorated with several 4m long icicles and a stationary Salamander.</p>
<a href='/1623/2023-mg-03/l/pls_make_this_my_mugshot.html'><img src='/1623/2023-mg-03/t/pls_make_this_my_mugshot.jpg' /></a> <a href='/1623/2023-mg-03/l/pls_make_this_my_mugshot.html'><img src='/1623/2023-mg-03/t/pls_make_this_my_mugshot.jpg' /></a>

View File

@ -1,6 +1,6 @@
<!DOCTYPE html> <!DOCTYPE html>
<!-- Only put one entrance in this file --> <!-- Only put one entrance in this file -->
<!-- This file is generated by troggle on July 13, 2023, 9:13 p.m. UTC using the form documented at handbook/survey/ententry.html --> <!-- This file is generated by troggle on Oct. 6, 2023, 11:58 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, <!-- 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 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 --> 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"/> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
</head> </head>
<body> <body>
<b>This file is generated by troggle</b> on July 13, 2023, 9:13 p.m. UTC using the form documented at <b>This file is generated by troggle</b> on Oct. 6, 2023, 11:58 p.m. UTC using the form documented at
<a href="/handbook/survey/ententry.html">handbook/survey/ententry.html</a> <a href="/handbook/survey/ententry.html">handbook/survey/ententry.html</a>
<br> <br>
<entrance> <entrance>
@ -49,9 +49,11 @@ though, you do not need to do a data import as it happens automatically -->
<alt></alt> <alt></alt>
<northing></northing> <northing></northing>
<easting></easting> <easting></easting>
<lat_wgs84></lat_wgs84>
<long_wgs84></long_wgs84>
<tag_station></tag_station> <tag_station></tag_station>
<exact_station></exact_station> <exact_station></exact_station>
<other_station>1623.p2023-mg-03.9</other_station> <other_station>1623.2023-mg-03.9</other_station>
<other_description></other_description> <other_description></other_description>
<bearings></bearings> <bearings></bearings>
<url></url> <url></url>