199.2 m surveyed this year.
Table of all trips and surveys aligned by date
|July 21, 2004||Cave 2003-02 - (Blaudrachenschact)||248-2||inst notes tape||92.0 m|
|--||248-2||inst notes tape||92.0 m|
|--||251to204d||inst notes||0.0 m|
|July 22, 2004||Loser Plateau - Surface bash|
|July 30, 2004||Cave 2003-02 - bolting|
|July 31, 2004||Cave - Skinny Festerers|
|Aug. 1, 2004||Cave - Skinny Festerers|
|Aug. 4, 2004||Cave 2004-12 - Finish 2004-12|
|Aug. 5, 2004||Cave 2004-19 - pushing||254||inst notes||107.2 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!