diff --git a/cave_data/1623-2023-JS-02.html b/cave_data/1623-2023-JS-02.html
index 83cfb1bfc..bd90a20b0 100644
--- a/cave_data/1623-2023-JS-02.html
+++ b/cave_data/1623-2023-JS-02.html
@@ -1,5 +1,5 @@
 <!DOCTYPE html>
-<!-- This file is generated by troggle on Aug. 20, 2023, 5:14 p.m. UTC using the form documented at /handbook/survey/caveentry.html -->
+<!-- This file is generated by troggle on Oct. 17, 2023, 4:16 p.m. UTC using the form documented at /handbook/survey/caveentry.html -->
 <!-- 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,
 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 Aug. 20, 2023, 5:14 p.m. UTC using the form documented at
+<b>This file is generated by troggle</b> on Oct. 17, 2023, 4:16 p.m. UTC using the form documented at
 the form documented at 
 <a href="/handbook/survey/caveentry.html">handbook/survey/caveentry.html</a>
 <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. -->
 <caveslug>1623-2023-JS-02</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></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'
 code used in the Austrian kataster e.g '1/S +' - https://expo/.survex.com/katast.htm
 
@@ -45,7 +45,7 @@ code used in the Austrian kataster e.g '1/S +' - https://expo/.survex.com/katast
 </entrance>
 
 <explorers>Joel Stobbart, Emily Mabbet, Lizzie Caisley, Tom Phillips, Merryn Matthews.</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></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></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>Promising large opening leads ~5m WNW, promtly choking with boulders.</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>None</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></references><!-- References to documentation. Could be Journal articles or Logbook entries. Can be links if the docs are online. -->
diff --git a/entrance_data/1623-2023-JS-02.html b/entrance_data/1623-2023-JS-02.html
index 9355b50da..8c25a8442 100644
--- a/entrance_data/1623-2023-JS-02.html
+++ b/entrance_data/1623-2023-JS-02.html
@@ -1,6 +1,6 @@
 <!DOCTYPE html>
 <!-- Only put one entrance in this file -->
-<!-- This file is generated by troggle on Aug. 20, 2023, 5:14 p.m. UTC using the form documented at handbook/survey/ententry.html -->
+<!-- This file is generated by troggle on Oct. 17, 2023, 4:16 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,
 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 -->
@@ -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"/>
 </head>
 <body>
-<b>This file is generated by troggle</b> on Aug. 20, 2023, 5:14 p.m. UTC using the form documented at 
+<b>This file is generated by troggle</b> on Oct. 17, 2023, 4:16 p.m. UTC using the form documented at 
 <a href="/handbook/survey/ententry.html">handbook/survey/ententry.html</a>
 <br>
 <entrance>
@@ -47,10 +47,9 @@ though, you do not need to do a data import as it happens automatically -->
 <findability>S</findability>
 <findability_description></findability_description>
 <alt>1745</alt>
-<northing></northing>
-<easting></easting> 
+<lat_wgs84></lat_wgs84> 
+<long_wgs84></long_wgs84> 
 <tag_station></tag_station>
-<exact_station></exact_station>
 <other_station>1623.p2023-js-02</other_station>
 <other_description></other_description>
 <bearings></bearings>
diff --git a/handbook/survey/newsurvex.html b/handbook/survey/newsurvex.html
index 07ed79c79..fff835387 100644
--- a/handbook/survey/newsurvex.html
+++ b/handbook/survey/newsurvex.html
@@ -75,7 +75,7 @@ This page outlines step 3 of the survey production process. Each step is documen
   <p>The (strongly) recommended procedure is to take a specific GPS measurement  at a well-defined point and to write down the location on your prospecting survey notes. Then for a new discovery it will be copied onto the New Cave data sheet.
 
 <p>Note that we record the location in degrees and decimals of degrees: <code>47.69055 13.80841</code> and the altitude is in metres. 
-  
+  <p>The altitude is not nearly as vital as the lat/long numbers. GPS altitudes are still pretty bad, and even the new Galileo system won't promise anything better than &plusmn; 0.4m in 2030. (If you take the altitude from a track while moving the altitude can easily be 15m wrong.)
     <p>See <a href="#location">the bottom of this page</a> for how the location information is typed in.
     
 
@@ -245,7 +245,6 @@ telling them to use the online form.]
 <p>The location of the cave is, eventually,  stored in a survex file, just <em>not the same survex file</em>. 
   <p><b>If you are doing this for the first time</b>, don't bother with this *fix stuff. Just type the latitude &amp; logitude numbers into the <a href="ententry.html">New Entrance form</a> and someone else will do the *fix stuff.
 
-<p>There is a lot more to say about how to record the best GPS data, and how to link GPS with survey points. See <a href="ententry.html#fix">more on *fix</a>.
   
 <h3><a id="tickingoff">Entering the cave description in the survex file</a></h3>
 <p>The last part of the survex file is a description of the passage surveyed. Remember
