Tomorrow’s ride was planned months ago . Cycle travel shows 360 ft of climb, but when I look at this route on Garmin Connect, it shows the climb to be 2959 ft. On today’s ride the actual climb was 2917 ft but cycle Travel showed the route would be 2200 ft. for route 755922. This degree of error is not acceptable when carrying camping equipment on tour. I am losing confidence in Cycle Travel for planning reliable routes. It’s a shame as I love the routes but not the errors in height. I can give more examples.
Comments
Some difference in totals is always to be expected between sites but there is something very wrong with the first example. I’m on tour at the moment so not able to look into it in detail I’m afraid but I think if you force it to replan (ie click the ‘Get route’ button again) it’ll fix it. Sorry for the hassle and I’ll look into it when I’m home.
I think this has been the hardest bug to identify and fix in over 10 years of building cycle.travel!
Essentially this was an issue where you have a route without full turn-by-turn instructions and split it into multiple days; in some circumstances the distance calculations (and the elevation calculations based on them) would go askew. This was particularly the case in hilly areas.
I’ve worked out a fix and it’ll be rolling out over the next week or two – some of it will require a mapping update but we’re due one of those soon anyway. Thank you for spotting the issue and sorry for the hassle.
thank you Richard for your perseverance