Community taxon seems off

Bug Reports
1

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): Website

App version number, if a mobile app issue (shown under Settings or About):

Browser, if a website issue (Firefox, Chrome, etc) : Firefox

URLs (aka web addresses) of any relevant observations or pages: https://www.inaturalist.org/observations/149721752 and https://www.inaturalist.org/observations/113872536

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.): I’m probably missing something here, but the community taxon says there’s only agreement at the family level when all three identifiers agree on the genus.

Step 1: Person 1: It’s Pilea.

Step 2: Persons 2 & 3: It’s Pilea capitata

Step 3: Community taxon: Users agree this is Uritcaceae.

I’m puzzled because I’d expect the community taxon to be Pilea.

2

The problem is not with community taxon, but with Pilea capitata, which is connected not to Pilea but to Urticaceae. So Pilea and P. capitata are concerned as sibling taxons.
You have already flagged P. capitata, so its resolving should help.

4 Likes
3

Flag now resolved

2 Likes
4

Thanks, All, for the feedback and resolution. I put in the taxon flag after posting my bug report, but I’m still figuring out how taxa and community taxa work on iNat, so I wasn’t entirely sure if I’d found the problem (or if there was really was one). I’m glad it was an easy fix.

1 Like