495.6 m surveyed this year.
Table of all trips and surveys aligned by date
|July 29, 2014||Rig 161g||UNKNOWN|
|July 30, 2014||161 - Reconnaisance trip to Runnel Stone||161|
|Aug. 1, 2014||Surface prospecting, NW of Tunnocks||UNKNOWN|
|Aug. 2, 2014||107 - Gemshohle - Attempt #2 to push Wookey & Jess' lead at North end of China||107||161connection||55.0 m|
|Aug. 3, 2014||107 - KH connection made / KH derig||107|
|Aug. 11, 2014||Tunnocks - Arctic Angle - "The wrong choice"||Tunnocks||nochoiceatall||80.8 m|
|Aug. 12, 2014||deadbatpitch||32.2 m|
|Aug. 13, 2014||Balcony Höhle Pushing minor leads near entrance pitch||UNKNOWN||roommop||10.8 m|
|Aug. 14, 2014||Tunnocks - Number of the Beast||Tunnocks|
|Aug. 18, 2014||Balcony - Tying up loose ends in Far Side||Balcony||farsideco1||15.5 m|
|Aug. 19, 2014||Leads at the bottom of Champagne on Ice / Arctic Angle, Grike Expectation||UNKNOWN|
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.
I blame Aaron Curtis who was too fond of being clever with the Django templating system
instead or writing it in python anyone could understand.
- The template is in troggle/templates/personexpedition.html
- The code is in function personexpedition() which calls get_person_chronology() in troggle/core/views/logbooks.py
- the connection between the two is made in the URL resolver in troggle/urls.py
To be fixed!