92.7 m surveyed this year.
Other years: | 2018 | 2019
Table of all trips and surveys aligned by date
|July 10, 2018||264 - Balkonhoehle/ 1st rig||264|
|July 11, 2018||plateau - Prospecting past Fisch Gesicht, beyond the ski pole line||plateau|
|July 12, 2018||Tunnocksschacht/258 - String Theory to Procrastination Rig||Tunnocksschacht/258|
|July 15, 2018||Fisch Gesicht - Pushed to Toto and surveyed free attic frys and Urinal||Fisch Gesicht||freeattic_flys||92.7 m|
|--||Fisch Gesicht - Found Ulysses||Fisch Gesicht|
|July 18, 2018||Homecoming - Hobnob Hallway||Homecoming|
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!