Just an FYI, and some may have noticed this, however didn't find anything on it. It is the same in the Web Connect, idk about the Apple Connect. I did find an article that said Garmin recently added MapBox to Connect, instead Google Maps, so maybe they have been noticing disrepencies already
Noticed this today, when planning a route that at some points it was significantly off. Idk, what Google uses, but somewhere the 2 maps don't line up in Connect.
This isn't something I would put on Garmin necessarily, however it is good to know:
Maps from Google Maps and Matchbox (which uses OpenStreetMap) don't always lineup. So when planning a route, if you plan a route using one then it won't line up in one or the other.
Meaning that what was a properly planned route will run off trail significantly for example for some distances and points.
IIUC the Fenix 7 (and other watches with navigation too?) uses the map based on OpenStreetMap. So if you line out your route in Connect on Google Maps, you may have issues with routing and turn by turn?
Matchbox is based on OpenStreetMap. Komoot is based on OpenStreetMap as well. The TopoActive uses OpenStreetMap too.
So, in that sense consistently just using MatchBox(OpenStreetMap) can help planning routes maybe, at least avoid disrepencies, and lines up better with the map used in the watch