Becka Lawson : 2001

1128.3 m surveyed this year.

Other years: | 1987 | 1988 | 1989 | 1996 | 1997 | 1999 | 2000 | 2001 | 2003 | 2004 | 2005 | 2007 | 2008 | 2009 | 2010 | 2011 | 2012 | 2013 | 2014 | 2016 | 2017 | 2018 | 2019

Table of all trips and surveys aligned by date

DateTripsSurveys
Aug. 11, 2001 204 - Steinbrückenhöhle 204 crowningglory 213.1 m
Aug. 12, 2001 204 - Steinbrückenhöhle 204 sucker 128.6 m
Aug. 13, 2001 Loser Plateau - Surface Loser Plateau
Aug. 14, 2001 204 - 204 204 tree15c 10.8 m
-- tree15c 10.8 m
-- helterskelter 40.6 m
-- helterskelter 40.6 m
-- flopsy 36.9 m
-- flopsy 36.9 m
-- playground 56.4 m
Aug. 15, 2001 204 - 204 204 swings 278.7 m
Aug. 17, 2001 204 - 204B 204 swings2 56.4 m
-- swings3 22.4 m
-- swings4 57.1 m
Aug. 18, 2001 204 - 204B 204 swings5 13.4 m
-- swings6 38.2 m
-- swings7 5.9 m
-- swings8 25.9 m
Aug. 19, 2001 204 - 204B to 204D! 204 swings9 90.9 m
-- 204d 0.0 m
Aug. 20, 2001 Cave 2001-05 - GNDN (Goes Nowhere Does Nothing) Cave Cave 2001-05 243 52.8 m
-- 243 52.8 m
Aug. 21, 2001 204 - 204D 204

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!