234.2 m surveyed this year.
Table of all trips and surveys aligned by date
|July 23, 1999||195||44.2 m|
|July 25, 1999||161 - Novice KH Trip||161|
|July 26, 1999||161 - Pushing 96-25 in Iceland||161|
|July 28, 1999||Loser Plateau - Assorted surface things||Loser Plateau||1||0.0 m|
|July 29, 1999||2||18.3 m|
|July 30, 1999||136 - Far End of 136||136|
|July 31, 1999||Loser Plateau - Surface exploration around VSK||Loser Plateau|
|Aug. 1, 1999||147 - ReExplore and resurvey 147||147||147||74.0 m|
|Aug. 4, 1999||136 - Steinschlagschacht||136||left2route||71.8 m|
|Aug. 5, 1999||ariston1||26.0 m|
|Aug. 7, 1999||204 - Unclear if trip occurred||204|
|Aug. 9, 1999||204 - Steinbrückenhöhle||204|
|Aug. 10, 1999||136 - derigging in 136||136|
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!