343.3 m surveyed this year.
Table of all trips and surveys aligned by date
|July 29, 2012||Holy Bondage||UNKNOWN|
|Aug. 1, 2012||Rigging 204||UNKNOWN|
|Aug. 2, 2012||Rigging King Carbide||UNKNOWN|
|Aug. 3, 2012||Rigging King Carbide||UNKNOWN|
|Aug. 4, 2012||UNKNOWN|
|Aug. 7, 2012||Pushing near Fat Cat||UNKNOWN||pussyriot||65.0 m|
|Aug. 10, 2012||Looking for BS17 (Organhöhle)||UNKNOWN|
|Aug. 15, 2012||Pushing leads in the north of Tunnocks||UNKNOWN|
|--||Inner Flap - Tunnocks||Inner Flap|
|Aug. 16, 2012||204 -> 161 -> pitch level of March of the Ents ("No sign of Sauron")||UNKNOWN|
|Aug. 20, 2012||204 -> 161, leads near Runnel Stone||UNKNOWN|
|Aug. 21, 2012||204 - 161, Runnel Stone area plus partial derig||204|
|Aug. 25, 2012||Tunnocks derig||UNKNOWN|
|Aug. 27, 2012||204 - Survey Pretzl Passage below Big Boulder Chamber + continue derig||204||pretzelpassage1||106.4 m|
|Aug. 28, 2012||204 - Final derig||204|
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.
I blame Aaron Curtis who was too fond of being clever with the Django templating system
instead or writing it in python anyone could understand.
- The template is in troggle/templates/personexpedition.html
- The code is in function personexpedition() which calls get_person_chronology() in troggle/core/views/logbooks.py
- the connection between the two is made in the URL resolver in troggle/urls.py
To be fixed!