150.6 m surveyed this year.
Table of all trips and surveys aligned by date
|Jan. 1, 1998||vordto156||inst notes pics||0.0 m|
|--||vordto156||inst notes pics||0.0 m|
|July 1, 1998||pitofdamnation||inst notes tape inst notes tape||0.0 m|
|July 15, 1998||Journey - Wook drives to Expo|
|July 17, 1998||Loser plateau|
|July 18, 1998||Loser Plateau - Surveyed from 90 to 91, 159*, 93 & 94||90to94||inst notes pics tape||0.0 m|
|--||90to94||inst notes pics tape||0.0 m|
|July 19, 1998||Lost Rucksack Hole - Lost Rucksack Hole|
|July 20, 1998||Lost Rucksack Cave - Lost Rucksack höhle|
|July 21, 1998||40 - Eishöhle - SVH||1623-40|
|July 23, 1998||40 - Eishöhle - 'Connect to 136' trip||1623-40|
|July 24, 1998||plastic||inst notes pics tape||150.6 m|
|--||plastic||inst notes pics tape||150.6 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.
- The template is in troggle/templates/personexpedition.html
- The code is in function personexpedition() which calls GetPersonChronology() in troggle/core/views_logbooks.py
- the connection between the two is made in the URL resolver in troggle/urls.py
To be fixed!