751.5 m surveyed this year.
Table of all trips and surveys aligned by date
|July 8, 1995||Plateau - Prospecting trip|
|July 11, 1995||161 - To Dreaming of Limo||1623-161|
|July 13, 1995||161 - Pushing Oral Series||1623-161|
|July 20, 1995||161 - inadvertantly go caving. (Down France)||1623-161|
|July 22, 1995||Main entrance, pushing hole off Stomping|
|July 24, 1995||Main Entrance, Pushing 'Doubting Thomas' Series & Surveying||limolink||inst tape notes||13.8 m|
|--||doubting||inst tape notes||181.2 m|
|July 26, 1995||161 - France, surveying Regurgitation (Goulash)||1623-161||regurg||inst tape notes||41.6 m|
|July 27, 1995||161 - Surveying Triassic Park & Photos||1623-161||pt1||pics notes notes instrument||446.5 m|
|Aug. 1, 1995||161 - Derigging France||1623-161||daz||inst tape notes pics||68.3 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!