950.4 m surveyed this year.
Table of all trips and surveys aligned by date
|July 7, 1994||161||1623-161|
|July 10, 1994||161 - Driller Killer||1623-161||notwhat||notes tape||232.5 m|
|July 12, 1994||161 - Gnome||1623-161|
|July 14, 1994||161||1623-161|
|July 16, 1994||161 - Driller Killer||1623-161||vestaconn||inst tape notes||35.0 m|
|--||nightsoil||inst tape notes||238.5 m|
|July 19, 1994||161 - Ginger Crunch||1623-161||brownie||inst tape notes||86.7 m|
|--||ginger||inst notes tape||215.2 m|
|July 20, 1994||161 - Quest for the holy generator thingy||1623-161|
|July 21, 1994||161 - Push Exhaustion Pitch (Burble area) & survey||1623-161||siberia||inst tape notes||142.4 m|
|July 23, 1994||161 - Photo trip||1623-161|
|July 25, 1994||161 - Derigged from Knossus||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!