Establishment status for sub-genus taxa

When performing a search based on establishment status, observations at the infrageneric level (like section or subgenus) don’t seem to make it into the search. For example, searching for all observations of section Piperia native to California yields 3044 observations all at the species level, but removing the “&native” produces 3452 observations. Also, searching for all observations of section Piperia at the species level yields exactly 3044 observations.

Platform: Website

URLs (aka web addresses) of any relevant observations or pages:

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: Observations of Piperia native to California: https://www.inaturalist.org/observations?place_id=14&subview=map&taxon_id=132363&native

Step 2: Observations of Piperia in California: https://www.inaturalist.org/observations?place_id=14&subview=map&taxon_id=132363

Step 3: Observations of Piperia at the species level in California: https://www.inaturalist.org/observations?hrank=species&place_id=14&subview=map&taxon_id=132363

Is there a way to add establishment statuses for taxa at a rank within genus? It seems that at least genera have some sort of native establishment status even though it’s not explicitly on their taxon page; for example, searching for Spiranthes in California yields 911 observations (https://www.inaturalist.org/observations?place_id=14&subview=map&taxon_id=50741) and adding the native designation yields 908 (https://www.inaturalist.org/observations?place_id=14&subview=map&taxon_id=50741), and searching for Spiranthes at the species level yields 827 (https://www.inaturalist.org/observations?hrank=species&place_id=14&subview=map&taxon_id=50741).

Also, I’m not sure why there are 3 observations not included in that second Spiranthes search, but I managed to track down one of them: https://www.inaturalist.org/observations/36007440

2 Likes

i didn’t look super deeply into this, but just superficially, it sounds like the same problem described in other threads (probably related to reindexing issues):

1 Like