Luke Stangroom : 2016

977.6 m surveyed this year.

Other years: | 2015 | 2016 | 2017 | 2018

Table of all trips and surveys aligned by date

DateTripsSurveys
June 27, 2016 Balkonhöhle - Bipedal 1623-264
June 28, 2016 Tunnocks - entrance rerig 1623-258 fatmanscoop inst notes bitch 42.6 m
June 29, 2016 Balkonhöhle - Dig Dug Pitch 1623-264
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 6, 2016 wrongway inst notes dog 97.2 m
July 7, 2016 Tunnocks Camp slackers6 inst notes pics dog 31.2 m
July 8, 2016 wrongcustard inst notes pics dog 50.5 m
-- slackers7 inst notes pics dog 40.6 m
-- lobsterpot inst notes pics dog 93.2 m
July 9, 2016 kippercock inst notes pics dog 135.3 m
-- indianropetrick inst notes pics 58.7 m
July 11, 2016 Balcony - Long Drop 1623-264
July 12, 2016 Balkon - Gosser Wager 1623-264
July 16, 2016 Tunnocks - Champagne on Ice 1623-258
-- Tunnocks - Champagne on Ice derig 1623-258
July 17, 2016 Hilti a Plenty - Pushing and Evening Breakthrough cant_stop_bat_country inst notes 182.6 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!