219.0 m surveyed this year.
Table of all trips and surveys aligned by date
|July 7, 2015||Gemsehöhle - 107|
|July 8, 2015||Gemsehöhle - 107|
|July 9, 2015||107|
|July 11, 2015||107|
|July 12, 2015||107/161|
|July 13, 2015||Balcony - Dark Arts||1623-264||darkartsvi||inst notes pics tape||14.8 m|
|--||darkartsvi||inst notes pics tape||14.8 m|
|July 16, 2015||Balkonhöhle - QMs in Far Side||1623-264|
|July 17, 2015||Balkonhöhle|
|July 18, 2015||Balcony Höhle - 59b|
|July 19, 2015||Balconyhöhle - 59b||pitch59b||inst tape notes||118.7 m|
|July 20, 2015||Balcony - 94a, 95a||1623-264||einundzwanzig||inst notes tape||85.5 m|
|--||einundzwanzig||inst notes tape||85.5 m|
|July 21, 2015||Balconyhöhle|
|--||Balconhöhle - Einundzwanzig leads (Ice cock)|
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!