Djuke Veldhuis : 2008

666.5 m surveyed this year.

Other years:  | 2007 | 2008 | 2011

Wallet status | 2007 | 2008 | 2011

Table of all trips and surveys aligned by date

DateTripsSurveys
July 18, 2008 The Van limps to Austria Journey to Austria
July 24, 2008 High hopes pushing 204 ubantu2 33.6 m
-- ubantu2 33.6 m
July 28, 2008 Ubantu 204 ubantu3 58.7 m
-- ubantu3 58.7 m
-- ubantu4 84.5 m
-- ubantu4 84.5 m
July 29, 2008 High hopes 204 05-9cqmkilling 14.3 m
July 30, 2008 High hopes 204 ubantu5 26.9 m
-- ubantu5 26.9 m
Aug. 2, 2008 derig Hauchhole lastchancesaloon 118.4 m
Aug. 3, 2008 Stone Monkey Tunnocks stonemonkey3 118.6 m
-- bouldersurfer 129.7 m
Aug. 4, 2008 Stone monkey Tunnocks stonemonkey4 82.0 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.)