200.2 m surveyed this year.
Table of all trips and surveys aligned by date
|July 10, 1992||161||161|
|July 14, 1992||161 - pipeless||161||beehive||72.6 m|
|July 16, 1992||161||161||1st||43.4 m|
|July 17, 1992||Puffball - Surface survey||Puffball||182to184||0.0 m|
|July 18, 1992||Puffball||Puffball|
|July 22, 1992||161 - (Repton) Garden Party||161|
|July 24, 1992||161 - Garden Party Finish - Survey & derig||161||3rd||62.4 m|
|July 27, 1992||161 - France||161|
|July 29, 1992||161 - Hyper Gamma Spaces||161|
|July 30, 1992||161 - Repton||161|
|Aug. 2, 1992||161 - Arrow Chamber||161|
|Aug. 4, 1992||161- Knossus||161- Knossus|
|Aug. 5, 1992||161 - More De-rigging||161|
|July 22, 1993||hgslink||21.7 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.
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!