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): Website
App version number, if a mobile app issue (shown under Settings or About):
Browser, if a website issue (Firefox, Chrome, etc) :
Description of problem (please provide a set of steps we can use to replicate the issue, and make as many as you need.):
Step 1: Search for observations of Black-capped Petrel
Step 2: Location is auto-obscured due to conservation status
Step 3: Full GPS coordinates are given… probably not an issue in this case, since they’re out at sea, but certainly defeats the purpose of obscuring the location in the first place.
Thinking about this, I suspect that fixing this completely would involve oceanic places, currently not something the site’s set up for. A possible work-around might be to utilize just the integer portion of the coordinates.
as far as i can tell, the coordinates displayed are still the obscured coordinates, not the true coordinates. so i don’t think there’s any bug here.
that’s correct. because there are no standard places associated with these coordinates, these observations get labeled with the coordinates rather than a standard place name.
Yes, they appear to be the obscured coordinates here. I don’t think this is a bug but intended behavior, so I marked it as solved. Non-obscured oceanic records show the same behavior. You could make a feature request, but I doubt that making oceanic places would be considered for implementation as they are so large though some other solution might be.
Ah, okay – I didn’t realize that those were the obscured ones. I wasn’t worried about observations like mine, actually at sea, but rather if there were nesting islands small enough to not show up as actual places.
