440.9 m surveyed this year.
Table of all trips and surveys aligned by date
|July 26, 1997||Journey - Team Lardis Time Travel to Expo|
|July 28, 1997||136 - Steinschlagschacht||1623-136|
|July 29, 1997||136 - Steinschlagschacht||1623-136||entrance||inst notes pics inst||246.3 m|
|--||entrance||inst notes pics inst||246.3 m|
|July 31, 1997||136 - Steinschlagschacht (136)||1623-136||theatre||inst notes pics||103.8 m|
|--||theatre||inst notes pics||103.8 m|
|Aug. 3, 1997||136 - Steinschlagschacht||1623-136||fantasy||inst notes pics tape||90.9 m|
|--||fantasy||inst notes pics tape||90.9 m|
|Aug. 7, 1997||Surface 136|
|Aug. 10, 1997||136 - Footlights Traverse||1623-136|
|Aug. 12, 1997||Surface - Pissing about on the surface|
|Aug. 13, 1997||Surface - Pissing about on the surface again|
|Aug. 14, 1997||136 - Derig 136||1623-136|
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!