264.0 m surveyed this year.
Table of all trips and surveys aligned by date
|July 20, 1999||136 - 161 - Steinschlagschacht to Scarface through trip||1623-136|
|July 25, 1999||Loser Plateau - Surface stroll|
|July 26, 1999||204 - Steinbrückehöhle||1623-204|
|July 29, 1999||Loser Plateau - surface surveying to Steinbrückenhöhle||steinsrf||inst notes pics||0.0 m|
|July 30, 1999||ent||inst notes pics||264.0 m|
|--||ent||inst notes pics||264.0 m|
|--||steinbrk_atob||inst notes pics||0.0 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!