312.5 m surveyed this year.
Table of all trips and surveys aligned by date
|July 10, 2007||Top Camp - Djuke's Bedtime Story||Top Camp|
|July 12, 2007||Top Camp - It's raining - again||Top Camp|
|July 13, 2007||204 - Rigging Gaffered||204|
|July 14, 2007||204 - The Gaffered rebolting project||204||slimy1||26.6 m|
|July 19, 2007||204 - Slimy Sludge Chute||204|
|July 20, 2007||204 - Slimy Sludge Chute continued||204||slimy2||59.6 m|
|July 21, 2007||11sr||139.3 m|
|July 23, 2007||Surface Prospecting||UNKNOWN|
|July 24, 2007||204 - The Happy Hippocampus||204|
|July 25, 2007||Random leads in Insignificant||UNKNOWN||swisscheese||86.9 m|
|July 29, 2007||Climbing||UNKNOWN|
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!