Olly Betts : 2002

135.8 m surveyed this year.

Other years: | 1990 | 1991 | 1992 | 1994 | 1996 | 1999 | 2000 | 2001 | 2002 | 2004 | 2005 | 2006 | 2007 | 2012 | 2013 | 2015 | 2016

Table of all trips and surveys aligned by date

DateTripsSurveys
July 30, 2002 Loser Plateau - Gear carrying
July 31, 2002 Loser Plateau - Loser Plateau
Aug. 1, 2002 40 - Loser Plateau - Surface work near portal row 1623-40
Aug. 2, 2002 40 - Eishöhle, Mission Impossible 1623-40
Aug. 4, 2002 40 - Eishöhle, Mission Impossible 1623-40
Aug. 5, 2002 Loser Plateau - Surface investigations in Eishöhle area 2002-w-02 instrument notes 28.1 m
-- 2002-w-02surf instrument notes 0.0 m
Aug. 6, 2002 Loser Plateau - Back on surface
Aug. 8, 2002 40 - Eishöhle 1623-40
Aug. 9, 2002 238 instrument notes 60.2 m
Aug. 10, 2002 40 - SVH tourist 1623-40
Aug. 11, 2002 mission10 inst notes pics tape 47.5 m
-- mission10 inst notes pics tape 47.5 m
Aug. 14, 2002 Loser Plateau - 40 - Surface work near Eishöhle
Aug. 16, 2002 Loser Plateau - Surface work near Eishöhle
Aug. 17, 2002 40 - Eishöhle, checking out passages behind 40A bivvy 1623-40
-- Loser Plateau - Surface work
Aug. 18, 2002 Loser Plateau - Surface work near Eishöhle
Aug. 21, 2002 40 - Try to reach "Window of Opportunity" + derig Mission Impossible 1623-40
Aug. 22, 2002 40 - Eishöhle, Window of Opportunity 1623-40
Aug. 23, 2002 Loser Plateau - 40 - Prospecting on walk up to Eishöhle + SVH tourist trip

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.
- The template is in troggle/templates/personexpedition.html
- The code is in function personexpedition() which calls GetPersonChronology() in troggle/core/views_logbooks.py
- the connection between the two is made in the URL resolver in troggle/urls.py

To be fixed!