420.7 m surveyed this year.
Other years: | 2015 | 2019
Table of all trips and surveys aligned by date
|July 21, 2015||Balconhöhle - Einundzwanzig leads (Ice cock)||icecock||inst dog notes||57.4 m|
|July 23, 2015||cathedralchasm||inst notes pics tape||85.2 m|
|July 24, 2015||northhole||inst notes tape||59.6 m|
|July 27, 2015||Balcony - Beyond Thunderdome||1623-264|
|July 28, 2015||Balcony Höhle Frozen North||frozennorth2||inst tape notes||142.1 m|
|July 29, 2015||frozennorth3||inst notes tape||30.3 m|
|Aug. 1, 2015||258 - Pushing Clayton's Cock Up to Flash Hard (P70)||1623-258||flashhard||inst notes||21.3 m|
|Aug. 4, 2015||bipedalpassage5||inst notes pics tape||24.9 m|
|--||bipedalpassage5||inst notes pics tape||24.9 m|
|Aug. 9, 2015||258, Clayton's cockup,Flash Hard|
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!