67.8 m surveyed this year.
Table of all trips and surveys aligned by date
|July 28, 2002||Journey - + 1/2 Ton of Expo gear go to Austria in a van||Journey|
|Aug. 2, 2002||Cave 2002-01 - 234 - Artischockehöhle (2002-01) + Hauchhöhle (2001-09)||Cave 2002-01|
|Aug. 3, 2002||249||67.8 m|
|Aug. 14, 2002||Loser Plateau - 40 - Surface work near Eishöhle||Loser Plateau|
|Aug. 17, 2002||40 - Eishöhle, checking out passages behind 40A bivvy||40|
|--||Loser Plateau - Surface work||Loser Plateau|
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!