in the circular boundary case, lat and lng are unrecognized parameters for that API endpoint. so you’re getting the same nonsense results as you would get if you didn’t specify a search area: https://api.inaturalist.org/v1/places/nearby.
…
a note for developers looking at this: is there a reason that the nearby places request is made any time the map view changes? seems like it would make more sense to do this only when the Places of Interest button is actually clicked.
(it seems like the request is relatively slow and takes a couple of seconds to return an answer, and maybe the background loading is an attempt to make the page seem more responsive when clicking the Places of Interest button? but it seems like clicking the button would be a relatively uncommon activity. so all those background requests seem like they would just be eating processing time.)