Yeah things get buried in long threads or if not consolidated, confusing with multiple threads about the same thing. Either way.
I agree that National listing/protection should be considered in decisions to obscure or not obscure. My only caveat is that such decisions not be automatic, but instead get considered case-by-case to make sure that obscuring iNat locations does in fact
and not inadvertently hinder them. It all depends on what the actual threats are for a particular species. In the case of substantial poaching threats, locations should definitely be obscured. In many cases this will already have been done because of similar concerns globally. But where poaching is a more localized national issue, then that is certainly a reason to obscure within that nation.
I agree, but there are some cases nationally where observations should probably be obscured by defaultā¦ and the other way, in some areas certain species otherwise obscured by default should not be.
For example, globally Burmese Pythons (Python bivittatus) is listed as Vulnerable on the IUCN Red List, but is considered Endangered in several countries in SE Asia due to poaching. However, in Florida in the US it is a prolific invasive species.
In cases like that a regional default approach makes more sense to my mind. By default obscure it in its native range, and in areas adjacent to that (to reflect the fact that range maps are often incorrect), but in the southern US states where it is a destructive invasive species ensure that the default is not to obscure observations.
However you slice it, itās a complicated subject.
In my region poaching is a massive problem, complicating things even more.
Iām really not confident this is a viable approach to get the stuff that really needs obscuring protected. You are talking about a manual review of tens of thousands of national or regional listings. Maybe even hundreds of thousands.
As it is right now flags being added by users to highlight missing listings or candidates for obscuring get ignored and never acted on by curators. And these number in the dozens, way below the volume a one off approach would generate if followed through on. My sense is the primary reason they get ignored is the lack of guidance or a standard framework to direct how to proceed.
And a one off approach still brings back the issue of inconsistent decision making being made by different curators applying different standards etc.
Iām sure Iām seen as just repeating myself, but a consistent approach to take is far cleaner. Make it like where we are going with taxonomy. This is the starting point, and then look for and discuss deviations. And Iām uncomfortable with that starting point being everything is open.
Just to flag it here, fyi:
GBIF expects to release a new version of Arthur Chapmanās guidance on publishing sensitive species data for community review within the next few weeks. This guide will update and replace the one Arthur and Oliver Grafton prepared in 2008.
I just want to link to this discussion on twitter, repeating concerns that obscuration is not doing enough to protect certain species, especially herps, from poaching.
https://twitter.com/sebastianaronh/status/1266661789179224064
Ugh some of the comments there are annoying. There seems to a widespread idea that the staff have insisted on not implementing protections for sensitive species and user privacy. In addition to comments like that in that Twitter thread and mentioned elsewhere on the forum, I saw this comment on facebook recently:
FYI, iNat submissions are commonly used by poachers to illegally collect reptiles and amphibians, and they know this but refuse to do anything about it (such as censor sensitive species, which ebird does to prevent poaching/ harassment for some species).
He never replied to comments with more details about those claimsā¦ eBird doesnāt even let you hide the location of your house like iNat does.
I donāt want to get too into it on here but thereās a contingent within the herper community (edit: not including the person who made the linked tweet!) with alterior motives that resurfaces this exact same claim every year or two. I donāt know when to inform and when to ignore. I get drawn into arguments too easily.
Iām assuming that in this case the person had a good-faith concern about large-scale collecting of a non-threatened species. I informed him that itās possible to flag a species and explain why it should be obscured in an area, and if the case is convincing a curator can do that. He responded positively.
Some of the comments reflected a lack of knowledge about how iNat works, and that observations of many species are obscured. Like many others, I think this can still be refined further to un-obscure species that are not threatened by having their locations public, and to obscure certain taxa in certain places where open locations poses a real problem. I think the best approach is to invite people with concerns to participate in the community.
Sorry, I didnāt mean to imply the person who made the first tweet was part of that contingent. I donāt think that at all.
No worries! I wasnāt sure if you meant the same person or others. I think there are real issues here, and there is a balance to be struck between protecting species and maintaining the usefulness of the data (which in turn can be helpful for the conservation of species). From my perspective, iNaturalist is continuing to make progress towards perfecting that balance.
As a relatively new user, I am struggling to wade through all of the information on the forum about what the current process is for handling species that are regionally significant/vulnerable.
I can see the general guidelines about geoprivacy (https://www.inaturalist.org/pages/help#geoprivacy), and also the curator guidelines about how/when to edit the geoprivacy on a taxon (https://www.inaturalist.org/pages/curator+guide#geoprivacy).
However, it is clear that this discussion is far from over, and I would love to see a summary somewhere of the current status so that I donāt need to read through pages and pages of a forum thread and find information that probably isnāt current anymore anyway. Perhaps in a wiki?
For example, how are we going with feature requests that were mentioned over a year ago in this thread? Have they been implemented already? Have they been rejected? One that comes to mind is a better system for documenting who/when/why the taxon geoprivacy settings are being changed, and making this visible. Has that been rejected in favour of the flag system?
And what is the latest thinking on regional vulnerability? Is there going to be a way of adding that? Also, it has been mentioned a couple of times in this thread that we donāt want to reopen the discussion about whether things should be obscured or not, but I havenāt read those, and although I donāt want to spend hours sifting through the threads, I would love to see a summary of pros/cons. Is there such a thing that someone could point me to?
I would be quite happy to get either/both of those things started (a wiki on the current processes for handling geoprivacy on iNaturalist, and a wiki on the pros/cons of geoprivacy in general), but Iām not even sure if maybe it already exists somewhere (please provide links if you know of such things), or if there is a better way of handling it, and I would definitely need a lot of support with editing the content, as I am not a power user yet.
Thank you everyone for your willing and thorough input into this forum! I am so thrilled to have found it and to be a part of it!
When I view all my records in the Map view, the locations of obscured records are obscured from me (the exact location is visible on the map for each record though). Often I want to revisit a record. Ideally, I would use the explore function in the map view to locate the record (rather than having to scroll through all my records to find it). Iāve just discovered that, for the records with obscured geoprivacy, the locations are obscured for everyone, including me!
Is it possible for me to see the exact locations of my own records on the Explore/Map view but they remain obscured for everyone else?
I see my options are to change the location privacy to open for all my records (which I donāt want to for sensitive species) or start using Google Maps to store my records that I want to revisit.
Are there other solutions? @nicklambert, any thoughts?
Short answer is that I donāt know of a way to āunobscureā your own obs pins in map view.
When I have this issue I generally use the filters in explore as much as possible, I also zoom the map in to a point Iām confident and hit the āredo search in mapā orange button which reduces the number of records Iām looking through. I switch between map view and grid view to find the record. This works for me most of the time, but yes you are right, the obscuring makes it tricky sometimes.
I do two other things to find records:
- sometimes I fave my own obs if I know Iām going to need to look at it again sometime
- I also use the iNat Jounrnal entries to store links to obs I want to revisit in the future, for example: https://www.inaturalist.org/journal/nicklambert/27380-id-tips-reference-links-mainly-for-me"
Sorry I canāt be of more help!
Cheers,
Nick
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.