gps and *fix docs

This commit is contained in:
2023-10-17 18:45:01 +03:00
parent 5337a86518
commit 9364f3496b
3 changed files with 9 additions and 11 deletions

View File

@@ -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