0.0 m surveyed this year.
Table of all trips and surveys aligned by date
|July 25, 1983||travel - The journeys out.||travel|
|July 27, 1983||Wednesday||Wednesday|
|July 28, 1983||Thursday||Thursday|
|July 30, 1983||Sat 30th||Sat 30th|
|July 31, 1983||Sunday 143||Sunday 143|
|Aug. 1, 1983||144||144|
|Aug. 2, 1983||TUESDAY 2nd August||TUESDAY 2nd August|
|Aug. 3, 1983||146 - WEDNESDAY 3rd August||146|
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!