825.9 m surveyed this year.
Table of all trips and surveys aligned by date
|Aug. 5, 2014||go down Champagne on Ice / Coldfinger in Tunnocks||coldfinger2||distox notes rigging||60.9 m|
|Aug. 6, 2014||Balcony Höhle: Room with a View|
|Aug. 7, 2014||Balcon Höhle - A Room With a View||leedsbypass||distox distox notes||283.1 m|
|Aug. 8, 2014||107 - derig||1623-107|
|Aug. 10, 2014||Room with a View Cave ~300m surveyed||amalgamation||distox nail notes||274.4 m|
|--||darkarts||distox nail notes||73.5 m|
|Aug. 11, 2014||Room with a View Cave - Leeds Bypass + Dark Arts||darkartsii||distox nail notes||57.9 m|
|--||darkartsi||distox nail notes||76.2 m|
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!