643.6 m surveyed this year.
Table of all trips and surveys aligned by date
|July 16, 2005||Journey to Austria - Drive out||Journey to Austria|
|July 21, 2005||204 - Gaffered - Rigging||204|
|July 22, 2005||204 - More Gaffered rigging||204|
|July 23, 2005||204 - Cresta Run Push||204||highhopes||48.1 m|
|July 26, 2005||204 - Gaffered - Earthenware / Hardware||204||someware||161.3 m|
|July 27, 2005||beyondbelief||29.8 m|
|July 28, 2005||204 - Gaffered - Earthenware + Heavily Soiled||204||software||28.8 m|
|July 29, 2005||204 - On A Mission - Faith - Beyond Belief||204||beyondbelief2||110.4 m|
|July 31, 2005||204 - Gaffered - Heavily Soiled (again)||204||hippocratic2||184.7 m|
|Aug. 1, 2005||Loser Plateau - Surface documentation work||Loser Plateau|
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!