Nadia Raeburn : 2017

163.2 m surveyed this year.

Other years:  | 2017 | 2018 | 2019

Wallet status | 2017 | 2018 | 2019

Table of all trips and surveys aligned by date

DateTripsSurveys
July 12, 2017 Balcony - rigging Hilti-a-plenty Balcony
July 21, 2017 Balcony - destroying Galactica Balcony
July 22, 2017 plateau - Prospecting plateau
July 23, 2017 plateau - Prospecting - Bad Forecast (2017-PW-01) found plateau
July 25, 2017 Tunnocks - Camp Kraken: Densham Master Cave, Grike of the Earth, Bullshit in a China Shop Tunnocks
July 26, 2017 mastercave 41.4 m
-- gryke-of-the-earth 121.8 m
July 28, 2017 plateau - Prospecting, 110 area plateau
July 30, 2017 Balcony - Sloppy Seconds Balcony
Aug. 1, 2017 CUCC-2017-28 - initial exploration CUCC-2017-28

Horrible bug here but only when there is more than one survex block per day, or is there ?!

WHat we thought was the bug: 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.

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!

What we now know

The eiscream.svx file does indeed record 3 blocks: eiscream, eiscream2 & eiscream3. But (more) careful inspection shows that eiscream2 and eiscream3 are in the year 2000, not in 1999. So they absolutely should not be shown here. So maybe everything is correct after all. (Well, apart from the duplication.)