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

copied text from :loser:/kataster-renumbering-README.txt in here - online edit of handbook/computing/newkataster.html

Browse Source
This commit is contained in:
philip s 2025-01-21 14:29:16 +00:00 committed by Expo on server
parent d1f1080849
commit b70f533025
1 changed files with 72 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

75
handbook/computing/newkataster.html
View File

@ -1,4 +1,4 @@
<html><head><title>New Katasetr Number Procedure</title></head><body> <html><head><title>New Kataster Number Procedure</title></head><body>
<h2 id="tophead">Data Maintenance - new cave id</h2> <h2 id="tophead">Data Maintenance - new cave id</h2>
<h1>Expo Data Maintenance</h1> <h1>Expo Data Maintenance</h1>
@ -35,13 +35,82 @@ Troggle: in the :expoweb: repo
<p> more here.. <p> more here..
<h2>Edit the survex files</h2> <h2>Edit the survex files</h2>
<p> more here.. <p> more here.. Need to edit this neatly.. taken from<var>:loser:/kataster-renumbering-README.txt</var>
<pre>
README for renumbering caves using new kataster numbers
e.g. 2023-ASH-15 => 1623-303
NB We are moving the survex files to new directories, but (not yet) moving the cave description and entrance description files.
expoweb/cave_data/1623-2023-ASH-15.html
1. Edit the cave file expoweb/cave_data/1623-2023-ASH-15.html and change to <caveslug>1623-303</caveslug>
2. Add the new kataster number: <kataster_number>303</kataster_number>
3. Leave this untouched: <unofficial_number>2023-ASH-15</unofficial_number>
4. Don't touch the <entranceslug>1623-2023-ASH-15</entranceslug> field for all the entrances
In the loser repo, rename the folder
loser/2023-ASH-15/
to
loser/303/
and then inside that folder rename the file
2023-ASH-15.svx
to
303.svx
And then edit any survex files which refer to that survex data ! (more explanation needed)
Change *fix points in loser/fixedpts/gps/gps23.svx from
*fix 1623.p2023-ASH-15 ...
to
*fix 1623.p303...
This may well not work due to the crapness of the "system" of recording fixed points. Much
time can now be wasted tracking down how the cave is located, furtling around in the innards
of files sprinkled all over the database. Remember that 1626 caves are stored in a completely
different way to 1623 caves.
Now go back and edit all the entrances of the cave to refer to this new *fix point
in the entrance editing page on
/1623/303/303.html
Select each entrance and look at the field
"Tag station: Survex station id, e.g. 1623.p2023-aa-01: "
and change
1623.p2023-ASH-15
to
1623.p303
If there is more than one entrance, this would be
1623.p2023-ASH-15a
to
1623.p303a
for a, b. c etc.
Find all the wallets for this cave
/cave/scans/1623-2023-ASH-15
and in each of them use the wallet edit page to correct the svx file link from
['caves-1623/2023-ASH-15/2023-ASH-15.svx']
to
['caves-1623/303/303.svx']
</pre>
<h2 id=cavealiases>Cave Aliases</h2> <h2 id=cavealiases>Cave Aliases</h2>
<p> Cave alias names can be edited by any logged-in user using an online form: <p> Cave alias names can be edited by any logged-in user using an online form:
<a href="/cave_data/cavealiases.txt_edit">/cave_data/cavealiases.txt</a> <a href="/cave_data/cavealiases.txt_edit">/cave_data/cavealiases.txt</a>
<p><em>However</em>, if you make a formatting mistake, all of troggle will <em>break instantly</em>. <br /><em>However</em>, if you make a formatting mistake, all of troggle will <em>break instantly</em>.
<ul>
<li>go to the webpage
https://expo.survex.com/cave_data/cavealiases.txt_edit
<li>Add the alias to some sensible place in this file, e.g. (using the example above)<br />
("2023-ASH-15", "1623-303"),
<li>Save and exit.
</ul>
adding this alias means that old logbook entries and wallets that refer to '2023-ASH-15' will be redirected to 1623-303 properly.
<p>When a lot are being done, as Becka did in 2024 when she got the new kataster numbers 1623-303 to 1623-316, it is a good idea to cross check (or to edit with a macro) the output from git, e.g. <p>When a lot are being done, as Becka did in 2024 when she got the new kataster numbers 1623-303 to 1623-316, it is a good idea to cross check (or to edit with a macro) the output from git, e.g.
<pre><code> # rename caves-1623/{2023-ASH-15/2023-ASH-15.svx => 303/303.svx} (94%) <pre><code> # rename caves-1623/{2023-ASH-15/2023-ASH-15.svx => 303/303.svx} (94%)