diff --git a/handbook/survey/coord2.html b/handbook/survey/coord2.html index 36ebf8e1e..88bf4389d 100644 --- a/handbook/survey/coord2.html +++ b/handbook/survey/coord2.html @@ -35,7 +35,7 @@

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.

Note that there are 6 digits starting 41... and 7 digits starting 52... This is not a mistake.

However, when you prospecting and discover a new cave, you possibly only have the WGS84 latitude and logitude from your phone, e.g. 47.690933 N 13.821467 E (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). -

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 New Cave and Entrance forms on troggle (step 6 of the dave data processing guide) in the lat/long. data entry fields. +

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 New Cave and Entrance forms on troggle (step 6 of the dave data processing guide) in the lat/long. data entry fields.

"Dataset" coordinates

We do all our serious geolocation within survex, using .svx survex files and using the conversion capabilities built into survex.

While cave entrance locations are input using a bewildering variety of different coordinate systems, the processing and output is now all standardised on using UTM33, i.e.