Have you gone into the route settings and made sure there are options clicked, ie avoid highways, ferries etc. That happend to me when I got mine and then once I set the route options to my liking, everything was good.
If that does not cure it then do a reboot of the TCAM and see if that helps with GPS accuracy.

 

First of all, you need to make sure you have access to LTE/GPS signals.
if yes, download an "off line" local map in to the system and it will always be ready regardless off signal.
you can also download a map via wifi hotspot

 

Hmm, I'm not sure I'd ever advise anyone to "trust" Google Maps ... even though I do use it regularly, I've learned that it often hallucinates and tries to send me the wrong way down one way streets, gets the speed limit wrong, decides that a road is blocked when it isn't, and (I call these Google Specials) tries to send me down some tiny back road when there is a perfectly good main road available.

I think of it as being like AI - very useful but not to be entirely trusted.

I find I generally get better routing from Apple Maps on my phone, connected via Car Play ... the only catch (and its a big one) is that I find the driver-display mini-map to be a lot less friendly than the Google Maps version, so tend not to use it very often. YMMV.

 

tries to send me the wrong way down one way streets, gets the speed limit wrong, decides that a road is blocked when it isn't, and (I call these Google Specials) tries to send me down some tiny back road when there is a perfectly good main road available.

Instructions to drive against traffic in one way street have never happened to me, driving in many countries for many years. Is it possible those were recently changed roads?

Deciding that a road is blocked is probably based on user reports, again the road could have been blocked and just opened.

Driving through tiny back roads is actually a Waze (Google Maps sister) specialty, GM actually factors in some kind of "comfort" factor and will not send you into a recently plowed field only to save 25 seconds (which Waze will do).

 

Well, all I can do is report my experience. According to Google, the road immediately outside my house has been blocked for many months (it isn't), and there is a one-way road nearby that it has been getting wrong for years. I've even tried reporting some of these errors but the Google Maps problem-reporting system is incredibly narrowly defined - if the thing you need to say doesn't fit their preconceptions, you're ignored. Typical narrow-minded programming behaviour. There is also a noticeable US orientation to their view of the world ... addresses that don't have street numbers, for example, it struggles with.

And while I've not been sent through a plowed or even ploughed field, I continue to be sent on silly diversions which might look quicker on paper but which nearly always aren't. A few examples that spring to mind:

• in Australia, being routed onto what would have been a 20 mile dirt track when there was a perfectly good highway just a few miles longer
• in Spain, being sent through a village where the gap between buildings was less than the width of my (ordinary) car. There were full sized roads available.
• in South Africa, being taken off a main road for a completely pointless diversion through a town (no, there wasn't a delay on the main road, the diversion was just shorter)
• in England, being sent (with a lot of other people) down a track which just got narrower and narrower until becoming impassable. It took a lot of effort for us all to extract ourselves from that mess.

For all that I do mostly continue to use it, but with vigilance (as one should with any "smart" IT system).

 

I've even tried reporting some of these errors but the Google Maps problem-reporting system is incredibly narrowly defined

Yes it is, the only exception are transient reports through the app (police, queues etc.)
I drive a stretch of 60kms main road, so not insignificant, where the speed limit was changed from 90 to 80 years ago but not at Google. It's even funnier since it adjust itself whenever it sees a 80 sign, but jumps back to 90 at the next junction.

 

Google maps indeed seems to be focused on taking the shorter route if it thinks it's faster, even though it makes no sense at all. I-5 in between Tacoma and Seattle, instead of staying in the carpool lane, it likes you to go back to the main lanes if it saves maybe a few seconds (speed limit is the same on both). Then going southbound turning into route 16 westbound, it likes you to ignore the (left) carpool exit and directs you to the regular exit which is often extremely busy and merges into one lane before merging onto 16.

All could be avoided quite easily by programming in some (time) threshold for leaving the carpool lane.

 

I have one funnier: Google maps also thinks "most energy-efficient" means smallest kWh/km, instead of lowest kWh required to get to your destination
I wonder if someday it'll tell me to go around the whole city just to get to the stores down the street, just because it's "most energy-efficient"

 

I suspect no system is perfect. My old MG4 satnav used to send me in circles or down cart tracks because they were 01.km shorter. A very old Alfa Romeo system at least gave me options for fastest, shortest, avoid motorways, etc. I'm old enough to remember the introduction of calculators where people would write down whatever the display gave them as the answer. We were taught to always sanity check the result before blindly assuming it was right. Rule seems to be that what you see is "indicative only", gut-feel should help as in "that doesn't seem right".