You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we save taxa to the local database from taxon search and when the app loads, we only save the search results, which tend to be leaf taxa, and not their ancestors, which means the local taxa table tends to be missing higher level taxa. This means that even if your local database as a row for Argentine Ant, it probable doesn't have a row for Ants, frustrating those of us who want to observe ants while offline.
We could address this with the existing API by making an additional fetch request for every search result to get those ancestors (ancestors don't come with the /v2/search results), but that would probably make #2277 worse.
Alternative, we could work with the web team to optionally include ancestors in the search results, or maybe make an option to include a full tree in search results in addition to the actual results.
The text was updated successfully, but these errors were encountered:
Note, inaturalist/iNaturalistAPI@9612615 added the include_ancestors param to /v2/observations_species_counts and the include_taxon_ancestors param to /v2/search, both of which will be useful here.
When we save taxa to the local database from taxon search and when the app loads, we only save the search results, which tend to be leaf taxa, and not their ancestors, which means the local taxa table tends to be missing higher level taxa. This means that even if your local database as a row for Argentine Ant, it probable doesn't have a row for Ants, frustrating those of us who want to observe ants while offline.
We could address this with the existing API by making an additional fetch request for every search result to get those ancestors (ancestors don't come with the
/v2/search
results), but that would probably make #2277 worse.Alternative, we could work with the web team to optionally include ancestors in the search results, or maybe make an option to include a full tree in search results in addition to the actual results.
The text was updated successfully, but these errors were encountered: