0.0 m surveyed this year.
Table of all trips and surveys aligned by date
|July 13, 2018||plateau - Surface recce for Futility series back door||plateau|
|July 14, 2018||plateau -Surface walk Stoger Weg/115 (Schnellzughöhle) - actually cucc-ps01-2018||plateau -Surface walk Stoger Weg/115 (Schnellzughöhle)|
|July 18, 2018||plateau - Solo walking in area of 115 entrances [and CUCC-PS01-2018]||plateau|
|July 28, 2018||basecamp - network nerding||basecamp|
|July 29, 2018||plateau -Surface prospecting along "lookfutile.svx" route||UNKNOWN|
|July 30, 2018||base camp - "Receipt for expo members of VfHO for 2018"||base camp|
|Aug. 1, 2018||plateau - Solo walking in Stumern Alm area||plateau|
|Aug. 3, 2018||plateau - "Lookfutile3"||plateau|
|Aug. 4, 2018||base camp - Expo T-shirts arrived at Gasthof||base camp|
|Aug. 13, 2018||base camp - "Local contact: Dr. Helmut Kalss"||base camp|
|Aug. 19, 2018||115 - Schnellzughöhle||115|
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!