504.3 m surveyed this year.
Table of all trips and surveys aligned by date
|July 25, 2014||Team 2 into Tunnocks|
|July 27, 2014||258 - Tunnocks - Pidgeons in Flight -> Pidgeon Droppings||1623-258|
|July 28, 2014||withintheabove||inst notes||97.3 m|
|July 29, 2014||Within The Above|
|Aug. 1, 2014||Tunnocks - Rigging Coldfinger by Champagne on Ice||1623-258|
|Aug. 2, 2014||Tunnocks - Champagne on Ice||1623-258|
|Aug. 3, 2014||2014-888 and MF - unmarked pit|
|Aug. 4, 2014||Tunnocks - Ducks on Ice rigging + connecting||1623-258|
|Aug. 5, 2014||Prospecting N of Tunnocks|
|Aug. 6, 2014||258 Tunnocks - Champagne on Ice - connection trip to Arctic Angle||coldladyslegs1||notes inst dog||297.1 m|
|--||coldfinger3||notes inst dog||109.8 m|
|Aug. 19, 2014||Leads at the bottom of Champagne on Ice / Arctic Angle, Grike Expectation|
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!