Wookey : 2000

506.1 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

Wallet status | 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 30, 2000 Loser Plateau - Surface wandering on Hinter Loser Plateau 96ones 0.0 m
-- 96ones 0.0 m
July 31, 2000 40 - Eishöhle - POV 40 eiscream2 15.5 m
-- eiscream2 15.5 m
-- 96ones2 0.0 m
-- 96ones2 0.0 m
Aug. 1, 2000 Loser Plateau - More surface stuff Loser Plateau 220 8.3 m
-- near205 0.0 m
-- near205 0.0 m
Aug. 2, 2000 40 - Eishöhle 40 eiscream3 29.0 m
-- eiscream3 29.0 m
-- missionconnection 6.0 m
-- missionconnection 6.0 m
Aug. 3, 2000 40 - Eishöhle bits and bobs 40 40h 49.1 m
-- 40h 49.1 m
Aug. 5, 2000 40 - Eishöhle - mission impossible 40 mission2 141.7 m
-- mission2 141.7 m
-- ent 4.7 m
-- ent 4.7 m
Aug. 6, 2000 40 - Eishöhle - Plus surface work 40 215 48.7 m
-- 215 48.7 m
-- wk2towk3 0.0 m
-- wk2towk3 0.0 m
Aug. 8, 2000 161 - 'The Connection trip' 161 161d 0.0 m
-- 161d 0.0 m
Aug. 9, 2000 Loser Plateau - - 170's Loser Plateau 172 20.9 m
-- 172 20.9 m
-- 250 10.2 m
-- 250 10.2 m
-- 250 10.2 m
-- 172to171a 0.0 m
-- 172to171a 0.0 m
Aug. 10, 2000 40 - Eishöhle: MI pushing 40 mission4 35.2 m
-- mission4 35.2 m
Aug. 11, 2000 40 - Eishöhle: MI pushing 40 163conn 0.0 m
-- 163conn 0.0 m
Aug. 12, 2000 modern 136.7 m
-- modern 136.7 m

Horrible convoluted bug here, but only for some survex files. Mostly, a survex block is duplicated. But not always.

e.g. see Wookey 1999 where there are one eiscream survex block on 5th August in eiscream.svx
It duplicates it. Also on 4th Aug. there is only one block, but it gets shown twice.

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!