801.2 m surveyed this year.
Table of all trips and surveys aligned by date
|July 27, 1999||136 - 136 to Lost in Space||136||2||97.6 m|
|July 28, 1999||136 - push end towards Stellerweg||136|
|July 29, 1999||136 - More in Chile||136||breezeblock||190.7 m|
|July 30, 1999||Loser Plateau - Useful surface things||Loser Plateau||199||86.1 m|
|--||Loser Plateau - Surface bumbling around 136 etc||Loser Plateau||199||86.1 m|
|Aug. 1, 1999||40 - Go look in Eishöhle||40||deviant||91.2 m|
|Aug. 2, 1999||40 - Eishöhle||40||uuaway||60.1 m|
|Aug. 3, 1999||209||0.0 m|
|Aug. 4, 1999||40 - Eishöhle||40||dangle||139.8 m|
|Aug. 5, 1999||40 - Eishöhle||40|
|Aug. 7, 1999||136 - 139 to 136 and surface surveyed 147||136||morent||91.6 m|
|Aug. 8, 1999||136 - 136||136||aven||44.0 m|
|Aug. 9, 1999||sflink||0.0 m|
|Aug. 10, 1999||136 - derigging in 136||136|
|Aug. 11, 1999||90to94bis||0.0 m|
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!