Martin Green : 2002

432.4 m surveyed this year.

Other years: | 2000 | 2001 | 2002 | 2003 | 2004 | 2005 | 2007 | 2009 | 2010 | 2011 | 2012 | 2013 | 2014 | 2015 | 2016

Table of all trips and surveys aligned by date

DateTripsSurveys
Aug. 17, 2002 204 - Tour of Steinbrücken 1623-204 upat45deg inst notes tape 58.0 m
-- tree2glory inst notes tape 44.6 m
-- tree2glory inst notes tape 44.6 m
Aug. 18, 2002 204 - Merry "Fucking" Go Round 1623-204 merrygoround inst notes tape 55.9 m
Aug. 22, 2002 204 - Plan Not Interesting 1623-204 not inst notes notes tape 50.6 m
-- not inst notes notes tape 50.6 m
-- not inst notes notes tape 50.6 m
Aug. 23, 2002 204 - Merry-Go-Round 1623-204 merrygoround3 inst notes tape 49.4 m
-- merrygoround3 inst notes tape 49.4 m
Aug. 24, 2002 204 - Merry-Go-Round 1623-204 merrygoround2 inst notes tape 57.1 m
-- merrygoround2 inst notes tape 57.1 m
Aug. 25, 2002 204 - Plan Not Interesting 1623-204 plan inst notes tape 77.1 m
-- plan inst notes tape 77.1 m
-- interesting inst notes tape 39.7 m
-- interesting inst notes tape 39.7 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.
- 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!