fix url - online edit of handbook/survey/coord2.html

This commit is contained in:
Expo on server 2024-07-20 11:29:53 +01:00
parent 1d685cfd67
commit 87f9c66dbf

View File

@ -35,7 +35,7 @@
<p>These might be called "dataset coordinates" in expo-speak, but note that some people historically used this to mean the coordinate system in common use on an expo many years ago, which would not be the same.
<p><em>Note that there are 6 digits starting 41... and 7 digits starting 52... This is not a mistake.</em>
<p>However, when you prospecting and discover a new cave, you possibly only have the WGS84 latitude and logitude from your phone, e.g. <var>47.690933 N 13.821467 E</var> (degrees and decimals of degrees, set your phone to produce this: none of that degrees/minutes/seconds stuff, but if that's all that you have, we can work with that).
<p>So when you are recording the position of a completely new entrance, before you do any surveying, it will be the WGS84 lat/long that you will be writing down on the survey notes, and which will get scanned into the wallet back at base, and which you will enter into the <a href="/handbook/survey/caveentry.html">New Cave and Entrance forms</a> on troggle (step 6 of the dave data processing guide) in the lat/long. data entry fields.
<p>So when you are recording the position of a completely new entrance, before you do any surveying, it will be the WGS84 lat/long that you will be writing down on the survey notes, and which will get scanned into the wallet back at base, and which you will enter into the <a href="/handbook/l/new-cave-form.html">New Cave and Entrance forms</a> on troggle (step 6 of the dave data processing guide) in the lat/long. data entry fields.
<h3>"Dataset" coordinates</h3>
<p>We do all our serious geolocation within survex, using .svx survex files and using the conversion capabilities built into survex.
<p>While cave entrance locations are <em>input</em> using a bewildering variety of different coordinate systems, the processing and output is now all standardised on using UTM33, i.e.