Wrong taxon returned

Please fill out the following sections to the best of your ability, it will help us investigate bugs if we have this information at the outset. Screenshots are especially helpful, so please provide those if you can.

Platform (Android, iOS, Website): API

URLs (aka web addresses) of any relevant observations or pages: https://www.inaturalist.org/observations?place_id=any&taxon_id=47570&view=species

Screenshots of what you are seeing (instructions for taking a screenshot on computers and mobile devices: https://www.take-a-screenshot.org/):

Description of problem (please provide a set of steps we can use to replicate the issue, and make as many as you need.):

Step 1: Open “All observations” page and search “Populus alba”.

Step 2: Delete default location if there are any

Step 3: Look to species tab

The problem is this: I have observations of Populus alba (id 47570), but an inactive species Populus alba pyramidalis (962906). If I narrow the search by adding a location or project, I get the correct Populus alba.
PS: I suppose if I re-identify the observation with Populus alba pyramidalis the problem goes away, but I’d like the underlying problem with the API to be fixed.

Upd: If I try to add taxon_is_active=true to query, I don’t have correct species on observation page https://www.inaturalist.org/observations?place_id=any&taxon_id=47570&view=species&taxon_is_active=true

1 Like

Has been resolved meanwhile?
I only find Populus alba.

I can reproduce exactly what is seen in the screenshot using either the URL above or by doing a fresh search on the explore page

Inactive taxon - needs to be flagged for curation.

Weird, we’ll take a look.

With a single obs

I’m not sure if there should be any flags. It is already marked as inactive.
I think the problem is rank of the taxa (species, not subspecies) and because it is child taxon of another species, something wrong is happened.

1 Like

is why a curator, or iNat staff, needs to resolve the issue.

I tried changing the rank from species to subspecies, but it appears not to have affected this

Perhaps iNat staff needs to resolve the issue?
@tiwane ?

It’s fixed now. Not sure if it took some time for my changes yesterday to percolate thru the system or if the admins did something.