223.3 m surveyed this year.
Table of all trips and surveys aligned by date
|July 28, 2002||Journey - + 1/2 Ton of Expo gear go to Austria in a van|
|Aug. 9, 2002||204 - Steinbrücken||1623-204|
|Aug. 23, 2002||204 - Merry-Go-Round||1623-204||merrygoround3||inst notes tape||49.4 m|
|Aug. 24, 2002||204 - Merry-Go-Round||1623-204||merrygoround2||inst notes tape||57.1 m|
|Aug. 25, 2002||204 - Plan Not Interesting||1623-204||plan||inst notes tape||77.1 m|
|--||interesting||inst notes tape||39.7 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!