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

Online edit of logbookentry 2024-07-21c

Browse Source
This commit is contained in:
Philip Sargent
2025-05-11 16:50:51 +01:00
committed by Expo on server
parent 5548ddf004
commit d5f94062bb
1 changed files with 10 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
years/2024/logbook.html
View File

@@ -16,7 +16,7 @@ re-written. This is prevent spurious re-orderings and spurious git commit lines
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 2025-04-14 14:04 using either the control panel webpage or when editing a logbook entry online
Exported on 2025-05-11 16:05 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)
-->
<body>
@@ -1123,10 +1123,10 @@ ADDENDUM 26th July:
<div class="timeug">T/U: 0.0 hours</div>
<div class="editentry"><br /><a href="/logbookedit/2024-07-21b">Edit this entry</a><br /></div>
<hr />
<div class="tripdate" id="2024-07-21d">2024-07-21</div>
<div class="trippeople"><u>Philip S.</u></div>
<div class="triptitle">Photo GPS is unreliable</div>
<div class="tripdate" id="2024-07-21c">2024-07-21</div>
<div class="trippeople"><u>Philip S.</u></div>
<div class="triptitle">Photo - Photo GPS is unreliable</div>
During this same trip walking to Geschandalm, later analysis of the GPS locations of various photos showed a lot of variability.
This is a particularly clear example where the location is obvious in the photo (it is definitely on the path)
but the GPS location stored by the phone camera is 60m away.
@@ -1143,17 +1143,16 @@ such as this one right by the shady cliff (photo EXIF GPS locations are orange d
<p>
The lesson to take away from this is to always take TWO photos at any one position, and throw away the first one.
This will nearly always work for most people, and is sufficiently simple that even undergraduates can remember it.
ALternatively, always continually record a GPS track on the phone you are using to take photos with -
Alternatively, always continually record a GPS track on the phone you are using to take photos with -
though this is unfortunately not always reliable either, as the camera app tends to cache locations and doesn't always
get a fresh one from the "location" module in the phone.
</p>
<br>
<div class="timeug">T/U: 0.0 hours</div>
<div class="editentry"><br /><a href="/logbookedit/2024-07-21b">Edit this entry</a><br /></div>
<div class="editentry"><br /><a href="/logbookedit/2024-07-21c">Edit this entry</a><br /></div>
<hr />
<div class="tripdate" id="2024-07-21c">2024-07-21</div>
<div class="tripdate" id="2024-07-21d">2024-07-21</div>
<div class="trippeople"><u>Lara</u>, Charlotte, Chi, Harry</div>
<div class="triptitle">Homecoming - A satisfying but not very useful result</div>
Slavedriver Payne woke us up early and we got up the hill vaguely fast (despite Chi's moderate faff). Unfortunately further faff then occurred at the entrance to Homecoming. This included further effort towards the Gordian Knot from the first Homecoming trip, which concluded in Chi doing an Alexander the Great. We ended up with two ropes. Chi also spent <em> some </em> time reconstructing a pantin from two broken ones (it didn't work). Clearly one person was the issue here. *editorial note: it would transpire that Lara concluded faffing a good 20 mins after the futile pantin was birthed*
@@ -1176,10 +1175,10 @@ I forgot that Harry's water bottle was in the bottom of my bag, and may have sli
<p>
Harry and Charlotte slowed themselves down by doing some more Wallace fettling. Chi and I got out at the lovely hour of 3am and napped for the 15 minutes before they caught up. I got deja vu as we headed up to Garlic and immediately passed out. A very long, very fun day.
<div class="timeug">T/U: 15.0 hours</div>
<div class="editentry"><br /><a href="/logbookedit/2024-07-21c">Edit this entry</a><br /></div>
<div class="editentry"><br /><a href="/logbookedit/2024-07-21d">Edit this entry</a><br /></div>
<hr />
<div class="tripdate" id="2024-07-21d">2024-07-21</div>
<div class="tripdate" id="2024-07-21e">2024-07-21</div>
<div class="trippeople"><u>Becka</u>, Sieds</div>
<div class="triptitle">Homecoming 359 - Second Coming Re-rig</div>
A hot, heavy walk up from Base Camp saw Sieds and Becka underground at 14.30. At the short drop with a high rebelay before Wallace and Grommit Sieds had accidentally dropped a large, loose rock on his last trip. Unfortunately, he now realised that the huge rock next to this previous rock was also extremely loose. We were aware that there was already a trip below us in Homecoming but the other rock was extremely loose so I derigged the next rebelay and prussiked up to the high rebelay and held the rope out of the way. Sieds then gently pushed the giant rock and it immediately toppled. I then headed down cautiously. The rope initially looked fine but at the Y-hang rebelay for the final long hang the Y-hang arm had been cored and the knot also looked to be damaged. I painstakingly got the knot out and tied out as much as I could then we headed down, leaving a warning not for the other group.
@@ -1188,7 +1187,7 @@ We went to Second Coming and, at the first traverse, wondered why it was rigged
<p>
We got out of the cave at midnight and Sieds walked to Garlic camp and I walked to Top Camp with a full moon and no wind. I could see and hear Sieds as he approached Garlic when I was almost at Top Camp, it was so still and silent. It was nearly 2am before I got to Top Camp and I crept around making food trying not to disturb anyone - I didn't realise until the next morning that there was nobody else there.
<div class="timeug">T/U: 9.5 hours</div>
<div class="editentry"><br /><a href="/logbookedit/2024-07-21d">Edit this entry</a><br /></div>
<div class="editentry"><br /><a href="/logbookedit/2024-07-21e">Edit this entry</a><br /></div>
<hr />
<div class="tripdate" id="2024-07-22a">2024-07-22</div>