123.8 m surveyed this year.
Other years: | 1999
Table of all trips and surveys aligned by date
|July 10, 1999||Journey - Journey|
|July 11, 1999||Loser Plateau - Carries|
|July 12, 1999||Base Camp - Base Camp|
|July 16, 1999||Cave - Bullethöhle|
|July 17, 1999||161 - Triassic Park||1623-161|
|July 18, 1999||161 - Triassic Park - Latzio||1623-161|
|July 19, 1999||161 - Triassic Park - Scorchio||1623-161|
|July 20, 1999||161 - Triassic Park - Scorchio||1623-161|
|July 27, 1999||136 - 136 to Lost in Space||1623-136|
|July 28, 1999||136 - push end towards Stellerweg||1623-136|
|July 31, 1999||136 - Chile Again||1623-136||watershoot||inst notes pics tape||123.8 m|
|Aug. 10, 1999||136 - derigging in 136||1623-136|
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!