Wookey : 2018
66.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
Table of all trips and surveys aligned by date
| Date | Trips | Surveys | |||
|---|---|---|---|---|---|
| July 1, 2018 | plateau - Eiskelle - Surface Prospecting | plateau | |||
| Aug. 2, 2018 | Tunnocks - testing to Balkonhöhle Connection - Part One | Tunnocks | |||
| Aug. 3, 2018 | Tunnocks - testing to Balkonhöhle Connection - Part Two | Tunnocks | |||
| Aug. 7, 2018 | FGH - try to connect to HB | FGH | gardeningschool | 66.1 m | |
| Aug. 8, 2018 | Tunnocks - Resurvey trip down Tunnocks - 1 | Tunnocks | |||
| -- | Tunnocks - Resurvey trip down Tunnocks - 2 | Tunnocks | |||
| Aug. 9, 2018 | Eiskeller - Revisiting 2004-18 | Eiskeller | |||
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!