0.0 m surveyed this year.
Table of all trips and surveys aligned by date
|July 16, 2018||Balkon - Cathedral Kazam - Wild Honeycomb shaft - The Hangman||1623-264|
|July 17, 2018||Balkon - Wild Honeycomb shaft - The Hangman - Hangman's Daughter - Tunnock's Connection||1623-264|
|July 19, 2018||Balkon - to Honeycomb -> Hangmans||1623-264|
|July 20, 2018||Balkonhöhle - to Hangmans -> Snailtrail. Rigging below Prangmans||1623-264|
|July 24, 2018||Balkon - toHangman's->Hangngman + Window in Hangman's -> Myopia||1623-264|
|July 26, 2018||Balkon - to Hangman's-> Myopia + Mongol Rally||1623-264|
|--||Balkon - to Mongol Rally||1623-264|
|July 27, 2018||Balkon - Hangman's-> Grand Prix + Tunnocks Connection to Antlermuza!||1623-264|
|Aug. 4, 2018||Balkon - to Grand Prix -> Camp Kraken -> Radio Silence + Scum of the Earth + Octopus Garden ->derig)||1623-264|
|Aug. 10, 2018||Balkon - Camping trip : Balkon||1623-264|
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!