749.2 m surveyed this year.
Table of all trips and surveys aligned by date
|July 12, 1996||Driving to Austria||Driving to Austria|
|July 13, 1996||Trip to climb pitch in bugger||Trip to climb pitch in bugger|
|July 14, 1996||Surveying in bugger||Surveying in bugger|
|July 17, 1996||Surveying in Henri's Cat - 161d||Surveying in Henri's Cat|
|July 18, 1996||Trying to avoid 'Stairway to Hell' Part 1||Trying to avoid 'Stairway to Hell' Part 1||palace||74.1 m|
|July 22, 1996||Go to the Forbidden Land||Go to the Forbidden Land||hotmc||333.2 m|
|July 24, 1996||Photo trip - 161d||Photo trip|
|July 25, 1996||Forbidden Land||Forbidden Land||elina||309.5 m|
|July 28, 1996||To the Forbidden Land again||To the Forbidden Land again||tyrolia||32.3 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!