282.6 m surveyed this year.
Table of all trips and surveys aligned by date
|July 26, 2008||Journey to Austria - Trip to Expo|
|--||['Journey to Austria', 'Trip to Expo ']|
|July 29, 2008||Base Camp - Tunnel work|
|--||['Base Camp', 'Tunnel work ']|
|Aug. 2, 2008||161 - Walk to 161h||1623-161|
|--||['161', 'Walk to 161h ']||1623-161|
|Aug. 3, 2008||Tunnocks - lead in hedonism highway||1623-258||rockyroad||inst notes notes tape||205.0 m|
|--||['Tunnocks', 'lead in hedonism highway ']||1623-258|
|Aug. 4, 2008||161 - 161h to 161d||1623-161|
|--||['161', '161h to 161d ']||1623-161|
|Aug. 5, 2008||Tunnocks - crossword passage||1623-258|
|--||['Tunnocks', 'crossword passage']||1623-258|
|Aug. 12, 2008||toomuch||inst notes useless||77.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!