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) : Firefox
take your place, and imagine a rectangle around it that touches the most extreme points. If the accuracy circle for an observation breaks the edges of that rectangle, it won’t count as in the place. You need to reduce that location uncertainty
Yup this is my least favorite part of “places” is that darn uncertainty circle. People submitting on phones or just new to iNat have their obs excluded and it’s quite difficult to explain how to fix the problem to people not familiar with the site. Explaining what a “radius of uncertainty” to someone who is not aware there is even a circle is tough. I always thought that the center of the observation circle should be used to attach it to projects, and the circle is for security or obscuring the exact location of the organism. Many rare species get removed from projects from this mechanic and there is no way to force them into a collection project (rare species are often high priorities to detect on projects!). The old school projects allow you to manually add them.
An annoying part of some projects is the default centroid for that place is at the edge of the park and MANY observations get cut off. I had to add a whole second polygon near the park edge that wasn’t in the park to try and accommodate the default circle for that park when searched on iNat. This could be a problem if there are private residences or other parks on the outskirts that are suddenly part of your project when they aren’t on the property at all!
