Travel time discrepancies

Steve Jarrell

Does anyone have any idea why the HERE maps calculate a travel time for a route that's WAY more than any of the other maps? Here's a link to my route. The calculated times are for the various maps are:

MRA - HERE map - 4:17
MRA - TomTom - 3:25
MRA - OpenStreetMap - 3:31
Kurviger - 3:15
Google Maps - 3:15

I can understand a little difference, but this seems excessive to me.

Thanks for your help!

Steve

Corjan Meijerink

It's specifically the road after waypoint 26 that gives way longer estimates than other map sources. It's based on the realistic travel time HERE tracks for that section and my guess is that their data on that is wrong.

Either incorrect speed limit or some anomalies in their realistic travel time estimation

Steve Jarrell

@Corjan-Meijerink That's interesting. Google Maps is estimating an average speed of 28 mph for the entire route which seems to be very reasonable. I have found Google Maps and Waze to be extremely accurate in their route time estimations. A greater than 1 hour discrepancy between what Google calculates to be a 3:15 minute drive is a BIG discrepancy.

I'm riding this entire route tomorrow with our local BMW riders' group at a leisurely pace and we'll be taking a 15 minute break halfway through. I'll report back with the exact time it took.

My guess is that there's something wrong with the HERE map's calculations for some reason instead of the other 4 calculations being wrong, but there's nothing like riding it to see for sure!

Corjan Meijerink

@Steve-Jarrell keep me posted!
Might also check what the navigation itself estimates once you load the track itself! (Not the converted route)

Steve Jarrell

@Corjan-Meijerink I have. The route-track and just the track both are 3:15, exactly like Google and Kurviger. It's only the HERE route that's way off. I think the solution for me going forward is going to be just using the OSM map as my default and forget about using the HERE map. The HERE map seems to have limitations that the others don't for whatever reason.

Hopefully the "The selected mode only works with the HERE / TomTom map" dialog won't be displayed in a future update if I have my transport mode set to Car as we discussed in a separate post.

Thanks,

Steve

Con Hennekens

@Steve-Jarrell said in Travel time discrepancies:

The route-track and just the track both are 3:15, exactly like Google and Kurviger. It's only the HERE route that's way off

I suspect that distance and duration of tracks are values that are embedded in the track data. They won't change on any platform unless recalculated.

Steve Jarrell

@Con-Hennekens If I look at the .gpx file it looks like the coordinates start at 13:35 and end at 16:15. If my "clock math" is correct that's 3:40. It does seem strange though that MRA's track, route-track, and Google's MyMap all show the same time down to the minute (they're all just using the track) so It would seem reasonable they're calculating it from the track somehow. I'm sure some of the MRA gurus could shed some light on this.

We rode the route today and it took 3:20, but that included a 15 minute break and about 10 minutes in delays for road construction where they're still rebuilding roads here in Western North Carolina that were destroyed by Hurricane Helene back in late September.

That would make the actual ride time about 2:55.