species_guess is an actual field that you can include when exporting your observations. it’s not reliable in every case, but it should generally give you an idea of what your identification is on your own observations.
if you don’t actually need the data exported, then on your own observations…
if you want to see where anyone identified something as X, then you can use:
if you want to see where you identified something as X, you have to search identifications (not observations):
- https://www.inaturalist.org/identifications?user_id=markus_dumke&for=self&taxon_id=[numeric id of X]
- https://jumear.github.io/stirfry/iNatAPIv1_identifications?per_page=200&own_observation=true&user_id=markus_dumke&taxon_id=[numeric id of X]
- this latter option has more additional filter parameters available, such as
place_id,observation_taxon_id,without_taxon_id,without_observation_taxon_id, etc.
- this latter option has more additional filter parameters available, such as
and here’s another thing that may be useful, particularly if you’re not dealing with a specific taxon X: https://forum.inaturalist.org/t/reviewing-multiple-older-entries-quickly-to-see-if-they-are-waiting-to-be-corrected-or-refined-to-ssp-or-var/69039/5
…
if species_guess doesn’t work for your use case, and if you actually need the data in, say, a CSV file, then i think the only way right now to get this done with standard user interfaces is by including your observations in a traditional project, making yourself a curator for the project, and then exporting the observations from the project page. that will generate a CSV export that includes fields like curator_taxon_id, etc.
otherwise, without resorting to a using traditional project, you’d have to extract the data via the API, and parse / lay out the data however you like it.