421.4 m surveyed this year.
Table of all trips and surveys aligned by date
|June 23, 2016||Walk over Grimming from Niederstuttern via Grimminghutte, Multerek + Grimmingsgipfel+ending at Kulm||UNKNOWN|
|June 27, 2016||Balkonhöhle||UNKNOWN|
|June 28, 2016||Balkon - Pitch of Bipedal||Balkon|
|June 30, 2016||Tunnocks (258)- Champagne on Ice (rigging)||UNKNOWN|
|July 1, 2016||Balkonhöhle 264 - Frozen North||Balkonhöhle 264|
|July 2, 2016||Tunnocks - Champagne on Ice - Rigging Daft Choice beyond Straight Choice Exposed||Tunnocks||daftchoice||245.6 m|
|July 3, 2016||Looking for 2nd Balkonhöhle entrance (dropping 2010-04)||UNKNOWN|
|July 5, 2016||Balcony - Frozen North||Balcony||snowhole||78.6 m|
|July 6, 2016||wrongway||97.2 m|
|July 7, 2016||Balcony||UNKNOWN|
|July 11, 2016||Balcony - Gosser, Wager||Balcony|
|--||Balcony - Hilti-a-Plenty "Roundabout.svx"||Balcony|
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!