1010.4 m surveyed this year.
Table of all trips and surveys aligned by date
|July 15, 2000||Journey - Mark S, Martin fly to Expo||Journey|
|July 19, 2000||Base Camp - Piss up. Again.||Base Camp|
|July 21, 2000||204 -Steinbrückenhöhle.||204 -Steinbrückenhöhle.|
|July 23, 2000||40 - Eishole||40|
|July 24, 2000||traun||125.5 m|
|July 26, 2000||traun2||71.8 m|
|July 27, 2000||204 - 204||204||110_bidet_b||23.4 m|
|Aug. 2, 2000||pleasuredome||138.6 m|
|Aug. 8, 2000||loop22||21.3 m|
|Aug. 9, 2000||b4surf||0.0 m|
|Aug. 10, 2000||Loser Plateau - Surface Bashing||Loser Plateau||193||20.8 m|
|Aug. 14, 2000||204 - Steinbrückenhöhle||204||110_bidet||59.4 m|
|Aug. 15, 2000||nopainnogain||81.5 m|
|Aug. 16, 2000||204 - Steinbrückenhöhle - final trip||204||bonsai||18.4 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!