Sandeep Mavadia : 2006

252.5 m surveyed this year.

Other years:  | 2006

Wallet status | 2006

Table of all trips and surveys aligned by date

DateTripsSurveys
July 23, 2006 Loser Plateau - Failed Attempt on Bivi Loser Plateau
July 24, 2006 204 - Stuff in Near End 204
-- 204 - Death and Glory 204
July 25, 2006 204 - Death and Glory 204 deathglory 51.7 m
-- Loser Plateau - Surface Wander Loser Plateau
July 26, 2006 204 - Bolting in Riverdance 204
July 27, 2006 204 - Surveying in Riverdance 204 riverdance3 58.6 m
-- fingerbang 18.7 m
Aug. 7, 2006 Surface bimble UNKNOWN
Aug. 8, 2006 2006-08 12.1 m
-- 2006-08 12.1 m
-- 231to2006-08 0.0 m
Aug. 9, 2006 sauerkraut 23.6 m
Aug. 10, 2006 Sauerkraut UNKNOWN skrautlink 0.7 m
-- gknodel 87.1 m
Aug. 11, 2006 2002-07 UNKNOWN
Aug. 14, 2006 204 Bivvi de-rig 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.)