There are a number of discussions going on about inappropriate species being suggested by the app and accepted by novice users, particularly outside of data-rich areas such as California. The computer vision suggestions are based on visual similarity, and while several changes have been made to addr…

Hi all - we just released a minor change today on the web to remove non-nearby suggestions from the computer vision suggestions by default. We released something similar on Android a week or two ago and a similar change on iOS is coming soon. We hope will reduce the frequencies of people choosing s…

The CV does know T. canadensis, so I’m really not sure why it suggests bacharidis here. But otherwise yeah. [image] rupertclayton: I guess if there were lots of genus-level Trirhabda observations marked “No, it’s as good as it can be” then the CV training and suggestion algorithm could pay atte…

I’ve brought this up several times on the forums, and I’ll do so again here… in its current implementation, the Computer Vision IDs greatly diminish the accuracy of the data on iNaturalist, such that experts are dissuaded from contributing. Here’s a twitter thread from a contributor, Dr. Derek Henne…

I just wanted to give a quick update on functionality changes to better use location in CV suggestions. On iNaturalist, we currently use location data to boost visually similar species that are also seen nearby, but we don’t do anything to demote visually similar species that aren’t seen nearby Ke…

There are two competing streams for ID on iNat. A garden plant, not marked as Casual, so iNat offers visually similar and nearby - which is not necessarily helpful or useful. Especially to someone new to iNat. A (genuine) wild plant - where nearby is more useful than visually similar. I see…

One simple thing that may help in the interim is removing the language “We’re pretty sure this is…” To inexperienced users, seeing that from the AI is difficult to distinguish from “This is…” Pretty much every time I upload a pile of images I get a wildly incorrect “We’re pretty sure this is…” Ma…

[image] dlevitis: One simple thing that may help in the interim is removing the language “We’re pretty sure this is…” To inexperienced users, seeing that from the AI is difficult to distinguish from “This is…” 100% agree with this; I think a lot of people associate any kind of AI or computer…

@loarie , thanks for sharing about this update. This seems to me like a reasonable solution, and I’m looking forward to seeing the implementation. It will help a lot! I like the idea of having the button to override location restrictions - that may also help for IDs of common (mostly introduced) spec…

Thank you. It is funny to me when I see an ID for Sierra Juniper (J. grandis) in Virginia or in Poland as well as a suggested ID of J. chinensis in the middle of Idaho.

This looks very promising @loarie , thanks to you and the iNat team! Let’s see how it plays out. Is there any way to compare its effect systematically, such as proportion of computer vision suggestions with later disagreements before and after? Disagreements would have to be within x months because o…

I agree, looks promising thanks for doing it. To address Loarie’s concern above that “captive/cultivated” species may be misIDed at a greater rate with this change, what about having the default toggle to include visually similar taxa when the observer checks the box that the observation is captive…

Better use of location in Computer Vision suggestions

Feature Requests

Topic		Replies	Views
Species Suggestions for the Wrong Continent General	90	10866	July 21, 2020
Some 'interesting' AI suggestions of late General	41	2168	September 10, 2022
Change computer vision suggestions to only above species level Feature Requests	31	3081	March 26, 2019
CV suggestions are bizarre, not "visually similar" at all Bug Reports	65	2184	February 2, 2023
Problems with Computer Vision and new/inexperienced users General	132	5980	October 28, 2021

Better use of location in Computer Vision suggestions

Related topics