Stuart Walker : 2012

304.0 m surveyed this year.

Other years:  | 2011 | 2012 | 2013

Wallet status | 2011 | 2012 | 2013

Table of all trips and surveys aligned by date

DateTripsSurveys
Aug. 1, 2012 Döppelgemzehöle - 2012-JS1 Döppelgemzehöle
-- "Bullets second höle" 2011-01 UNKNOWN
-- Prospecting (2012-SW0x) UNKNOWN
Aug. 8, 2012 Tunnockschäfte - climb of the penguins Tunnockschäfte climbofthepenguins1 10.4 m
-- climbofthepenguins2 47.4 m
Aug. 15, 2012 204a UNKNOWN boulderchamber 11.9 m
-- boulderchamber_upper 61.4 m
Aug. 18, 2012 Strubklamm UNKNOWN
Aug. 20, 2012 slapperpinkpot 60.4 m
Aug. 21, 2012 234 - Hauchhöle - Slapper Pink 234
Aug. 23, 2012 youshouldhaveneverletmebegin 84.6 m
-- mercurialsuppository 27.8 m
Aug. 24, 2012 234 - Hauchhöle - 'Mercurial suppository' 234
Aug. 25, 2012 Tunnocks derig UNKNOWN

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