362.1 m surveyed this year.
Other years: | 2011 | 2013
Table of all trips and surveys aligned by date
|July 27, 2013||Alex and Matt driving to Austria||UNKNOWN|
|Aug. 2, 2013||bullet 2nd Hohle||UNKNOWN|
|Aug. 3, 2013||Bullet 2nd Hohle||UNKNOWN||bullet1||75.0 m|
|Aug. 4, 2013||Bullet 2nd Hohle||UNKNOWN||bullet2||101.7 m|
|Aug. 5, 2013||Bullet 2nd Hohle||UNKNOWN||bullet3||47.6 m|
|Aug. 11, 2013||Surface Prospecting - Drafty hole area||Surface Prospecting||2004-10||51.1 m|
|Aug. 15, 2013||Tunnocks, Downgraded window||UNKNOWN|
|Aug. 16, 2013||window||86.7 m|
|Aug. 17, 2013||antsinyourpantsto258||0.0 m|
Horrible bug here but only when there is more than one survex block per day, or is there ?!
WHat we thought was the bug: 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.
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!
What we now know
The eiscream.svx file does indeed record 3 blocks: eiscream, eiscream2 & eiscream3. But (more) careful inspection shows that eiscream2 and eiscream3 are in the year 2000, not in 1999. So they absolutely should not be shown here. So maybe everything is correct after all. (Well, apart from the duplication.)