351.1 m surveyed this year.
Table of all trips and surveys aligned by date
|July 29, 2007||Via Ferrata - Loser Klettersteig|
|July 30, 2007||204 - Gaffered -> The Wares -> Software||1623-204||software3||inst notes pics tape||29.8 m|
|--||software3||inst notes pics tape||29.8 m|
|July 31, 2007||204 - Razordance -> push horizontal leads. Combined push, survey, photo + derig trip. Sigh.||1623-204|
|Aug. 14, 2007||Maximum Pleasure survey in Tunnockschacht||literalnorth4||inst notes||38.8 m|
|--||maxpleasure5||inst notes||46.8 m|
|--||justforalaugh||inst notes||144.4 m|
|--||letsgetnaked||inst notes||91.2 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!