I had Google maps on the other day for directions mainly in the the last 2/3 miles of my journey. It's a good job it wasn't needed at the start, as I noticed it got the lanes I needed drastically wrong on every single roundabout. Little wonder there's chaos of people chopping and changing lanes.
Google maps is terrible. So bad, I typically do the opposite of what it suggests, and usually get it right
When driving back from Stoke to Norfolk I drive through Grantham on the A52, yet every time google maps tries to send me South down the A1 for about 2 miles then on a single track farmers road (Whalebone lane) because it "thinks" that road is a 60mph road, and is therefore faster than driving through the centre of Grantham, when in reality its a 20mph at best pot-hole infested nightmare - and yet it still tries to route me that way every time!
just doing a comparison of waze/google/apple maps , it's ridiculous how waze&apple pick routes using windy cross-country roads, and equally (as a newish user)
have poor mechanisms to adjust the route to travel what you know would be a better route.
I need to learn how you can sync a google maps route between a laptop(which you have optimised on big screen) and the mobile phone, and reliably replay routes you have done/verified before
I prefer native maps over carplay but do find that it often suggests better routes.Never use Apple Maps for navigation.
10 years on, it’s still a cut and paste nightmare of every cheap geodata vendor’s offerings.
It's usually does stuff like that to avoid traffic.