484.3 m surveyed this year.
Other years: | 2017 | 2018
Table of all trips and surveys aligned by date
|June 8, 2017||12monkeys||95.8 m|
|July 19, 2017||Balcony - Natural Highs||Balcony|
|July 20, 2017||Balcony - Sloppy Seconds 2||Balcony|
|July 21, 2017||sloppyseconds2||51.8 m|
|July 25, 2017||nothingtosee||127.8 m|
|July 27, 2017||nothing2see||81.9 m|
|July 28, 2017||Balcony - Nothing to See||Balcony|
|Aug. 1, 2017||Balcony - Nothing To See||Balcony|
|Aug. 2, 2017||Tunnocks - The Beast, trip #3||Tunnocks|
|Aug. 6, 2017||FGH - below first pitch||FGH|
|Aug. 7, 2017||plateau - Prospecting beyond FGH and GSH||plateau|
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.
I blame Aaron Curtis who was too fond of being clever with the Django templating system
instead or writing it in python anyone could understand.
- The template is in troggle/templates/personexpedition.html
- The code is in function personexpedition() which calls get_person_chronology() in troggle/core/views/logbooks.py
- the connection between the two is made in the URL resolver in troggle/urls.py
To be fixed!