All location options for Buenos Aires city redirect to the Buenos Aires province instead

Bug Reports
1

Platform: Web (Works properly in Android app)

Browser, if a website issue: Firefox

URLs (aka web addresses) of any relevant observations or pages:

https://www.inaturalist.org/observations?place_id=7860

Screenshots of what you are seeing:

20250820 - inat issue caba
20250820 - inat issue caba1173×636 89.6 KB

20250820 - inat issue caba 2
20250820 - inat issue caba 21159×531 104 KB

20250820 - inat issue caba 3
20250820 - inat issue caba 3632×653 143 KB

Description of problem:

The Buenos Aires Province and the Buenos Aires City are two independent areas, and the first does NOT encompass the other. In Firefox searching with the site in english, any of the displayed options that can be selected for the city (including: “Ciudad de Buenos Aires”, “Ciudad Autónoma de Buenos Aires” and “CABA”) redirect instead to the location Id 7860, which is the Buenos Aires Province and does not include the city.

Users from this city are shown by default a third, non-formal option (ID 135921) that encompasses both the city and the surrounding metropolitan area (This is not a complain, but an explanation of why this default area is not the city).
For some reason, searching for this metropolitan area is also now bugged, and redirects instead to a huge custom boundary.

This issue was not happening a couple of months ago.

Step 1: Go to either the “Explore” page, or to “Observations > View all” from a taxa page

Step 2: Try to filter the location as “Ciudad de Buenos Aires”, “Ciudad Autónoma de Buenos Aires”, “Caba” or “Buenos Aires city”

Step 3: See in the map that the location displayed is the province, and excludes the city

Thanks in advance for looking into it :slight_smile: I was not able to find a curator option for default places.

2

This is due to a long-standing issue between Google Maps and iNat, relating to how information is passed between them.
(Here’s just one previous discussion on the same general topic.)

This will presumably be fixed when the Explore page is rewritten, but until then, it’s unlikely to be changed. The recommendation is to use Filters->More Filters->Place

image
image1568×1040 103 KB

3

Thank you @jwidness , the workaround works, I will mark it as solved and see if I can find how to flag the other custom boundary for curation.

The weird thing is that this was not happening a while ago! Something may have changed in that communication recently.