Thanks for flagging that up Gary. We'll investigate and report back asap.
Hi Gary,
It looks like it was only around the Wellington area where there was a problem - other parts of New Zealand appear to be OK, as far as we can tell. We've reverted the elevation data for this area and are recalculating the Ascent figures for affected routes. This update should complete over the next few days, but most of your routes should already now have the missing elevation data.
I have just caught up with this upgrade in the calculation of ascent statistics when I noticed that the ascents in my earlier routes differed from those I had recorded in my own records. No problem, I can correct my own records so that I can still compare across routes.
Can you explain what the difference is between the elevation interval filter and the gradient filter? Am I correct that if I want to capture all the undulations of a route in most detail, I should keep the filter sliders at their lowest level?
Finally, I notice when I set the ascent filter in the statistics above the route profile at its lowest level (1m or 3 ft), the Ascent (raw) and the Ascent (filtered) are the same. Is this the default?
Thanks
Hi Liz and Tom,
The Elevation Interval slider changes the gap between the elevation readings, so readings in between are ignored. If you change from "Chart" to "Data" you'll be able to see better how this works. You can use this to as a simple way to smooth the overall profile of the route.
The Gradient Filter sets the maximum and minimum gradient between the readings, so that small elevation changes below the minimum gradient are ignored and large elevation changes above the maximum gradient are reduced. You can use this to filter out unexpectedly steep peaks and troughs as well as ignoring sections that are almost flat.
To show the maximum detail, the Elevation Interval slider should be set to the minimum value, the Minimum Gradient Filter should be set to 0% and the Maximum Gradient Filter to the maximum value.
Regarding the Ascent Filter, yes, a value of 1m will not have any effect - when set to 1m, changes of 1m or more (the minimum it can change by) are counted in the Filtered Ascent figure.
Thanks for that. I've got it now after playing around with it a bit.
Liz