Platform: mobile app
App version number, if a mobile app issue:
1.37.2 (638)
Browser, if a website issue:
URLs (aka web addresses) of any relevant observations or pages:
Edit: add the url of obs in screenshot:
https://www.inaturalist.org/observations/338287776
Screenshots of what you are seeing:
Description of problem:
Step 1: click suggest an id
Step 2: view suggested id
Step 3: determine via my eyes that “we’re pretty sure it is in this genus” isn’t even in top suggestions.
I have seen this before in some of my observations. In my experience, it is when the CV thinks it is something that is not expected nearby. If you click the “include suggestions not expected nearby” button, it should show you an organism in the genus Zemeros.
Yeah, this isn’t a bug but it’s a bit confusing. The “pretty sure” suggestion is based on the top visually similar results. The model tries to find a common ancestor of the visually similar results before it filters out taxa not expected nearby from the final suggestion list.
hmmmmmm??? Zemeros is found nearby .
If im understanding this comment correctly… you are saying Zemeros is not found in Borneo (edited)?
Because of quirks in how the AI uses elevation data, it often gets confused by areas with dramatic elevation changes and I suspect the coastal mountains in Borneo might be causing problems. You can see here:
https://www.inaturalist.org/geo_model/549333/explain
that the model expects Z. emesoides in most of Borneo but there are small coastal slivers that should definitely be included but get left out (even though there are already many observations present in some of these slivers)
I’m not sure I can add much to what @yongestation wrote. What I’m saying, though, is that it’s not uncommon for a genus to be suggested in the “we’re pretty sure” section but for none of its child species to be specifically suggested in the “top suggestions” section, especially if you only include suggestions expected nearby.
However, if I go to the observation I do see one Zemeros species suggested:
Weird that the app isn’t showing that.
Appreciate it 
Oh well since it’s a tech problem to debug… I don’t forsee this to be solve in the near future, especially since it is a bug that’s not always reprpducible, as per Tiwane’s final reply.
