Jacob Podesta : 2015

930.0 m surveyed this year.

Other years:  | 2015 | 2017

Wallet status | 2015 | 2017

Table of all trips and surveys aligned by date

DateTripsSurveys
July 24, 2015 Balcony - Hiltaplenty and Pubic S Balcony
July 28, 2015 Balcony - to Gösser Wager Balcony gosserwager 26.9 m
July 29, 2015 pubicsynthesis 12.7 m
Aug. 1, 2015 icecock3 10.0 m
-- icecock3 10.0 m
-- northhole2 32.7 m
-- northhole2 32.7 m
-- frozennorth4 41.2 m
-- frozennorth4 41.2 m
Aug. 2, 2015 gosserwager3 49.0 m
-- gosserwager3 49.0 m
Aug. 3, 2015 hiltiaplentypitch 206.8 m
-- hiltiaplentypitch 206.8 m
Aug. 5, 2015 hiltiaplentychamber 237.6 m
Aug. 8, 2015 belowhiltiaplenty2 17.2 m
-- belowhiltiaplenty2 17.2 m
Aug. 9, 2015 belowhiltiaplenty 196.3 m
-- belowhiltiaplenty 196.3 m
Aug. 10, 2015 penguinfellatio2 47.8 m
Aug. 11, 2015 voyeur 51.8 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.)