442.9 m surveyed this year.
Table of all trips and surveys aligned by date
|July 22, 2009||204 - Merry Fucking Christmas||204|
|July 24, 2009||204 - Pussyprance, Caterwal||204||pussyprance2||80.7 m|
|July 25, 2009||204 - Pussy Prance, CatFlap, Cat Walk||204||catflap||159.2 m|
|July 26, 2009||204 - Pussyprance||204||paintedlady||30.6 m|
|July 29, 2009||204 - Pussy in Bolts||204|
|July 30, 2009||204 - Pus in bolts||204|
|July 31, 2009||204 - Snow Leopard||204||snowleopard||28.9 m|
|Aug. 3, 2009||204 - On the Prowl, Catwalk||204|
|Aug. 4, 2009||204 - Derigging||204|
|--||204 - Derigging||204|
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!