1514.9 m surveyed this year.
Table of all trips and surveys aligned by date
|June 29, 2016||Tunnocks - Set up Camp and Living the Dream||Tunnocks|
|June 30, 2016||livingthedream||319.5 m|
|July 4, 2016||Tunnocks, 2-night camp||UNKNOWN|
|July 5, 2016||slackers||922.0 m|
|July 11, 2016||Camp - Tunnocks master cave and unprecedented depth potential!||Camp||part1||123.8 m|
|July 12, 2016||part3||149.6 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.
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!