Wookey : 1999

1145.5 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 1, 1999 156tagconn 0.0 m
-- 01to201 0.0 m
-- 01to201 0.0 m
July 23, 1999 footconn 67.5 m
-- footconn 67.5 m
July 25, 1999 136 - 136 136 2 177.9 m
-- 2 177.9 m
July 26, 1999 136 - Carry on to check out the Overrun 136 1 204.5 m
-- 1 204.5 m
July 27, 1999 Base Camp - Hydrospeeding Hilde's River Base Camp
July 28, 1999 Loser Plateau - Assorted surface things Loser Plateau 138to135 0.0 m
-- 138to135 0.0 m
July 29, 1999 136 - More in Chile 136 breezeblock 190.7 m
-- breezeblock 190.7 m
July 30, 1999 Loser Plateau - Useful surface things Loser Plateau 199 86.1 m
-- Loser Plateau - Surface bumbling around 136 etc Loser Plateau
Aug. 1, 1999 40 - Go look in Eishöhle 40 deviant 91.2 m
-- deviant 91.2 m
Aug. 2, 1999 40 - Eishöhle 40 uuaway 60.1 m
-- uuaway 60.1 m
Aug. 3, 1999 209 0.0 m
-- 209 0.0 m
-- 136shelf 0.0 m
Aug. 4, 1999 40 - Eishöhle 40 dangle 139.8 m
-- dangle 139.8 m
Aug. 5, 1999 40 - Eishöhle 40 eiscream 127.5 m
-- eiscream 127.5 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!