390.7 m surveyed this year.
Table of all trips and surveys aligned by date
|Aug. 4, 2010||Tunnocks - Checking horizontal leads||1623-258||atobtoc||inst notes||30.4 m|
|Aug. 5, 2010||Tunnocks - Stringfellows chamber and connecting to Usual Suspects||1623-258||stringtheory||inst notes||255.5 m|
|Aug. 6, 2010||Tunnocks - First photo trip||1623-258|
|Aug. 14, 2010||Tuncocks across usual suspects and goody goody||downtoearth2||inst notes||30.6 m|
|--||flyinghigh4||inst notes||10.4 m|
|--||flyinghigh5||inst notes||63.8 m|
|Aug. 15, 2010||Walk to Greiskogel eyehole|
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!