326.1 m surveyed this year.
Table of all trips and surveys aligned by date
|Aug. 9, 2010||2010-06||inst notes||10.6 m|
|--||2010-06||inst notes||10.6 m|
|Aug. 13, 2010||2010-07||inst notes||45.7 m|
|--||2010-07||inst notes||45.7 m|
|Aug. 16, 2010||Ice Flow Tunnocks||gawbypass||inst notes||37.9 m|
|--||iceflow||inst notes||149.5 m|
|Aug. 17, 2010||Usual Suspects - Rampart||rampant||inst notes||82.4 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!