Jon Telling : 1999

592.1 m surveyed this year.

Other years: | 1999 | 2007

Table of all trips and surveys aligned by date

DateTripsSurveys
July 27, 1999 2 inst notes pics 97.6 m
July 31, 1999 runnybowels inst notes pics tape 196.4 m
-- runnybowels inst notes pics tape 196.4 m
Aug. 1, 1999 136 - 136 1623-136
Aug. 4, 1999 136 - Steinschlagschacht 1623-136 left2route inst notes pics tape 71.8 m
-- left2route inst notes pics tape 71.8 m
Aug. 5, 1999 136 - 136 1623-136 carpetworld inst notes pics tape 50.3 m
Aug. 7, 1999 136 - 136 1623-136
Aug. 8, 1999 pebbled1 inst notes pics tape 33.2 m
-- pebbled1 inst notes pics tape 33.2 m
-- pebbled2 inst notes pics tape 46.5 m
-- pebbled2 inst notes pics tape 46.5 m
-- pebbled3 inst notes pics tape 47.9 m
-- pebbled3 inst notes pics tape 47.9 m
Aug. 9, 1999 136 - Push near Runny Bottom 1623-136 4 inst notes pics tape 48.5 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!