Martin Green : 2003

696.3 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
July 10, 2003 Journey , Packing and Journey to Austria
July 20, 2003 204 , 204E to Helter Skelter 1623-204
July 21, 2003 204 , 204E to survey Sandpit off Helter Skelter 1623-204 sandpit inst notes pics tape 178.6 m
-- sandpit inst notes pics tape 178.6 m
-- helterdig inst notes pics tape 17.6 m
-- helterdig inst notes pics tape 17.6 m
July 24, 2003 204 , Round Gaffered (Traverse + down) + Dutch Beauty squeeze 1623-204
July 25, 2003 trihang inst notes 91.0 m
July 26, 2003 110aday2 inst notes 10.0 m
-- upat45deg2 inst notes 7.8 m
-- onamission2 inst notes 5.7 m
July 27, 2003 246 inst notes tape 57.5 m
-- 246 inst notes tape 57.5 m
July 28, 2003 204 , On a Mission 1623-204 crimper inst notes 28.5 m
-- onamission3 inst notes 58.5 m
July 29, 2003 204 , Rigging + survey down Gaffered 1623-204 eeyore inst notes 18.5 m
-- poohstyx inst notes 67.5 m
-- sirens inst notes 30.0 m
July 30, 2003 Base Camp , Grabenbach Canyon
Aug. 4, 2003 Loser Plateau , The walk back from top camp without using a helicopter.
Aug. 5, 2003 dontstep inst notes 36.8 m
Aug. 6, 2003 204 , Kiwi Suit + Ariston derig 1623-204
Aug. 9, 2003 ermintrude inst notes tape 21.4 m
-- ermintrude inst notes tape 21.4 m
Aug. 10, 2003 faith inst notes tape 66.8 m
-- faith inst notes tape 66.8 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!