256.8 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|
|July 9, 2019||plateau - reflect the route from Fish Face to top camp|
|July 10, 2019||plateau - tagging and surface bashing to Fishgesicht|
|July 11, 2019||plateau - back to Fischgesicht for more prospecting|
|--||base camp - CUCC Austria Expedition 2019 Blog|
|July 13, 2019||plateau - Fishface and prospecting|
|July 17, 2019||Homecoming - Blog Post Homecoming||1626-359|
|July 19, 2019||couldashouldawoulda_to_bathdodgersbypass||inst notes||155.5 m|
|July 20, 2019||wheresthemilk||inst dog notes||60.0 m|
|--||drunkdrivers||inst dog notes||23.5 m|
|--||custardcavalry||inst dog notes||17.8 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!