Noel Snape : 2014

1504.8 m surveyed this year.

Other years: | 2009 | 2011 | 2012 | 2014

Table of all trips and surveys aligned by date

DateTripsSurveys
Aug. 4, 2014 2005-05 Balcony Höhle UNKNOWN roomwithaview2 81.5 m
-- Tunnocks THE BEAST UNKNOWN smashcrashpassage 104.4 m
Aug. 5, 2014 2005-05 Balcony Höhle UNKNOWN entrancepitch2 61.8 m
-- entrancepitch2 61.8 m
-- entrancepitch2 61.8 m
-- pitpot 13.5 m
Aug. 7, 2014 2005-05 Balcony Höhle UNKNOWN pitpot2 73.6 m
-- Balcony Höhle: Traversing + dropping Pit Pot UNKNOWN
Aug. 8, 2014 107 - derig 107
Aug. 11, 2014 Tunnocks - Arctic Angle - "The wrong choice" Tunnocks thewrongchoice 141.3 m
-- nochoiceatall2 31.3 m
Aug. 13, 2014 Balcony Höhle Pushing minor leads near entrance pitch UNKNOWN roommop 10.8 m
-- crashmop 131.8 m
Aug. 14, 2014 Tunnocks - Number of the Beast Tunnocks
Aug. 17, 2014 Balcony - The Far Side Balcony farside 513.9 m
Aug. 18, 2014 Balcony Höhle, Turtlehead passage UNKNOWN turtlehead 340.8 m
-- turtlehead 340.8 m

Horrible bug here but only when there is more than one survex block per day, e.g. see Wookey 1999 where there are 3 eiscream survex blocks on 5th August. it duplicates the entry but gets it wrong. The length from the first block is displayed twice but there should be 3 rows: eiscream, eiscream2, eiscream3.

Fortunately it is just this display on this page which is wrong: no bad calculations get into the database.

The interaction of django database query idioms with django HTML templating language is a bit impenetrable here. I blame Aaron Curtis who was too fond of being clever with the Django templating system instead or writing it in python anyone could understand.
- The template is in troggle/templates/personexpedition.html
- The code is in function personexpedition() which calls get_person_chronology() in troggle/core/views/logbooks.py
- the connection between the two is made in the URL resolver in troggle/urls.py

To be fixed!