Automate geoprivacy with user-defined geofences

Yes, I’d like this automatic geoprivacy too.

2 Likes

with an easy way to retrospectively add it!

4 Likes

This is a great idea! It always bugs me that I have to remember to hit the obscured geoprivacy setting when submitting observations near my house. Obviously not a big problem, but it would be nice if there was an easy solution.

9 Likes

One could even take it a step further and allow a creation of a privately visible ‘Home’ place (or maybe several) which would not only auto obscure, but also make a special ‘home species list’ and show some special stats too, and make it easier to share them on social media (without revealing location) or show them in a profile). Help get people excited about the biodiversity in their own backyard - what’s not to like! I currently do this with manual obscuring and a traditional project but a ‘home’ space would be way better.

16 Likes

Agreed. I am moving, so I recently used the batch edit function to set the geoprivacy to ‘open’ on the observations around my home. It was clunky but worked. I would rather just be able to move the geoprivacy fence location and perimeter size and let iNat obscure what falls inside.

3 Likes

OK, brought it up with the team and here’s our proposal:

  • 1 geofence allowed per user
  • it can’t be any bigger than something like a football or soccer field
  • when you upload an observation made in that area, it automatically is obscured or made private (whatever you’ve set it to do) upon creation, but you can change the geoprivacy afterward.

Obviously not exactly what everyone wants, but should solve the problem about a home place.

13 Likes

Looks good to me!
Would it be possible to have this act as a secret place/location filter as well? I would like to be able to see my “yard list” but not have to make a public place to collect the observations.

7 Likes

I’ll see if this is possible, that’s a good suggestion.

2 Likes

Yeah it would be awesome to be able to have a yard list. I’m hoping it can be at least an acre and a half in size since that’s our land. We are pretty rural so I know it’s larger than average. But I don’t really know how big sports fields are… not a sports guy.

5 Likes

I thought we already had it for people who wanted it

people can choose to obscure of course, but there are not what is being proposed here: private ‘home’ places that can come with a species list/life list AND obscure a user’s observations when they post there, for their privacy. I think rolling out a home place’ with those features and a few other stats could be a fun way to encourage people to do small conservation activities on their own land such as planting pollinator plants, native species, starting a rain garden, etc etc.There used to be a ‘map my yard’ site (i think Cornell) that was really neat and let you do stuff like that but sadly it lost funding and went away

3 Likes

What I would prefer instead of obscuring, would be to change the location to a random spot somewhere, say, 1 km away, then change the accuracy to, say, 2 km. By comparison, obscured locations can cover a range of hundreds of square kilometres.

Here’s an example:

https://imgur.com/VegVtvA.png

Hmm, on other Discourse forums posting an image URL will display it automatically (saves on server costs). On this site you need to use this format: [<img src='//cdck-file-uploads-global.s3.dualstack.us-west-2.amazonaws.com/business6/uploads/inaturalist/original/2X/0/0377ecdae93c00a7200a0621c1ed72455fe4f93f.png' alt='https://imgur.com/VegVtvA.png'>](https://imgur.com/VegVtvA.png).

Edit: then the system goes and downloads local copies of the images and edits my comment with a local link. So much for trying to save on server costs!

1 Like

What if someone is fortunate enough to own property of that size (or bigger)?

1 Like

In the case of a farm, for instance, they could choose the “home paddock”? But seriously… most of us will typically have a town section etc, and a 1/4 acre would be on the large size. A football field would be a good sized lifestyle block, but I think farm owners etc have exactly the same issues as we have…

My impression is this could be a compromise or “easy implement” option, so there may be potential to re-address it down the track?

in vermont (which is rural but iNat is very popular) many users live on a few acres. I guess i am not sure how that translates globally - what the median and mean property size is (including renters) but i do want to subtly remind the devs that a lot of people don’t live in big cities and do have interest in a larger 'home ’ parcel. I wouldn’t see any reason to limit it to such a small size (more than say 5 acres) unless there is a compelling coding-side reason to do so, and in any event if it’s smaller than maybe 2 acres (to have a buffer to account for GPS precision and such) i probably won’t use it and i imagine many others in Vermont also would not.

8 Likes

In rural upstate NY, same deal. Modest small home with some acreage.

1 Like

My previous suggestion I posted about on the Google Group was to just save those locations (which we do have now, and it’s great!), and have all observations you make from that saved location all obscure to the exact same spot. That spot should be within an area that would allow it to still be visible on the proper local checklists, yet still retain privacy. If the user can pick the obscured spot or at least the encompassing places for the spot then they can ensure that. The current obscuring pushes half of my home observations outside of my county so that they don’t show up in searches or lists for it anyways. Let the user also set the publicly visible label for the saved place to something they are comfortable with, but that is still descriptive like “Username’s Home, Town, State, Country”.

That would do away with the giant rectangle of hundreds of obscured observation markings blocking out large areas of the map over active users’ homes like mine and many other users I’ve seen. I don’t really see the point of that, unless it is to just indicate lots of observations in the area. The markers let you know that they aren’t actual locations anyways, so what is the purpose of having it look like buckshot on the map.

This could work well with the automatic geofencing privacy as well. Set-up a home area boundary and give it a private and public label. You can either let the gps put observations in that place or select it manually. Any observations you submit for that place are visible to you with the actual location and your custom private label like it works now. Other people would see all those observations as someplace nearby all at one point where they can be included in the correct public lists, and not obscure the map for other purposes. There could even be a different icon for displaying many aggregated observations for these places in searches or species page maps and such. It could have an icon flyout for it that just says something like “User’s obscured spot with 85 monarch butterfly observations”.

5 Likes

this is what i do. i just manually select Houston, TX, which points to a spot in the middle of downtown, and bump up the range of uncertainty. i know where i live. so if i ever want to go back and change any of those, i can go back to observations at that point and find them relatively easily.

2 Likes

i think you might want to test this out on some real-world cases. i know GPS technology is pretty good nowadays, but sometimes i think even the best non-professional devices might be off just a bit, and it would be unfortunate if that led to a the creation of sort of a donut ring of observations around a an otherwise obscured geofence.

2 Likes

i used to do this for stuff at my house, and it resulted in a smaller uncertainty area (i don’t care if people know I live in the Montpelier area, and everyone who cares knows that anyway, i just didn’t want my address on here and easy to find).I was doing that because the points used to obscure in a circle around a central point and with lots of observations it was easy to see where the center was. I stopped when the obscuring method got updated because i didn’t like creating ‘imprecise’ data and liked to know where on our land i saw things, plus i wanted to be able to share that data with a conservation organization. But… I think the ‘big circle’ approach is mildly frowned upon but not wrong. The problem is it may be harder to filter out when you filter out obscured things, but there are some filters for low precision observations now too.