Obscuring geolocation by date?

[scharf]

I care about protecting threatened species. This argument can go both ways.

[pisum]

yeah, i’m not saying your perspective isn’t valuable. i’m saying that’s not the perspective that drives my own objection. by the way, i’m not saying simply don’t do anything. there are probably ways to get the best of both worlds, though it would be no simple exercise to achieve that.

[clay_s]

I just hope I’m aware when it occurs to my observations, so I can delete the observation causing it.

[jdmore]

@pisum

this other option, which i’ll call datetime obscuration

Based on the proposal, I think it would be clearer to just call it time obscuration. The date portion of the datetime would not be hidden.

[er1kksen]

I certainly do too, but there have to be better ways to do it.

I currently do the same thing Charlie describes: uploading truly vulnerable obvs on a different day, with altered date and time of observation, and location private. If there’s a way to automate that, awesome! But again, an approach that obscures 75% of my data for the sake of some NY S3-S2 species that are not in danger and abundant in my area seems like a pretty obviously problematic way of going about it.

[charlie]

In the unfortunate event it ever happens I’d request a one time optional auto purge of all auto obscured observations I’ve uploaded. A day of 50 georeferenced species is more valuable for most ecology/management purposes than obscured locations for 51 observations including some rare sedge no one would ever poach anyway. Etc. and yeah for most cases I’d stop posting all of those species, start deleting the date, or create an alt account for them.

But no point getting riled up over something that hopefully won’t ever happen.