528.7 m surveyed this year.
Table of all trips and surveys aligned by date
|July 30, 2004||204 - Subsoil – Fat Worm Blows a Sparky||1623-204||fatworm||inst notes tape||96.0 m|
|July 31, 2004||204 - Subsoil||1623-204||heavilysoiled||inst notes tape||37.4 m|
|--||fatworm2||inst notes||111.4 m|
|Aug. 1, 2004||204 - Earthenware||1623-204||earthenware2||inst notes tape||159.8 m|
|--||earthenware3||inst notes tape||79.0 m|
|Aug. 4, 2004||Cave 2004-12 - Finish 2004-12||161h||instrument notes||45.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!