0.0 m surveyed this year.
Table of all trips and surveys aligned by date
|June 22, 2016||2007-71 Ngauruhoe|
|June 26, 2016||101 survey practice|
|June 27, 2016||2007-71 Ngauruhoe survey|
|June 28, 2016||2007-71, 15-02B|
|July 1, 2016||76 - Rigging Plugged Shaft||1623-76|
|July 3, 2016||76 - Keg Series||1623-76|
|July 5, 2016||76|
|July 7, 2016||76 - Keg Series||1623-76|
|July 8, 2016||171 survey|
|July 9, 2016||16-JB-01 Hohle der guten Hoffnung|
|July 10, 2016||171, near old top camp - surveying|
|July 16, 2016||2016-JB-01 Hopeless|
|July 18, 2016||16-JB-01 Dirty Snow|
|July 19, 2016||76 Derig|
|July 20, 2016||16-JB-01: Hohle der Guten Hoffnung|
|July 21, 2016||16-JB-01: Nervous Breakdown|
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!