When the original iNat app was first launched the app was unable to rule out suggested IDs by location, as a result there are a number of mass mis-IDs we are still dealing with. Examples are Rhododendron ponticum, not a species found in the wild or regularly in cultivation in North America, but the …

[image] edropkin: the AI was programmed to only select from likely IDs by region. Unfortunately it seems like this beneficial feature was forgotten in the iNat next release are you using iNat Next on iPhone? Did you have any screenshots you could share of this? When I open the app and try to …

also could you clarify why you believe this is an iNat Next-specific issue, re: [image] edropkin: iNat next keeps suggesting Parthenocissus dalzielii as possible IDs for North and Central American plants so now that species is being reported in North and Central America even though it is not fo…

I use iNat Next on the iPhone, and I’ve noticed that sometimes I don’t have the “Use Location”/”Ignore Location” option, and sometimes that it defaults to species that aren’t local at all. I’m not sure if this is a new issue with the app? I feel like this has only been happening recently.

This is a good point, I just assumed this was an iNat next issue as I have experienced iNat Next giving extremely unlikely/impossible IDs several times since it’s inception the way the original app used too. Here’s one from yesterday, I’ve seen bad ID’s with way higher percentages than this on iNat …

I’ve felt like I’ve needed to crop photos more heavily to get reasonable CV suggestions than I used to, but I’m not sure if that’s a more recent CV model thing or an iNat Next thing since I haven’t systematically tested the same photos on iNat Next vs. the iNat Classic app. It might be that if you c…

Looking at the squirrel observation in question , S. carolinensis is the #1 suggestion (using the standard CV model via the browser client). I do think the large amount of asphalt and deep shadows are the reason for the disparate suggestions on this one. Gallirallus australis is suggestion #5 (and n…

Users should always be cropping photos and adjusting brightness/shadows. It’s the most basic form of photo editing and can be done on the phone or on the computer. A little-known fact to users is that iNaturalist resizes the photos to 2048px on the long edge. On a 12MP photo (3024x4032), that 300px…

Yes, I’m aware of this and crop my images. But my workflow for phone photos is usually to take the initial photos in the app so I can have an observation to make field notes in and have the uncropped photos for context, save the observation, and then crop the photos and add them when I’m not in the …

The “asphalt issue” occasionally creaps into the ID misidentifications of many urban/suburban species. In Texas, we’ve seen this arise in photos of squirrels, white-tailed deer, distant coyotes, and even some plants like Ashe Juniper. CV is “learning” that a lot of pavement, a curb, or even parked…

Yep. When the photo is mostly background, the CV is mostly looking at the background. Just another of the many issues with CV that have been brought up on this forum.

INat Next computer vision contributing to mis-IDs

General

Topic		Replies	Views
iNat AI bizarre misidentifications/suggestions Bug Reports	24	1221	May 24, 2024
Better use of location in Computer Vision suggestions Feature Requests	53	8800	April 13, 2021
iNat iPhone app not able to ID critters when photo is cropped by iPhone - help me please? General question	9	392	May 11, 2024
CV suggestions are bizarre, not "visually similar" at all Bug Reports	65	2237	February 2, 2023
Anyone else noticing a big increase in outlandishly bad IDs? General	22	3148	July 27, 2019

INat Next computer vision contributing to mis-IDs

Related topics