0.0 m surveyed this year.
Table of all trips and surveys aligned by date
|July 5, 1991||Pushing trip down Puffball||Pushing trip down Puffball|
|July 10, 1991||Puffball||Puffball|
|July 13, 1991||182totc||0.0 m|
|July 17, 1991||"survey" + "Pushing" trip down France||"survey" + "Pushing" trip down France|
|July 21, 1991||France rig, Survey||France rig, Survey|
|--||Continuation of France rig + survey||Continuation of France rig + survey|
|July 23, 1991||Knossus derig.||Knossus derig.|
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!