641.1 m surveyed this year.
Table of all trips and surveys aligned by date
|Aug. 2, 2010||Tunnocks Rigging|
|Aug. 4, 2010||Tunnocks - String Theory||1623-258|
|Aug. 6, 2010||Tunnocks - Usual Suspects||1623-258||usualsuspects4||inst notes||106.6 m|
|--||usualsuspects5||inst notes||41.6 m|
|--||usualsuspects6||inst notes||68.1 m|
|Aug. 7, 2010||Tunnocks, Stone Monkey||fallempire||inst notes tape||24.9 m|
|Aug. 8, 2010||Tunnocks HL||sovein||inst notes notes||114.1 m|
|Aug. 9, 2010||Tunnocks - Usual suspects to Trident chamber, Phreas Interruptus||1623-258||trident||inst notes tape||87.1 m|
|Aug. 10, 2010||Tunnocks Usual suspects to Trident to Phreas Interruptus||hastespeed||inst notes||198.8 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!