786.6 m surveyed this year.
Table of all trips and surveys aligned by date
|Aug. 3, 2009||["Tunnock's", 'Alphabet Soup']||cleadjackpot||inst dog notes||46.4 m|
|--||alphabetsoup||inst dog notes||30.8 m|
|Aug. 4, 2009||["Tunnock's", 'Goody Goody']||goodygoody||inst dog notes||356.6 m|
|Aug. 5, 2009||["Tunnock's", 'Frankly Freezing']||franklyfreezing2||inst notes||91.7 m|
|Aug. 7, 2009||['KH', '3 Wise Men re-rig and beyond']||1623-161|
|Aug. 8, 2009||['KH', 'East Anglia, Grimes Graves']||1623-161|
|Aug. 9, 2009||['KH', 'East Anglia']||1623-161||naturalway||inst notes disto||261.0 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!