Tomtom chooses WRONG route

scubaal
scubaal Registered Users Posts: 53
Legendary Explorer
This problem has existed for over 2 years. I have reported it multiple times.
Now I am adding screen shots so others can see the issues a verify although I have no expectation it will be rectified.

Using TomTom (Go or MyDrivce it doesnt matter- same result as the underlying algorythm is at fault) set to choose fastest route.
Routing from - Monash, ACT to Huskisson, NSW
TomTom routes 3:08 hours - 260km.
This is NOT the fastest route.
If I modify the route to go via Nerriga, TomTom comes back with 2:39 hours - 198km.
We are not talking a couple of minutes here - this is a huge difference.
This is the correct fastest route that Google and Apple find EVERY TIME.
What is up with the TomTom app?
There seems to be no way to find out WHY the algorithm chooses a diffetrent route.
Images attached so you can verify it yourself.

s7ielj812opf.png
92ecpfvcjyfr.png

I have reported it through Mapshare a dozen times with no fix. I would be happy to help TomTom troubleshoot but no-on one seems to care.
Tagged:

Answers

  • VikramK
    VikramK Administrators Posts: 14,342
    Moderator
    Hi @scubaal
    Thanks for the detailed explanation...
    Let me see if I can report this internally. Could you also share the mapshare id's for the previous reports?

    Thanks
    Vikram
  • scubaal
    scubaal Registered Users Posts: 53
    Legendary Explorer
    VikramK wrote: »
    Hi @scubaal
    Thanks for the detailed explanation...
    Let me see if I can report this internally. Could you also share the mapshare id's for the previous reports?

    Thanks
    Vikram

    Thanks Vikram. The Mapshare error reports were at various points along the road identifying that it has been FULLY sealed (and has been for 3+ years) - because I thought that was the issue. Mapshare says they are 'fixed' - but the routing problem persists.

    Mapshare IDs:

    788a61db-9f5e-4cd6-b52c-469aa9432d12
    37fdcb3e-afb5-4151-8dec-ffbb1a098f23
    5e2b51e1-cea3-40af-a71c-7b586a5e00ff
    70ed5376-46ce-4588-a1e7-95570f2fd7bb
    2b942343-a1db-428c-a2bf-b501d732bd66
    0a2bcf41-3783-4c75-92ed-1258c952ef63