940.9 m surveyed this year.
Table of all trips and surveys aligned by date
|June 22, 2016|
|June 23, 2016|
|June 24, 2016||Balcony rigging - guide (start of 2016)||swingers||inst notes||19.0 m|
|June 26, 2016||Tunnocks - Procrastination||1623-258|
|June 27, 2016||Tunnocks|
|June 28, 2016||Tunnocks - entrance rerig||1623-258|
|June 30, 2016||Tunnocks (258)- Champagne on Ice (rigging)|
|July 1, 2016||Tunnocks - Champagne on Ice||1623-258|
|July 2, 2016||Balkonhöhle Rescue|
|July 3, 2016||Balcony - Haydon's pitch near gear dump||1623-264|
|July 4, 2016||Tunnocks, 2-night camp|
|July 5, 2016||slackers||inst notes dog inst notes notes dog dog||922.0 m|
|July 10, 2016||The Non Rescue - 1st Response Team|
|July 11, 2016||Prospecting North of Balcony|
|July 12, 2016||Tunnocks - Derigging and pushing Champagne on Ice||1623-258|
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!