I’m not sure this is what you’re looking for, but maybe? @Loopy30 It’d allow you to see on your mobile phone what you haven’t already observed at a park or preserve that has been observed there by others.
Unobserved within Project - Use this Instead
You can click on user and project name to search for and change the user/project. The observed/unobserved is a toggle. The species name, when clicked takes you to a grid of OBS.
No, that example is essentially the “not_observed_by_user” filtered by the geographical boundaries of the park.
What I am looking for is the generation of a list of all those species observed by all users in a wider area (eg. county/province/state), but not yet seen by any (not just individual) user in a specific area (eg. park/project/city etc). Preferably, this list would be ranked by total observations.
I would look at some of the posts in these discussions:
https://forum.inaturalist.org/t/way-to-see-unobserved-species-for-project/38200
https://forum.inaturalist.org/t/a-query-that-will-find-unobserved-species-in-a-smaller-place-that-exists-inside-a-larger-place/44807
For example, this is the compare tool, showing the bird species seen in Ottawa, but not seen in the Petrie Island project.
Oh, actually here’s another option that I don’t think was linked in those topics – this example shows animals see in Ottawa, but not seen in the Petrie Island project.
The reason it’s only listing animals is because there is a limit of 10000 species and Ottawa has a little more than that. But the limit to the compare tool I showed above is 500 species, so 10000 is comparatively quite large.
This is useful, thanks. The 500 spp. limit was quite limiting…
Question about the limits of 10,000 and 500…
Did the first compare tool example choose to go with a lower limit of 500 since the page might influence the user to enter several queries successively (each limited to 500)? I only ask because I’m working on something somewhat similar and may need help deciding what the limits should be. The observation endpoint seems to allow 200 per-page with a max limit of 10,000… but it would be unreasonable if too many users were doing this too many times (and I think it’d hit the limit of transactions per-day too quickly anyway… unless that’s per user rather than per app).
I don’t know why they did it that way. Without looking at the code, I would guess it’s an unpaginated call to observations/species_counts.
