138.5 m surveyed this year.
Table of all trips and surveys aligned by date
|Aug. 3, 1997||Journey - Swiss Alpinists arrive...|
|Aug. 4, 1997||161 - Lost World||1623-161|
|Aug. 5, 1997||136 - Steinschlagschacht||1623-136||distraction||inst notes pics tape||61.7 m|
|--||distraction||inst notes pics tape||61.7 m|
|Aug. 6, 1997||161 - Staudnwirt Palace||1623-161|
|Aug. 7, 1997||136 - Steinschlagschacht||1623-136|
|Aug. 10, 1997||136 - Footlights Traverse||1623-136|
|Aug. 12, 1997||136 - Footlights cont.||1623-136||footlights||inst notes pics tape||76.9 m|
|--||footlights||inst notes pics tape||76.9 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.
- 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!