642.1 m surveyed this year.
Table of all trips and surveys aligned by date
|July 10, 2015||Tunnocks Entrance Rig|
|July 11, 2015||Tunnocks Entrance De-ice|
|July 14, 2015||Tunnocks Rigging ctd.|
|July 16, 2015||Team Fiasco go surface prospecting|
|July 17, 2015||More Tunnocks rigging|
|July 18, 2015||Balcony Höhle - 59b|
|July 20, 2015||Tunnocks, complete rig to pushing front below Number of the Beast|
|July 22, 2015||Tunnocks - pushing below Number of the Beast||1623-258||inferno||inst notes||204.9 m|
|July 27, 2015||Tunnocks - pushing Kraken||1623-258|
|July 29, 2015||Tunnocks - Pushing Kraken (again)||1623-258||kraken||inst notes||181.4 m|
|Aug. 3, 2015||Tunnocks - Kraken H/L to Anthemusa||1623-258||anthemusa||inst notes pics||182.3 m|
|Aug. 5, 2015||Tunnocks, Kraken Lower||tentacle||inst notes pics tape||73.5 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!