Work progressing on the 'reverse measurement' update. Once I've given it a thorough test Apple takes about 5 or 6 days to process the update for the App Store.
Yes, the 21st century does call but I still jot counter values down on my route map just in case technology fails!
I'm a dedicated user of a spreadsheet (Numbers) for the report generation as the presentation is important. I'll follow the link to the above spreadsheet. The app in this respect is complimentary to that process in that it is an in-the-field tool, basically an intelligent pocket calculator that knows the calculations and can feed a spreadsheet when back at home. I'd be interested to hear of any spreadsheet functions that people feel could be incorporated.
If anyone was wondering, the design of page 3 is supposed to mimic a cycle computer with the current position in the middle with the next split ahead and the last split behind. If the counter is incremented in realtime it behaves just like one with a dynamic countdown to the next split being shown (my test app can simulate this). If anyone knows how to interface an iOS device to a jones counter this would be the result! Unfortunately iOS accessory development is a complicated process as I believe you have to get access to licensed chips.
In the meantime, hidden away on the calibration summary page is a little output calculating the size of your tyre circumference which can be used with most cycle computers - seems to be reasonably accurate for distance awareness aside from the inability of cycle computers to reverse backwards...
Not sure about the GPS elevation data as I test this on an unequipped iPod - GPS units have always been a bit notorious about displaying 3D elevations unless datums are corrected; off the top of my head, terminology such as WGS84 geoid elevation and Ordnance Survey Newlyn Datum (ie local mean sea level for here in the UK) have significant differences so you need to know which one you are using. Our Ordnance Survey website explains it all in horrendous detail:
http://www.ordnancesurvey.co.u...in_Great_Britain.pdf but that doesn't help with the accuracy of the GPS question! That said, relative elevations should be accurate and logged plan locations can be referenced to the ground in Google Earth to ascertain the real elevation if there is an error.
Tracing the course as a ground level 'path' in GoogleEarth then using 'show elevation profile' yields an elevation v distance diagram which is as good as is needed as seems to be within a metre or so of our 'official' OS mapping elevations.