Mismatched place name despite correct latitude and longitude

Please fill out the following sections to the best of your ability, it will help us investigate bugs if we have this information at the outset. Screenshots are especially helpful, so please provide those if you can.

Platform (Android, iOS, Website): Android

App version number, if a mobile app issue (shown under Settings or About): 1.36.8 (628)

Browser, if a website issue (Firefox, Chrome, etc) :

URLs (aka web addresses) of any relevant observations or pages:
https://www.inaturalist.org/observations/265112207

Screenshots of what you are seeing (instructions for taking a screenshot on computers and mobile devices: https://www.take-a-screenshot.org/):


Description of problem (please provide a set of steps we can use to replicate the issue, and make as many as you need.):
Although the latitude and longitude of the observation (and therefore the Encompassing Places) are correct, matching a location near Vancouver, Canada, the place name shown is in Nigeria. The code “QJJF+FW6” preceding the place name means nothing to me, but when I look it up in Google Maps, it appears to identify a location on one of the Gulf Islands in the Strait of Georgia, again somewhere having no relation to the observation.
Step 1: I recorded an observation on the app. At the time of setting the location using the crosshairs icon on the map, I noticed that the place name did not fit.

Step 2: As it happens, I selected a placeholder photo, which I removed before synching this and two other observations from locations a few metres away, neither of which exhibited the problem.

Step 3:

Those locality notes are generated automatically (from Google I think, so not an iNat issue) but are not always accurate, and they don’t update if you change the location. But you can edit that text to say what you like, so I don’t think this is a bug.

3 Likes

Okay, a Google Maps bug, then, apparently, and not anything intrinsic to iNat. In any case, thanks, yes, resolved.

This topic was automatically closed after 21 hours. New replies are no longer allowed.