Andy Chapman : 2011

296.7 m surveyed this year.

Other years:  | 2010 | 2011 | 2014

Wallet status | 2010 | 2011 | 2014

Table of all trips and surveys aligned by date

July 22, 2011 Tunnockschact Entrance Series UNKNOWN
July 23, 2011 UNKNOWN
July 26, 2011 Tunnocks UNKNOWN
July 27, 2011 Tunnocks UNKNOWN
July 28, 2011 bobon 58.5 m
July 30, 2011 Tunnocks - Leaky Chamber - Bob on Tunnocks
Aug. 1, 2011 Tunnocks - Above and Beyond Tunnocks
Aug. 5, 2011 Tunnocks - Thirty Nine Steps (beyond flying high) Tunnocks thirtyninesteps 172.3 m
Aug. 6, 2011 Surface Prospecting North of Tunnocks UNKNOWN
Aug. 7, 2011 Tunnocks, Bob on Passage UNKNOWN bobon2 23.5 m
Aug. 15, 2011 appendix 15.9 m
-- appendix 15.9 m
-- appendix 15.9 m
-- root 26.5 m
-- root 26.5 m
Aug. 16, 2011 Tunnocks derig finish UNKNOWN

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/
- the connection between the two is made in the URL resolver in troggle/

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.)