How can I get a list, ideally exportable of only those observations of mine that others have suggested differring IDs from mine and that I haven’t agreed with yet?
I have tried using the approach shown in https://forum.inaturalist.org/t/identifications-search-using-api-v1/26794/2 - my search result is https://jumear.github.io/stirfry/iNatAPIv1_identifications.html?user_id=dineshs&options=idextra&per_page=30&page=1
I want to list only those observations where the “ID vs Obs Taxon” is not ‘identical’
The closest thing to that I know of is checking to see if you’re a maverick, that is, if you have an ID that disagrees with the community ID.
I’m sure there is some extra ‘under the hood’ method though.
first, i think it’s worth noting that folks should never just agree with identifications. any identification you make should indicate that you actually believe a particular organism is a particular taxon. it’s okay to not agree with others’ identifications if you don’t actually know how to identify that particular organism / taxon.
that said, as far as i’m aware of there’s no mechanism that regular users have access to which will have iNat’s servers filter for and return only cases of disagreements or subsequent refinements, etc. the best you can do is to get a set of observations and then filter on your end for what you’re looking for.
if you know how to do a little programming, you can accomplish this by writing something to get data from the API via
/v1/observations and then looking for whatever you’re looking for within those results.
short of that, you can use the page referenced in the first link in your original post. to make things slightly more efficient, you can probably use a few additional parameters:
&per_page=200 to bring back more results per page
&quality_grade=needs_id,casual since these are most likely to have further refinements or disagreements
&idextra_user_id=[your id] – this a special parameter that works only on that page which shows how your identification compares to the observation taxon. in your case, you would look for cases where your identification taxon is not obs. (you would want descendant, ancestor, other, and maybe N/A.)
here’s the specific configuration of that page that i would use based on the above notes: https://jumear.github.io/stirfry/iNatAPIv1_observations.html?per_page=200&user_id=dineshs&quality_grade=needs_id,casual&order_by=updated_at&options=idextra&idextra_user_id=dineshs
note that because the above page includes a parameter to order by update date, once you go through the initial set the first time, in the future, you’ll only have to look through observations updated since the last time you did this kind of review.
Thanks pisum. I wanted a ‘short’ list of those observations where others differed from my initial ID and that I wasn’t able to conclude either way at that point of time. The link that you so helpfully created for me has almost 60% of all my observations listed whereas the actual number where someone suggested an ID that differed from mine and that I didn’t accept is likely less than 10%. Is it possible for me to refine the link that you created to exclude those observations where the value of the field ‘User dineshs ID taxon category’ is not equal to ‘obs’? Thanks once more
thanks but the ‘maverick’ thing only applies if several people (‘community’) differed from your ID but I’m looking for even one different suggestion from my ID
thanks. The first link did look promising but turns out this creates a list of all observations where I changed my ID - either because of someone else’s suggestion or even by revisiting on my own. I’m looking for almost the reverse of this - where I’m yet to change ID despite different suggestion(s)
as i noted previously, you can do it, but you’ll have to do the coding for this on your own. what i’ve described is probably the best you can do with existing tools.
it’s not clear to me why you need a list with only a small set of observations. to me, assuming the point of this is to help you find observations to add IDs to, it seems like it’s easy enough to scan through to page to figure out what needs to be addressed.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.