I am working on a personal project with another naturalist trying to document a site as thoroughly as possible before it gets developed.
I am aware of the trick to see your personal unobserved taxa (&unobserved_by_user_id=rlhardin), but is there a way to apply this to a whole project so me and the other person can collectively see what we have not observed at a particular site?
Yeah, you can just go to the projects observations tab, open the identify modal, remove “/identify” from the link, and then add that URL parameter. If you want to link a project I can show it in more detail.
I appreciate your help. Adding that URL parameter allows me to view the contents of the project excluding my observations, but maybe I’m doing something wrong. In other words, is there a way to stack multiple users into the string, ie. &unobserved_by_user_id=user1, user2, user3? This would be just as useful and solve the same problem.
if i’m understanding you correctly, you’re effectively trying to compare 2 sets of data:
species observed (by anyone) in a particular place A
species observed by you and another person in place A
if that’s correct, you can’t really do this in the Explore page as one query. however, there are existing tools that may help you get this information relatively easily.
if there are less than 500 species observed in the place in total, you can use the “experimental” compare tool to handle this: https://www.inaturalist.org/observations/compare. (you could also break up the species into subsets by, say, kingdom or family to work around the 500 species limit.)
there are other ways to get what you’re asking for, of course, but i think the above 2 methods are going to be the fastest way to get the answer without creating something on your own or jumping through many hoops.
have you actually tried this? does it actually produce a result that you expect?
even if there was only one user to account for, would this be the right parameter to use in this case? that parameter seems to operate based on species the user has observed anywhere, even if you limit the core query to a particular place, i believe. so i don’t think that would get:
By the way, unobserved_by_user_id means “species never observed by the user”. It doesn’t take into account current project or other keys in query. So if you want to check if you see something in special area, timespan or project, this key could give you wrong results.