Becka Lawson : 2011

824.5 m surveyed this year.

Other years: | 1987 | 1988 | 1989 | 1996 | 1997 | 1999 | 2000 | 2001 | 2003 | 2004 | 2005 | 2007 | 2008 | 2009 | 2010 | 2011 | 2012 | 2013 | 2014 | 2016 | 2017 | 2018 | 2019

Table of all trips and surveys aligned by date

DateTripsSurveys
July 29, 2011 Steinbrucken - Convenience series - channel 5 channelfive1 inst notes 44.8 m
July 30, 2011 Steinbrucken - night shift channelfive2 inst notes tape 13.0 m
July 31, 2011 granddayout3 inst notes tape 14.2 m
Aug. 1, 2011 204 Pingu pitch - bottom left pingu2 inst notes tape 54.2 m
Aug. 2, 2011 Tunnocks, Down String Theory - konnisberg - TenthousandBusStops tenthousandbusstops notes inst tape 42.4 m
Aug. 3, 2011 Tunnocks - Leads in higher level above Sting Theory, So Vein and IntoThinAir 1623-258 sovein3 notes inst tape 14.4 m
-- intothinair notes inst tape 72.2 m
Aug. 5, 2011 Tunnocks - Thirty Nine Steps (beyond flying high) 1623-258 thirtyninesteps instrument notes tape 172.3 m
Aug. 6, 2011 161 - Old Men to conservation tape 1623-161 chocolateloops inst notes 117.5 m
Aug. 7, 2011 KH, 161 - Country for Old Men
Aug. 8, 2011 KH - Country for Old Men 1623-161
Aug. 10, 2011 KH - Country for Old Men 1623-161
Aug. 11, 2011 Tunnocks - Konnisberg - that's the way to do it. CONNECTION of 258 -> 204 1623-258 thatsthewaytodoit inst notes 238.3 m
Aug. 22, 2011 suicidalvampyre inst notes 41.2 m

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.
- The template is in troggle/templates/personexpedition.html
- The code is in function personexpedition() which calls GetPersonChronology() in troggle/core/views_logbooks.py
- the connection between the two is made in the URL resolver in troggle/urls.py

To be fixed!