749.4 m surveyed this year.
Table of all trips and surveys aligned by date
|July 24, 2015||Balcony - Hiltaplenty and Pubic S||1623-264|
|July 28, 2015||Balcony - to Gösser Wager||1623-264||gosserwager||inst notes tape||26.9 m|
|July 29, 2015||pubicsynthesis||inst notes tape||12.7 m|
|--||pubicsynthesis||inst notes tape||12.7 m|
|Aug. 3, 2015||hiltiaplentypitch||inst notes tape||206.8 m|
|Aug. 5, 2015||hiltiaplentychamber||inst notes nail||237.6 m|
|Aug. 8, 2015||belowhiltiaplenty2||inst notes pics tape||17.2 m|
|--||belowhiltiaplenty2||inst notes pics tape||17.2 m|
|Aug. 9, 2015||belowhiltiaplenty||inst notes pics tape||196.3 m|
|--||belowhiltiaplenty||inst notes pics tape||196.3 m|
|Aug. 11, 2015||voyeur||inst notes nail||51.8 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!