I've just discovered that mapmyride.com is replacing routeslip (which worked wonderfully well thank you very much). The "climb" or "ascent" totals are completely wrong. Both on maps that were migrated over and maps that I put in new. The hill profile looks accurate...but the totals are not even close.
Also, is there a place for general site feedback. I'm dying to make some comments.
I also noted that when mapping a ride you can see the "ascent" or "climb" rise to say 1,200 ft, then when posting your next point the "ascent" drops to say 900 ft. Hu?
I didn't know going down hill reduced my total climb...
yep, I've just noticed this too. My lowest point was 100ft, my highest was 1069ft and yet my TOTAL ascent (for a 40 mile ride) was only 870ft. I wish it felt like I'd climbed less than was physically impossible but sadly not.
Something crazyn is going on. Routes that I had that used to have the sensible cumulative ascent, now do not in the new (July) version of MapMyRide. Please fix! (Of course, I *love* this tool, so thanks for all the other work you guys do!)
It almost looks like feet and meters got mixed up.
Switching to meters gives a total ~3 times higher than it gives in feet. Actually, thats almost certainly what happened. The height in "m" (ie minimum and maximum elevation) is right what you would read off the topo in FEET.
Indeed. A route I imported from bikely.com (via file) showed 1700 m ascent - figure from bikely is 2700m. I downloaded the csv file and worked out the total ascent from the elevation figures - came to 2300m.
Auto-notes are enabled by a checkbox in the Map Settings.
As for questions about elevation accuracy and the data sources we use:
We report ascent and descent stats for routes when they become 'significant'. This is currently set at about 60 meters of total climb. We can't guarantee a great deal of accuracy for routes with ascents < 60m, so we don't want to confuse our users by displaying inaccurate data. For long ascents, you should see your stats appear the the right of the elevation profile.
Our ascent and descent calculation algorithms don't count every small elevation change at every point because we need to filter out 'noise' in the underlying data. Prior to our latest algorithm change, we were reporting ascents that were in many cases too high. Our new algorithm gives more reasonable results for a wider variety of routes. However, since we know that this isn't 'perfect' quite yet, we've provided the raw data in CSV format so that users such as yourself can interpret the data as you choose.