215.3 m surveyed this year.
Table of all trips and surveys aligned by date
|July 7, 2007||Anthony's journey out|
|July 11, 2007||115 - MarkD & Anthony install a radon detector in 115||1623-115|
|July 13, 2007||204 - Kiwi Suit Rig||1623-204|
|July 14, 2007||Surface Prospecting - northwest of 204e|
|July 15, 2007||204 - Razordance Rig||1623-204|
|July 18, 2007||204 - Razordance||1623-204||razor10||inst notes||113.2 m|
|July 19, 2007||Surface Prospecting - Useful Walkies|
|July 22, 2007||204 - Razor Dance||1623-204||razor12||inst notes||102.1 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!