194.9 m surveyed this year.
Table of all trips and surveys aligned by date
|July 25, 2014||Team 2 into Tunnocks|
|July 29, 2014||107 - Gemshohle - Finalising Nipped Down rigging + Pushing lead in Southern China - "The Last TSA"||1623-107||1||notes inst dog||39.9 m|
|July 30, 2014||258 - Tunnocks - Sightseeing and C lead at the top of String Theory (09-44C)||1623-258||trireme||inst notes dog dog||25.7 m|
|Aug. 1, 2014||Surface prospecting, NW of Tunnocks|
|Aug. 2, 2014||Checking Ants in Your Pants for snow level|
|Aug. 3, 2014||2014-888 and MF - unmarked pit|
|Aug. 5, 2014||SRT practice|
|Aug. 7, 2014||2005-05 Balcony Höhle||lemonsnout||notes instrument||129.3 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!