Becka Lawson : 2016

1384.0 m surveyed this year.

Other years: | 1987 | 1988 | 1989 | 1996 | 1997 | 1999 | 2000 | 2001 | 2003 | 2004 | 2005 | 2007 | 2008 | 2009 | 2010 | 2011 | 2012 | 2013 | 2014 | 2016 | 2017 | 2018 | 2019

Table of all trips and surveys aligned by date

DateTripsSurveys
June 23, 2016 Walk over Grimming from Niederstuttern via Grimminghutte, Multerek + Grimmingsgipfel+ending at Kulm
June 25, 2016 Tunnocks - Rigging to start of String Theory 1623-258
June 27, 2016 Balkonhöhle
June 28, 2016 Balkon - Pitch of Bipedal 1623-264
June 30, 2016 Tunnocks (258)- Champagne on Ice (rigging)
July 1, 2016 Balkonhöhle 264 - Frozen North
July 2, 2016 Tunnocks - Champagne on Ice - Rigging Daft Choice beyond Straight Choice Exposed 1623-258 daftchoice inst notes point 245.6 m
July 3, 2016 Looking for 2nd Balkonhöhle entrance (dropping 2010-04)
July 5, 2016 Tunnocks - Champagne on Ice - Daft Choice 2 1623-258 daftchoice2 inst notes 36.4 m
-- daftchoice3 inst notes 29.3 m
July 6, 2016 Tunnocks - Kracken 1623-258 slackers2 inst notes varnish 185.5 m
-- slackers3 inst notes varnish 43.9 m
July 7, 2016 Balcony slackers4 inst notes pics tape 295.9 m
-- slackers4 inst notes pics tape 295.9 m
-- slackers4 inst notes pics tape 295.9 m
-- slackers5 inst notes varnish 443.2 m
July 11, 2016 Prospecting North of Balcony
July 12, 2016 Tunnocks - Derigging and pushing Champagne on Ice 1623-258 whatwouldyourmothersay inst notes varnish 104.2 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!