Improving cave identification in logbook entries

This commit is contained in:
2025-03-02 00:37:07 +00:00
parent 16ea3fb05d
commit 7951a1626f
6 changed files with 309 additions and 446 deletions

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-03-01 22:03 using either the control panel webpage or when editing a logbook entry online
Exported on 2025-03-02 00:03 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>
@@ -227,7 +227,7 @@ As we weren't allowed to derig Wolfh&ouml;hle we went to look at Pete's new hole
<div class="tripdate" id="1984-08-04a">1984-08-04</div>
<div class="trippeople"><u>Mike Martin</u>, Andy Waddington</div>
<div class="triptitle">Surface - surveying</div>
<div class="triptitle">82 - surveying</div>
A sweaty walk up followed by survey starting at Wolfh&ouml;hle + then to 107. On return walk (trying to locate 82) Andy's credentials were caressed by a howling gale emitting from a pile of rocks which with a little modification became a cave entrance. Andy declined Pete's offer of a loan of a torch so I accepted on his behalf. Explored to ~60m length. Still continuing. <br /><br />Time underground &frac12; hour.
<div class="timeug">T/U: 0.0 hours</div>
<div class="editentry"><br /><a href="/logbookedit/1984-08-04a">Edit this entry</a><br /></div>