Fleur Loveridge : 2014

930.3 m surveyed this year.

Other years:  | 2013 | 2014 | 2015 | 2016 | 2017 | 2019

Wallet status | 2013 | 2014 | 2015 | 2016 | 2017 | 2019

Table of all trips and surveys aligned by date

Aug. 5, 2014 go down Champagne on Ice / Coldfinger in Tunnocks UNKNOWN coldfinger2 60.9 m
Aug. 6, 2014 Balcony Höhle: Room with a View UNKNOWN
Aug. 7, 2014 Balcon Höhle - A Room With a View Balcon Höhle leedsbypass 283.1 m
-- Balcony Höhle UNKNOWN
Aug. 8, 2014 107 - derig 107
Aug. 10, 2014 Room with a View Cave ~300m surveyed UNKNOWN amalgamation 274.4 m
-- darkarts 73.5 m
Aug. 11, 2014 Room with a View Cave - Leeds Bypass + Dark Arts Room with a View Cave darkartsii 57.9 m
-- darkartsi 76.2 m
-- leedsbypass2 104.4 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.)