Richard Mundy : 2007

677.6 m surveyed this year.

Other years: | 2007

Table of all trips and surveys aligned by date

DateTripsSurveys
July 10, 2007 204 - Rigging Entrance to 204-E 204
July 13, 2007 204 - Rhino Rift 204 shanks 154.2 m
-- spittersend 40.3 m
July 14, 2007 204 - Rhino Rift 204 nonconformism 26.3 m
July 16, 2007 204 - Underworld 204 dangerous 96.5 m
July 19, 2007 Surface Prospecting - Surface messing Surface Prospecting
-- 204 - The 11 second rattle story 204
July 20, 2007 204 - Slimy Sludge Chute continued 204 slimy2 59.6 m
-- slimy2 59.6 m
-- slimy2 59.6 m
July 21, 2007 11sr 139.3 m
July 23, 2007 204 - 11 Second Rattle 204
July 25, 2007 204 - Upper levels of 204e 204 wetdry 42.2 m
Aug. 3, 2007 'Quest to BS17' UNKNOWN
-- Top Camp - VERMIN Top Camp
Aug. 4, 2007 'Lead 03-75A' UNKNOWN hollow 35.3 m
Aug. 5, 2007 Chocolate Salty Balls UNKNOWN
-- CSB Thermistor & Treeumphant UNKNOWN
Aug. 8, 2007 'Slippery Hole' UNKNOWN 2007-04 83.9 m
-- 2007-04 83.9 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!