350.9 m surveyed this year.
Table of all trips and surveys aligned by date
|July 2, 2016||264 Balcony - Cathedral Chasm|
|July 7, 2016||Tunnocks Camp||slackers6||inst notes pics dog||31.2 m|
|July 8, 2016||wrongcustard||inst notes pics dog||50.5 m|
|--||slackers7||inst notes pics dog||40.6 m|
|--||lobsterpot||inst notes pics dog||93.2 m|
|July 9, 2016||kippercock||inst notes pics dog||135.3 m|
|July 19, 2016||Balcony - Cathedral Chasm||1623-264|
|July 20, 2016||Tunnocks derig, Upper Kraken to String Theory|
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!