0.0 m surveyed this year.
Other years: | 2019
Wallet status | 2019
Table of all trips and surveys aligned by date
|July 7, 2019||plateau - Discovery of Snow-filled Steinbruckhohle||plateau|
|July 11, 2019||base camp - CUCC Austria Expedition 2019 Blog||base camp|
|July 14, 2019||Homecoming - Blog Post, More Details on Homecoming||Homecoming|
|July 15, 2019||Homecoming - Blog Post bit||Homecoming|
|July 16, 2019||Homecoming - Blog PostBlog Post bit||Homecoming|
|July 17, 2019||Homecoming - Blog Post Homecoming||Homecoming|
|July 18, 2019||base camp- Blog Post bit - Basecamp||base camp- Blog Post bit|
|July 19, 2019||Homecoming - Blog Post bit, Homecoming||Homecoming|
|July 20, 2019||plateau - Blog PostBlog Post bit - Prospecting||plateau|
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.)