417.7 m surveyed this year.
Table of all trips and surveys aligned by date
|July 16, 2006||Loser Plateau - Carrying lots of Stuff||Loser Plateau|
|July 18, 2006||Loser Plateau - More carrying lots of stuff||Loser Plateau|
|July 19, 2006||204 - Carrying + first push of expo||204||stageleft||21.6 m|
|July 20, 2006||204 - Random Pitch Series in Great Oak||204||greatoak2||14.8 m|
|July 21, 2006||204 - More Pitches in Great Oak + Cave Tree||204||goesser||52.5 m|
|--||204 - Gösser Streamway||204||goesser||52.5 m|
|July 22, 2006||More surface stuff||UNKNOWN|
|July 23, 2006||1||42.0 m|
|July 24, 2006||Tunnocks Trips||UNKNOWN|
|July 26, 2006||2||163.2 m|
|Aug. 1, 2006||204 Tourist trip||UNKNOWN|
|Aug. 2, 2006||234 Monster Munch||UNKNOWN||monstermunch||79.5 m|
Horrible bug here but only when there is more than one survex block per day, 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.
Fortunately it is just this display on this page which is wrong: no bad calculations get into the database.
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!