Screenshots of what you are seeing: I have screenshots, but I won’t show them unless there’s significant confusion about what I’m saying
Description of problem:
Step 1: Go to the “Explore” page in grid view.
Step 2: Click on an observation with an obscure location (it’s not clear to me if this is ALL obscure locations or if it’s just for threatened species that have been auto-obscured)
Step 3: Observe the map shown on the bottom. It will take a few seconds to fully load the obscuring location box. During this loading period, the precise location will be shown.
i don’t see an issue, at least not a privacy issue.
looks like this is a report for Android
i looked at an obscured observation that i happen to know the true location for, and i think what you’re seeing as “the precise location” is just a zoomed in view of the obscuration point, not the true underlying location. the only problem i see is that it’s a little inefficient to display the zoomed in view first and then zoom out to show the entire bounding box. it would be more efficient to just show the whole box view first, and then if for some reason that dynamic zoon couldn’t be achieved, you could fall back to the obscuration point at a default zoom level.
fundamentally, i think it would be impossible for the app itself to reveal the true location of an observation, unless the API response contained the true location, which the last time i checked, it does not. i didn’t check just now, but i assume that no fundamental changes have been made to the API that would cause this sort of problem to manifest all of a sudden.
i’m not sure what the new (React) app does, but if it’s displaying a zoomed in pin before zooming out, that still might be something worth addressing to at least make the app more efficient, even if it’s just a minor issue.