389.1 m surveyed this year.
Table of all trips and surveys aligned by date
|July 14, 2004||204 - Ariston rigging||204|
|July 15, 2004||204 - 204E rigging||204|
|July 21, 2004||204 - Gaffered||204|
|July 22, 2004||Cave 2004-11 - In Your Face||Cave 2004-11||251||170.8 m|
|July 23, 2004||Cave 2004-11 - 204 - In Your Face + 204 scrotting||Cave 2004-11|
|July 30, 2004||234 - Hauchhöhle: How to knacker yourself in the least interesting way possible||234|
|Aug. 1, 2004||Loser Plateau - Surface prospecting near Hauchhöhle||Loser Plateau||2004-14||23.2 m|
|Aug. 2, 2004||204 - Loop closures + Cresta Run||204||insig2rhino||11.6 m|
|Aug. 3, 2004||204 - Razor Dance Derig||204|
|Aug. 4, 2004||Loser Plateau - Surface work near Hauchhöhle part 2||Loser Plateau|
|Aug. 6, 2004||Base Camp - Grabenbach Canyon||Base Camp|
|Aug. 9, 2004||gravity||35.8 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!