155.5 m surveyed this year.
Other years: | 2018 | 2019
Table of all trips and surveys aligned by date
|July 7, 2019||plateau - Discovery of Snow-filled Steinbruckhohle||plateau|
|July 11, 2019||base camp - CUCC Austria Expedition 2019 Blog||base camp|
|July 15, 2019||Homecoming - Blog Post bit||Homecoming|
|July 19, 2019||Homecoming - Blog Post bit, Propane Nightmares||Homecoming||couldashouldawoulda_to_bathdodgersbypass||155.5 m|
|July 21, 2019||264 - Derig below Littleboy camp to Pitstop||264|
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!