120.8 m surveyed this year.
Table of all trips and surveys aligned by date
|July 10, 1999||Journey - Journey|
|July 11, 1999||Loser Plateau - Carries|
|July 25, 1999||161 - REGURGITATION||1623-161|
|July 26, 1999||161 - Pushing 96-25 in Iceland||1623-161|
|July 27, 1999||Base Camp - Hydrospeeding Hilde's River|
|July 29, 1999||136 - Photo + push in 136||1623-136||breezethrough||inst notes tape||78.3 m|
|Aug. 1, 1999||40 - Go look in Eishöhle||1623-40||oldway||inst notes pics tape||42.5 m|
|Aug. 5, 1999||40 - Eishöhle||1623-40|
|Aug. 10, 1999||161 - 161D - Pushing Regurgitation (almost)||1623-161|
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.
- The template is in troggle/templates/personexpedition.html
- The code is in function personexpedition() which calls GetPersonChronology() in troggle/core/views_logbooks.py
- the connection between the two is made in the URL resolver in troggle/urls.py
To be fixed!