1181.9 m surveyed this year.
Other years: | 2016 | 2017
Table of all trips and surveys aligned by date
|June 22, 2016|
|June 23, 2016|
|June 26, 2016||BalkonH - Gosser Wager|
|July 2, 2016||Balkonhöhle|
|July 3, 2016||Balcony - Fetching Drills||1623-264|
|July 11, 2016||Balcony - Long Drop||1623-264|
|July 17, 2016||cathedralchasm2||inst notes tape||484.5 m|
|July 18, 2016||Long Drop - final push, survey & Derig||longdrop2||inst notes tape||232.0 m|
|July 19, 2016||Balcony - Cathedral Chasm||1623-264|
|July 24, 2016||Balcony - Hilti-a-Plenty - Galactica||1623-264|
|July 25, 2016||hiltigalactica||inst notes tape||465.4 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.
- 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!