expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2025-12-08 14:54:28 +00:00
Code Issues Packages Projects Releases Wiki Activity

alt - online edit of handbook/survey/ententry.html

Browse Source
This commit is contained in:
Expo on server
2023-10-16 23:57:38 +01:00
parent b742969cef
commit 955e6c6f19
1 changed files with 1 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
handbook/survey/ententry.html
View File

@@ -88,6 +88,7 @@ This page outlines step 7 of the survey production process. Each step is documen
*end 2023-js-01<br />
</code>
<p>There is a lot more to say about how to record the best GPS data, and how to link GPS with survey points, e.g. see <a href="gps.htm">Getting a GPS fix</a>
<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>In practice, for us on the plateau, we get repeat measurements of the same spot by different teams in different years to be accurate to only about 3m. This is fine for finding entrances, and for checking whether two different teams have found the same cave, but it is not adequate for loop-closure. That requires particular care with averaging the reading over 2 minutes, and use of a location with good view of the sky, away from vertical rock, and surface survey using instruments to get from the GPS point to the actual cave entrances. To get a decent <em>altitude</em> measurement requires averaging over 10 minutes, and it is still not good.