0.0 m surveyed this year.
Table of all trips and surveys aligned by date
|July 1, 1996||Nick, Helen, Gunilla and Matthew go to Expo|
|July 3, 1996||Looking for a way back to England...|
|July 4, 1996||Top Camp carry|
|July 5, 1996||Caving in 161d|
|July 6, 1996||Pushing Leads off Trifurcation|
|July 9, 1996||Attempt to go caving|
|July 11, 1996||Surveying big pitch off Minoan Surprise (QM 95-54)|
|July 13, 1996||BPEC|
|July 14, 1996||'Interview Blues'|
|July 15, 1996||Prospecting|
|July 17, 1996||Interview Blues|
|July 18, 1996||Interview Blues|
|July 20, 1996||Interview Blues|
|July 21, 1996||IB, where else?|
|July 23, 1996||Interview Blues|
|July 26, 1996||Interview Blues - 161d|
|July 28, 1996||Interview Blues|
|July 29, 1996||IB, where else?|
|July 30, 1996||You know where|
|July 31, 1996||No prizes for guessing where|
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!