502.5 m surveyed this year.
Table of all trips and surveys aligned by date
|Aug. 2, 2010||Tunnocks Rigging|
|Aug. 4, 2010||Tunnocks - Checking horizontal leads||1623-258|
|Aug. 5, 2010||Tunnocks - Stringfellows chamber and connecting to Usual Suspects||1623-258|
|Aug. 6, 2010||Tunnocks - Stringfellows||1623-258||konigsbergpassage||inst notes||170.2 m|
|Aug. 9, 2010||konigsberg2||inst notes||70.2 m|
|Aug. 10, 2010||konigsberg3||inst notes||95.3 m|
|Aug. 13, 2010||Tunnocks||konigsberg4||inst notes||82.7 m|
|--||konigsberg5||inst notes||84.0 m|
|Aug. 14, 2010|
|Aug. 15, 2010||Tunnocks|
|Aug. 16, 2010||Ice Flow Tunnocks|
|Aug. 17, 2010||Usual Suspects - Rampart|
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!