Katey Bender : 2014

256.9 m surveyed this year.

Other years:  | 2014 | 2016 | 2017

Wallet status | 2014 | 2016 | 2017

Table of all trips and surveys aligned by date

DateTripsSurveys
July 28, 2014 258 - Tunnocks -> Pidgeon Droppings -> Flying Rat 258
July 29, 2014 Prospecting ~NE of Tunnocks UNKNOWN horizontalentrance 58.8 m
July 30, 2014 258 - Tunnocks - Sightseeing and C lead at the top of String Theory (09-44C) 258 trireme 25.7 m
Aug. 1, 2014 2005-05 UNKNOWN entrancepitch1 21.1 m
-- entrancepitch1 21.1 m
-- entrancepitch1 21.1 m
Aug. 2, 2014 2005-05 UNKNOWN
Aug. 3, 2014 2005-05 UNKNOWN roomwithaview 56.3 m
-- roomwithaview 56.3 m
Aug. 4, 2014 2005-05 Balcony Höhle UNKNOWN roomwithaview2 81.5 m
Aug. 5, 2014 2005-05 Balcony Höhle UNKNOWN pitpot 13.5 m
-- pitpot 13.5 m

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.)