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

fix bad capitals

Browse Source
This commit is contained in:
Philip Sargent 2024-08-03 23:50:40 +03:00
parent 77483e62dc
commit 69ade98139
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
cave_data/1623-2024-ND-01.html
View File

@ -39,8 +39,8 @@ code used in the Austrian kataster e.g '1/S +' - https://expo/.survex.com/katast
<unofficial_number>2024-nd-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-ND-01A</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>A</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. -->
<entranceslug>1623-2024-ND-01a</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>a</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. -->

2
entrance_data/1623-2024-ND-01A.html → entrance_data/1623-2024-ND-01a.html
View File

@ -19,7 +19,7 @@ though, you do not need to do a data import as it happens automatically -->
<br>
<entrance>
<non_public>False</non_public>
<slug>1623-2024-ND-01A</slug> <!-- one entrance and one slug per entrance_data file -->
<slug>1623-2024-ND-01a</slug> <!-- one entrance and one slug per entrance_data file -->
<name></name>
<entrance_description></entrance_description>
<explorers></explorers>