369.8 m surveyed this year.
Table of all trips and surveys aligned by date
|July 5, 2004||Journey - In Cambridge|
|July 19, 2004||204 - 204||1623-204||grater||inst notes tape||12.9 m|
|July 22, 2004||Cave 2004-11 - In Your Face|
|July 23, 2004||Cave 2004-11 - 204 - In Your Face + 204 scrotting|
|July 27, 2004||204 - Razor Dance||1623-204|
|Aug. 1, 2004||204 - Earthenware||1623-204||earthenware2||inst notes tape||159.8 m|
|--||earthenware3||inst notes tape||79.0 m|
|Aug. 2, 2004||204 - Loop closures + Cresta Run||1623-204|
|Aug. 4, 2004||204 - derigging continued||1623-204|
|Aug. 6, 2004||Base Camp - Grabenbach Canyon|
|Aug. 8, 2004||obese||inst notes||10.4 m|
|--||allroads||inst notes||71.9 m|
|Aug. 9, 2004||gravity||inst notes tape||35.8 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!