renaming entrance_data files to match kataster numbers

This commit is contained in:
2024-07-02 18:59:30 +03:00
committed by Expo on server
parent 689adec8bc
commit 8e108c1567
20 changed files with 10 additions and 21 deletions

View File

@@ -17,9 +17,7 @@ the form documented at
<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>1626-LA34</caveslug><!--(Ignored). 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>R&auml;tselh&ouml;hle</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>1626</area><!-- e.g. "1623" -->
<kataster_code>3/S +</kataster_code><!-- 'length-or-depth/type exploration'
code used in the Austrian kataster e.g '1/S +' - https://expo/.survex.com/katast.htm
@@ -40,7 +38,6 @@ code used in the Austrian kataster e.g '1/S +' - https://expo/.survex.com/katast
<entrance>
<entranceslug>1626-la34</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 1626-LA34+1626-la34 '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>