Different route planners giving different elevation data?

[Paul_L]

I've been using mapmyride to plan routes, but yesterday i couldn't get on it for whatever reason, so i used bikehike instead.

The elevation details from bikehike looked a lot higher than mapmyride, so i compared the same 38mile training route on both and got completely different data;

mapmyride gave me;
distance = 61.6km
Min = 73m
Max = 371m
Ascent = 532m
Descent = 637m

bikehike gave me;
distance = 61.6km
Min = 73m
Max = 367m
Ascent = 927m
Descent = 983m

Any ideas why they should be so different?

Not that it matters just curious.

 

[Crackle]

They use different algorythyms to add up the mileage. I found Mapmyride to be more accurate except if you are on a road with lots of little climbs and descents. You can download the elevation data from Mapmyride and compare it to your OS map.

 

[jimboalee]

The BikeHike, Mapmyride, Bikely mapping packages are NOT really cycling specific.
They are adaptions from motoring route planners.

I have indicated on another thread that these route planners DO NOT follow useful cyclepaths to avoid busy road junctions or cut routes shorter than following the roadway.

As for hills, all you need to know is where the chevrons are on the OS map.
If there isn't a chevron, you have the gears for it. If there is a single chevron, you will be tested; and if there are two chevrons, expect a challenge.

To plan a 'training' route for roadracing purposes, look on the OS map and pick out the single chevrons. Plan your route to ride up as many as you can find.

If there are some hills around with single chevrons, a 'training' ride will be a wasted trip if you skirt round the roads you NEED to be riding up.

To plan a 'leisure' ride or an 'easy' ride, fair enough, avoid the 14% hills.

If you want big legs, go for the double chevrons.