145.8 m surveyed this year.
Table of all trips and surveys aligned by date
|July 10, 2018||Tunnocks - 1st rig||1623-258|
|July 11, 2018||plateau - Prospecting/visiting known holes near Organhöhle||2012-dd-08||notes inst||45.0 m|
|July 15, 2018||258 - Tunnock's Rig||1623-258|
|July 19, 2018||Tunnocks -Setting up Camp Kraken (Tunnocks)|
|--||Homecoming - shallow level||1626-359|
|July 20, 2018||Fischgesicht - Surveying near Ulysses|
|July 21, 2018||ulysses_to_toto||inst notes pics pics||100.8 m|
|July 24, 2018||Tunnocks - Camping Trip||1623-258|
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!