Luke Stangroom : 2018

1895.9 m surveyed this year.

Other years: | 2015 | 2016 | 2017 | 2018

Table of all trips and surveys aligned by date

DateTripsSurveys
July 16, 2018 Balkon - Cathedral Kazam - Wild Honeycomb shaft - The Hangman Balkon
July 19, 2018 Tunnocks -Setting up Camp Kraken (Tunnocks) UNKNOWN
-- Homecoming - shallow level Homecoming
July 24, 2018 toto_to_crystalcrumble 87.8 m
-- ulysses_to_colericchamber 50.6 m
July 25, 2018 2014-MS-14 - Driven East 2014-MS-14 driveneast 118.4 m
-- driveneast 118.4 m
July 26, 2018 Balkon - to Mongol Rally Balkon pitstop 588.0 m
July 27, 2018 catlitter 25.4 m
-- catlitter 25.4 m
-- safencomfortable 270.0 m
July 28, 2018 plateau - Surface plateau
Aug. 3, 2018 Balkon - Pitstop Balkon turnbacktime 133.8 m
-- turnbacktime 133.8 m
Aug. 8, 2018 ntdwyt 43.1 m
Aug. 9, 2018 onedirection 181.5 m
-- scoopyloopy 83.9 m
-- lbbeneaththeboulders 66.8 m
-- lbbeneaththeboulders 66.8 m
Aug. 10, 2018 Balkon - Camping trip : Balkon Balkon
Aug. 15, 2018 FGH - "FGH Derig" FGH pushderig 246.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. I blame Aaron Curtis who was too fond of being clever with the Django templating system instead or writing it in python anyone could understand.
- The template is in troggle/templates/personexpedition.html
- The code is in function personexpedition() which calls get_person_chronology() in troggle/core/views/logbooks.py
- the connection between the two is made in the URL resolver in troggle/urls.py

To be fixed!