Discrepancy between Planner and NavigationApp

[Corjan Meijerink]

Probably not a HERE route so you’d have seen a warning that it was converted to a navigable route. That changes some numbering.

Create routes in HERE when navigating with our app

[mtackoutlook.com]

Thanks, Corjan. This creates the next questions: I copied the route, and took 1x OSM as engine, and 1x HERE.
While in view, the km and hours/duration differs (especially time by over 1 hr), but after save, it still shows OSM data, also when re-opening the HERE version.
So, the routing engine setting is not consistant when closing planning.

[mtackoutlook.com]

BTW: I had to force HERE to follow a small street by placing 3 extra route points, which were not necessary with OSM. Then, it was possible, without it made a detour of 40 km.

[Reinhard Grossmann h 0]

Did you switch on Traffic (upper right corner?) Maybe there is a road block e.g. reconstruction site, one-way etc.

[Anonymouse]

I reported a similar discrepancy between routeplanner estimate and navigation estimate (both using HERE) in the beta forum - I wasn’t sure whether this was a beta routeplanner issue but perhaps it belongs here.

Here’s what I found:

• bigger than expected difference between beta routeplanner’s duration estimate (1h29) and the estimate I got when I started navigating (2h15 inc 18 min traffic, ie 1h57). What causes such a big divergence? (Actual duration when driven: about 2h 10 with little traffic).

• mid journey the duration suddenly leapt to over 4h, including 2h of traffic. This was completely phantom - there was no 2h traffic jam

• when I pulled over to look I saw that it had also invented a series of seasonal road closures which don’t exist as far as I know (this is southern England between Hungerford and Inkpen, not the alps). Bizarrely, it had allocated 11 minutes delay to each point. (this still didn’t add up to 2 hours jam either). As I drove the route these disappeared again, and there was of course also no closure or delay - eventually the estimate returned to normal.

Beta forum post has more info: https://forum.myrouteapp.com/topic/12365/carplay-oddities

[M. Schrijver]

It is good idea to plan on the Here map and use the OSM map to compare the route. This method reduces the discrepancy a lot. Every map uses it own algortimes and because of that the course of the route can differ.
In screenshot of the phone i see a lot of orange and red warning signs. I suspect this also affect the course of the actual route.

When i make a route between point 11 and 12 i see there are more option to ride from 11 to 12. The shape on the phone is an alternative route.
Simply put. Use more points to force the navigation to take the direction you planned.

[Anonymouse]

There are some odd things going on with route durations. In this example all three engines are following the same route but there is a huge discrepancy in estimate, with TomTom estimating 30% longer. It’s set to ignore seasonal closures (there aren’t any anyway).

What causes this?

[M. Schrijver]

On a TomTom device is always see a longer duration compared to MRA. So that is explainable. Don't expect that every engine calculates the same time.

[Anonymouse]

Fine that the engines estimate differently, but 2h7 (tomtom) vs 1h38 (OSM) on an identical route, planned when there is no traffic, seems a bit out of bounds which is why this one caught my attention.

By the way, the new route comparison feature, with auto-repair, is fabulous.

[M. Schrijver]

It is what it is. TomTom thinks you're driving pretty slow. While OSM thinks you're driving pretty fast. Never used OSM. I cannot say if OSM is exaggerating or not.
From my own experience i can say that TomTom times are on the slow side (too much time).