577.2 m surveyed this year.
Table of all trips and surveys aligned by date
|July 21, 1999||Journey - Anthony + Julia make it to expo||Journey|
|July 24, 1999||161 - Iceland||161|
|July 25, 1999||Loser Plateau - Surface stroll||Loser Plateau|
|July 26, 1999||161 - Pushing 96-25 in Iceland||161|
|July 30, 1999||161 - Survey "Frozen Turkey" (pitch off Iceland)||161||turkey||62.0 m|
|Aug. 1, 1999||204 - Steinbrückenhöhle||204|
|Aug. 4, 1999||204 - Steinbrückenhöhle||204||junction||42.6 m|
|Aug. 5, 1999||204 - Steinbrückenhöhle||204||phreatic||25.7 m|
|Aug. 7, 1999||196||30.2 m|
|Aug. 8, 1999||204 - 204||204||millennium||219.1 m|
|Aug. 10, 1999||204 - Steinbrückenhöhle||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!