370.8 m surveyed this year.
Table of all trips and surveys aligned by date
|July 1, 1998||logic||148.4 m|
|July 4, 1998||bearbum||30.9 m|
|July 20, 1998||Loser Plateau - Looking for 40, Eishoehle||Loser Plateau|
|July 21, 1998||40 - Eishöhle - SVH||40|
|July 23, 1998||40 - Eishöhle - 'Connect to 136' trip||40|
|July 24, 1998||40 - Eishöhle - 'Connect to 136 mk II' trip||40||plastic||150.6 m|
|July 25, 1998||plastic2||41.0 m|
|July 27, 1998||40 - Eishöhle -"Connect to 136 mk III or derig" trip||40|
|July 28, 1998||Loser Plateau - Random stumblings||Loser Plateau|
|July 31, 1998||161 - Fuzzy logic - pushing the realms of uncertainty||161|
|Aug. 4, 1998||161 - Derig from Fuzzy Logic to Knossos||161|
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!