100.8 m surveyed this year.
Other years: | 2017 | 2018
Table of all trips and surveys aligned by date
|July 19, 2018||Balkon - to Honeycomb -> Hangmans||Balkon|
|July 20, 2018||Fischgesicht - Surveying near Ulysses||Fischgesicht|
|July 21, 2018||ulysses_to_toto||100.8 m|
|July 24, 2018||2018-ad-02 - Prospecting and checking out the new bivi cave (Garlic Cave 2018-ad-02)||2018-ad-02|
|July 25, 2018||2018-ad-02 - More prospecting and bivi cave fettling (Garlic Cave 2018-ad-02)||2018-ad-02|
|July 26, 2018||base camp - Festering at base camp||base camp|
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!