Skip to content

Non-human exclusion #5

@albullington

Description

@albullington

Is your feature request related to a problem? Please describe.
The AR camera sometimes identifies humans as non-humans, which often isn't a positive experience for the end user.

Describe the solution you'd like
Tackle this somewhat differently from how we tackled it on the web, since RN-inat-camera doesn't have a concept of a common ancestor.

Ideally, a solution would also address the concept of uncertainty similar to the common ancestor approach in iNatAPI, where if the distribution of scores among top results is relatively even & human is in the mix, we assume the result might be human and return nothing.

  • Calculate the scores for the branch ending in human and compare that with the “best” branch, and if the leaf of the best branch has a score within 0.2 of the equivalent rank on the human branch, return nothing

Describe alternatives you've considered
None

Additional context
The original non-human exclusion for iNatAPI is in this commit. Since React Native only ever receives a single branch, non-human exclusion needs to be tackled in native code.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions