Olly Betts : 2004

1231.6 m surveyed this year.

Other years: | 1990 | 1991 | 1992 | 1994 | 1996 | 1999 | 2000 | 2001 | 2002 | 2004 | 2005 | 2006 | 2007 | 2012 | 2013 | 2015 | 2016

Table of all trips and surveys aligned by date

DateTripsSurveys
July 12, 2004 Loser Plateau - Carry up Loser Plateau
July 13, 2004 Loser Plateau - Set up Loser Plateau
July 14, 2004 76 - 76 76
July 16, 2004 76 - 76 76
July 17, 2004 76 - 76 76 entrance 26.8 m
-- entrance 26.8 m
July 18, 2004 76 - 76 76 bitter 22.9 m
-- bitter 22.9 m
-- bent 24.1 m
-- bent 24.1 m
July 19, 2004 76 - Brave New World 76 brave 133.2 m
-- brave 133.2 m
July 21, 2004 99 - 99 99
July 22, 2004 76 - 76 76 lovers 27.7 m
July 24, 2004 76 - Eislufthöhle - rigging down 70's route to Keg Series 76 saved 107.0 m
July 25, 2004 76 - Brave New World 76 brave2 127.0 m
July 26, 2004 76 - Brave New World 76 brave3 38.4 m
-- brave4 51.4 m
-- brave5 18.4 m
July 27, 2004 76 - Brave New World 76 brave6 12.7 m
-- brave7 27.8 m
-- brave8 45.6 m
July 29, 2004 76 - 76 and surface shaft 76
July 30, 2004 76 - Keg Series 76 keg 124.5 m
July 31, 2004 Loser Plateau - Surface stuff Loser Plateau
Aug. 1, 2004 76 - to the Tap Room 76 tap 68.0 m
Aug. 3, 2004 76 - Brave New World 76 rift 84.5 m
-- noways 122.6 m
-- boiling 76.5 m
Aug. 4, 2004 76 - Brave New World pitch series 76 pitch 92.4 m
Aug. 5, 2004 Cave 108 - Cave 2004-02 - Descending "108" and 2004-02 Cave 108

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!