It’s been several times that I notice that the application does not recognize certain places, in the “explore” part of the application while the places in question are displayed without problems on the website.
Is this an app bug?
Platform (Android, iOS, Website): Android
App version number, if a mobile app issue (shown under Settings or About): 1.26.7
Browser, if a website issue (Firefox, Chrome, etc) :
URLs (aka web addresses) of any relevant observations or pages:
as far as i can tell, the Android app’s Explore page allows you to filter by places that have been defined within the system, while the website allows you to additionally filter by places defined in Google Maps. this provides the ability to search by many more places in the website, though usually the Google places will be represented by only a very rough box (as opposed to a more precise polygon), and there can also sometimes be issues trying to return / match Google places vs iNaturalist places when places with similar names exist in both systems.
i assume that it was intentional to allow the app to search only by iNaturalist places, since that would simplify the development and maintenance of the app and also keep it lightweight on a mobile device.
if there is a particular place that you search for frequently, you could just add that place in iNaturalist (from the website), and then you would be able to use your new place in the app.
it does exist, but this is one manifestation of the Google place vs iNaturalist place matching issue i noted above. there are other reports of cases like this, if you search the forum. some cases are more problematic than other cases, and some are more like actual bugs than other cases. but the solution (workaround?) for these cases usually is:
personally, i almost always filter for locations using Filter > More > Places. the only time i might use the Location box (next to the Species box) is if i can’t find the place the other way, and i don’t want to bother adding (or can’t add) a new place to the system.