This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Garmin Explore and Google Maps GPS Don't Match Up

Having a weird issue, entering some Google Maps GPS coordinates into Garmin Explore Map gives wrong results. 

For example: Enter the following into Google Maps: 39.401089 -122.426720 or Or 39°24'03.9"N 122°25'36.2"W take your choice. 

Enter that into Explore.

Look at the map.

Not even close. The Garmin Explore result is way up North. 

Any idea why this might be happening?  Note, cutting and pasting the GPS for the Eiffel Tower worked. But here: nope. 

Top Replies

All Replies

  • I understand, however on the explore website you cannot navigate so there is no lost functionality. It is a POI search tool. If you are looking for specific coordinates to navigate to you would need to create a waypoint or route anyway.

  • Thank you for looking into it. Probably don't need to point out (and many people I am sure will) that when entering in coordinates to a GPS site, the primary user intent is to go to those coordinates not, say, a random city street 20 km north of there. Especially since the main use case for the tool is designing routes. In empathy, part of my full time job is hitting product managers and engineers with a rolled up newspaper and saying "no! bad dog! Bad UI!". I recommend a fairly light paper like the Financial Times combined for cookies or donuts when they fix it (as a long time subscriber, I will happily buy the donuts). R  ; ) 

  • Also, just my opinion, but the waypoint tool is terrible for this. Also, jelly donuts, the best. 

  • This is true.  But the behavior is the same on the iOS Explore app, and the contract for that is that it must work offline in the backcountry.  Will there be a separate bug submitted for that?  Given this behavior it's surprising that a waypoint is automatically created upon entry for the POI search across every UI...it's just usually in the wrong location when given raw geoaddress info.  I say "usually" because there are way more geoaddresses than there are named POIs.  My guess is the 99% case for raw geoaddress info search, is the resulting waypoint will be in the wrong location - because why search for a POI by raw address if you know the POI name?  And then it fools folks sharing geoaddress info into thinking they have the right waypoint location, when they do not.  Dangerous.

  • +1 on request for a separate ticket

  • This really sucks!