Wookey : 2007

1034.9 m surveyed this year.

Other years: | 1988 | 1989 | 1990 | 1991 | 1992 | 1993 | 1995 | 1996 | 1998 | 1999 | 2000 | 2002 | 2005 | 2007 | 2009 | 2011 | 2012 | 2013 | 2014 | 2015 | 2016 | 2018

Table of all trips and surveys aligned by date

DateTripsSurveys
July 25, 2007 Trisselwand - the IVth Trisselwand
July 29, 2007 Via Ferrata - Loser Klettersteig Via Ferrata
July 30, 2007 204 - Gaffered -> The Wares -> Software 204 software3 29.8 m
-- software3 29.8 m
July 31, 2007 204 - Razordance -> push horizontal leads. Combined push, survey, photo + derig trip. Sigh. 204 crouching 131.0 m
Aug. 3, 2007 Razordance - Finish derigging Razordance
Aug. 4, 2007 Gösser Streamway - Rig push, survey, derig Gösser Streamway
Aug. 7, 2007 Walk to 204 via 161d UNKNOWN
Aug. 8, 2007 Photo, Rig, survey, push in Tunnocks UNKNOWN 2007-04 83.9 m
-- literalnorth2 25.6 m
-- literalnorth3 34.3 m
-- maxpleasure1 261.3 m
Aug. 9, 2007 More horizontal cave UNKNOWN maxpleasure2 469.0 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!