Umbrella Projects - Trusting Obscured Observations

You can’t join and trust a whole umbrella project, so for umbrella projects with many collection projects, short of having the observer join & trust say 50 collection projects - is there any way they can run a query of their own obscured observations that can be shared? Any other work around?

based on what you’ve written, it’s not clear what your actual problem is. do your observations not fit the criteria of the various projects? are you making the proper distinction between geoprivacy and taxon geoprivacy? are you making the proper distinction between obscured and private?

You can easily configure a collection project to allow people to trust the administrator/owner of that project with true locations of obscured (either type) observations. Unfortunately you can"t do that with an umbrella project and allow people to trust all of the included projects. It’s simply unrealistic to expect anyone to join and trust 50 individual collection projects.
I can see my own taxa obscured observations and I’d like to be able to filter on just those in an umbrella project and share the results with trusted people. e.g. I didnt realize that Piping Plovers are obscured until it didn’t show up in my park project - I’d like to filter all of my taxa obscured observations.
I’m not confused about private vs obscured, I’d simply like a way to filter out which of my observations have been obscured and maybe allow others to do likewise.
I just don’t see any way to conveniently allow people to trust an umbrella by simply joining just that main project.


This shows up under your membership for an umbrella project - and its not correct. So how would someone trust an umbrella project without joining all included ones?

to filter for obscured observations (those that you obscure yourself), you would filter using geoprivacy=obscured. to filter for taxon obscured observations (those that are obscured based on taxon setups), you would filter using taxon_geoprivacy=obscured.

if you want to change the way the system works, you can always write up a feature request to cascade membership settings, if one doesn’t already exist. to me, it seems like a technical non-starter, but there’s no harm in asking.

working within the existing system though, if there’s a situation where you would want to cascade membership settings to 50 subprojects, i would think that maybe you’ve started with too many subprojects. maybe you should have consolidated some of those to begin with.

Ok, taxon instead of taxa! Good. That works, but the location names are still obscured. How would I share this and show which park it was seen in?


I didn’t realize that some of these were obscured. I would have thought that I could see those locale names.

you download the data, including the private location description, or extract it using the API.

1 Like

I can do that, but it’s unlikely I could talk anyone else into going to that trouble for their own observations, even if they were inclined.
I’m really looking for something simple like is available for collection projects - anything?

I guess what I’m looking for is a simple, sharable query that anyone could execute.

if they can’t be bothered for a simple task, then they can’t be bothered.

do you really need 50 subprojects?

https://www.inaturalist.org/projects/south-carolina-state-parks-inaturalist

Unfortunately there is no way to consolidate this. I’ve actually asked about something like this as a feature request - they wouldn’t post it.

I’m absolutely NOT asking to redo the system - I would simply like to reach out to some folks and allow them to send all their taxon obscured observations per park.

I guess i could make a separate single collection project consisting of all 50 places and let people trust that?

https://www.inaturalist.org/projects/national-park-service

The fact that visitors can’t just trust the main umbrella project seems like an oversight. There are many more just like this.

Here was the response to the previous request:

an umbrella project can contain any project within it, whether or not the umbrella owner owns or admins any of the subprojects, so its not possible to allow someone to trust subprojects of an umbrella project - there are too many potential security issues and inconsistencies, I’m sorry.

1 Like

Did you read this post? i wasnt asking for a way to trust a whole umbrella project. I just think its a mistake to not have some way of sharing obscured observations from umbrella projects short of trusting the whole umbrella projects. Not sure what that would look like, but … individuals should have a way to filter on their own obscured observations and share that with anyone they want without having to jump through alot of hoops. Just my opinion.

I was responding to @pisum.

Ok, missed that details. Thanks. I guess there is no simple way to accomplish this.
I gave it a try, moving on.

Admittedly, I skimmed, but creating a new project which is filtered to all the same locations as an umbrella would be a viable workaround. Then users would just need to add trusting with obscured observations for one project.

2 Likes

I created it, now i just need to get people to join/trust it! Not pretty, but it should work.

1 Like