893.9 m surveyed this year.
Table of all trips and surveys aligned by date
|Aug. 7, 2007||Gaffered -> Inconvenience Series|
|Aug. 8, 2007||Surface shafts|
|Aug. 11, 2007||Gaffered -> The Wares + Derig||whereoware||inst notes tape||214.1 m|
|Aug. 12, 2007||Gaffered derig + Thermistors||stonemonkey||inst notes tape||129.7 m|
|--||Tunnockschacht -> Stone Monkey|
|Aug. 13, 2007||Maximum Pleasure leads in Tunnockschacht||maxpleasure3||inst notes notes inst||397.4 m|
|--||maxpleasure3||inst notes notes inst||397.4 m|
|--||maxpleasure4||inst notes||13.1 m|
|Aug. 14, 2007||stonemonkey2||inst notes||58.4 m|
|--||maxpleasure6||inst notes||29.4 m|
|--||justforalaugh2||inst notes||51.8 m|
|Aug. 15, 2007||Packing Steinbruckenhoehle Bivvy|
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!