The taxonomic group that you searched for but did not find (eg Papilionoidea if you were searching for butterflies and found none).
Observation | Taxon sought but not found |
---|---|
unknown | |
unknown | |
unknown | |
unknown | |
unknown | |
unknown | |
unknown | |
unknown | |
unknown | |
unknown | |
unknown | |
unknown | |
unknown | |
unknown | |
unknown | |
unknown | |
unknown | |
unknown | |
unknown | |
unknown | |
unknown | |
unknown | |
unknown | |
unknown | |
unknown | |
unknown | |
unknown | |
unknown | |
unknown | |
unknown |
@tony_wills FYI
There is a much more straightforward way to do this, which would be trivially easy to implement (if there were the will at iNat central). All we need is to have it so that adding the value 0 (zero) to the observation field 'count' stops the obs from showing on the map for the taxon (or better, makes it show on the map in a different colour).
I find both this field and the Sought but not found
field very problematic if they are misrepresenting observations which are occurrences by definition as a non-occurrence.
For example, if this observation https://www.inaturalist.org/observations/3053718
is actually saying that Trichosurus vulpecula was not present at that point in space and time, thats creating all sorts based on how the iNat system is interpreting data used for distributions, image recognition, reputation etc.
I'm also not understanding how this observation could be both a presence and absence of a butterfly
https://www.inaturalist.org/observations/20838639
Please use https://www.inaturalist.org/trips instead for recording absence data on iNaturalist make sure we're being consistent in our interpretation of observations as the presence (not absence) of an organism at a point in space and time.
For several years now I've used the Sought but not found field (Yes/No) in combination with my observation ID to specify what I was looking for when I didn't find anything. For example, if I searched for butterflies but found none, I'd upload an observation with the ID Papilionoidea and set "Sought but not found" to "Yes".
This hasn't been ideal because every time I do this it puts a pin on the map for Papilionoidea.
I've just added this new field, "Taxon sought but not found", so I can do this a better way. Now I can add a new observation with no ID so it doesn't show on the iNat map. Then I can specify the taxon I was looking for with "Taxon sought but not found".
I could also answer the Data Quality Assessment question "Based on the evidence, can the Community ID still be confirmed or improved?" to "No" so nobody needs to bother trying to ID it.