1266.2 m surveyed this year.
Table of all trips and surveys aligned by date
|July 23, 1995||Journey to Austria|
|--||161 - France - Black Suspender||1623-161|
|July 24, 1995||ppot||inst tape notes||99.1 m|
|--||ppot||inst tape notes||99.1 m|
|July 25, 1995||161 - Entrance a||1623-161|
|July 26, 1995||161 - France||1623-161||suspender||inst notes tape||42.3 m|
|--||suspender||inst notes tape||42.3 m|
|July 27, 1995||161 - Surveying Triassic Park & Photos||1623-161||pt1||pics notes notes instrument||446.5 m|
|July 30, 1995||semidet||notes instrument||128.2 m|
|July 31, 1995||161 - Go to find new entrance||1623-161||scarface||notes instrument||239.9 m|
|Aug. 1, 1995||161 - More 161d & triassic||1623-161||pt3||notes pics instrument notes pics instrument||310.3 m|
|--||pt3||notes pics instrument notes pics instrument||310.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!