269.3 m surveyed this year.
Other years: | 2017
Table of all trips and surveys aligned by date
|July 25, 2017||nothingtosee||inst notes tape||127.8 m|
|July 28, 2017||Balcony - Nothing to See||1623-264||hilti_nts_bones_pitch||inst notes||41.5 m|
|--||hilti_nts_near_bats||inst notes||25.5 m|
|--||hilti_nts_near_start||inst notes||74.5 m|
|Aug. 1, 2017||Balcony - Nothing To See||1623-264|
|Aug. 6, 2017||Tunnocks - 'The Beast' has fallen #gloriousendings #whataday #pokemon||1623-258|
|Aug. 7, 2017||Balcony - Nothing to See - surveying and photography||1623-264|
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!