207.0 m surveyed this year.
Table of all trips and surveys aligned by date
|July 28, 2013||258 Rigging||UNKNOWN|
|July 30, 2013||258 Rigging||UNKNOWN|
|July 31, 2013||258 Rigging and AT LAST some pushing||UNKNOWN||bringontheclowns||64.4 m|
|Aug. 2, 2013||258 Pushing Determination||UNKNOWN|
|Aug. 3, 2013||Ants In Pants||UNKNOWN|
|Aug. 4, 2013||Tunnocks â Procrastination â bolting the climb âBring on the Clownsâ||UNKNOWN||bringontheclowns2||32.4 m|
|Aug. 6, 2013||258 Tunnocks â The Number of the Beast||UNKNOWN||numberofthebeast||110.3 m|
|Aug. 7, 2013||String Theory Rigging Guide||UNKNOWN|
|Aug. 11, 2013||Surface Prospecting - Drafty hole area||Surface Prospecting|
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!