diff --git a/cave_data/1623-2017-AMS-01.html b/cave_data/1623-2017-AMS-01.html new file mode 100644 index 000000000..c76470d9c --- /dev/null +++ b/cave_data/1623-2017-AMS-01.html @@ -0,0 +1,64 @@ + + + + + + +
+ + + +This file is generated by troggle on Oct. 17, 2023, 6:45 p.m. UTC using the form documented at +the form documented at +handbook/survey/caveentry.html +Low drafty entrance at base of small cliff quickly becomes walking/stooping passage. On the right is a 1m climb down to an undescended pitch (07-01B), next to this is another way on which leads to another undescended pitch (07-02C) with a passage appearing to continue beyond. A few metres further along the main passage is 271b, a skylight entrance (free-climbable). Continuing on leads to a small chamber and four way junction. The passage on the right soon chokes. The passage on the left quickly becomes very small and can be followed to pop out on a ledge part way down a shakehole (271c), there is a sound connection between a rift in the SE corner of this shakehole and 97. The main pitch in the shakehole is unexplored (15-03C). The passage continuing straight on from the chamber is bigger and soon reaches a drop which can be traversed over (crawling sized passage continues beyond, 15-01B), the drop is initially free-climbable, but then bells out (15-02B).
Photo © Olly Betts 2015
Photo © Olly Betts 2015
We now (2018) have differential GPS which is much more accurate than in the past (e.g. Wookey's 1996 article) but altitudes are often very inaccurate -and GPOS devices don't tell you how inaccurate the altitude is. +and GPS devices don't generally tell you how inaccurate the altitude is.
Once you have chosen your point, mark it in some way (could be a spit hole or a cairn, for example - we aren't supposed to use paint any more) and place -the GPS on the point. If you build a cairn, make it wide rather than high - -tall cairns are knocked down by the depth of snow each winter. Give it a +the GPS on the point. Don't build a cairn, they don't last for decades and we have survey stations that old. Give the GPS device a couple of minutes to get a fairly good fix (the first figure reported may be quite a way out, but after a couple of minutes things should settle). Then mark the point as a waypoint. If you're feeling really keen, you can set it up for @@ -45,9 +44,7 @@ the point as a waypoint. If you're feeling really keen, you can set it up for support this automatically, and with others you can just leave it recording a track log, then record another waypoint at the same place just before you leave so it's clear to someone examining the track log when you actually left. -(Averaging was once crucial to getting any kind of remotely close fix, but is -somewhat less important these days now that Selective Availability has been -turned off.)
+Averaging the readings like this is vital if you want an even vaguely accurate altitude reading.While the GPS is recording your location, you can do something useful (like rigging the cave, doing a surface survey from the GPS point to the diff --git a/years/2017/logbook.html b/years/2017/logbook.html index b838dc36e..c799f3261 100644 --- a/years/2017/logbook.html +++ b/years/2017/logbook.html @@ -14,7 +14,7 @@ maintain half a dozen parser functions. Sorry about all the crap that surrounds the image tags which has been imported along with the content when UK Caving blogs have been parsed. -Exported on 2023-10-17 16:10 using either the control panel webpage or when editing a logbook entry online +Exported on 2023-10-17 20:10 using either the control panel webpage or when editing a logbook entry online See troggle/code/views/other.py and core.models/logbooks.py writelogbook(year, filename) -->
@@ -24,6 +24,7 @@ See troggle/code/views/other.py and core.models/logbooks.py writelogbook(year, fBack to index: Expo 2022 Reports Back to index: Expo 2022 Reports +Back to index: Expo 2022 Reports
+lat="47.692963919" lon="13.808749951" +ele 1677.613525 +name=080 +comment=3 BIG HOLES +