If anyone is interested in visualizing their iNat data, I’m currently making a repository on GitHub that will be full of code for producing some cool graphics done with R. Also, if you have any suggestions for a visualization I don’t have yet in the repo or if you don’t know how to use R, dm me and I will make it for you.
If you notice any errors in the code or a way to make the visualizations better, feel free to file an issue in the repo.
i’m actually not an R person, but there are plenty of folks who have mentioned making things for iNat for and related to R (feel free to add to this wiki post, if you like):
I don’t have much else to say at the moment, but this is great. Keen to see where this goes.
Actually I’m not sure whether the links that @pisum provided will mention it at all, but there’s also the rinat package here: https://github.com/ropensci/rinat.
from what i can tell, the rinat package is a little dated at this point. it seems to hit the old iNaturalist API, which is deprecated at this point, and rinat doesn’t seem to be actively developed any more. i think it would be better to use hanly’s thing above, which hits the current v1 API, or just hit the API directly yourself. (the v2 API is currently in development. so even the current v1 API and anything built on it may be dated soon, too.)
it’s definitely not all of it. the above items are only the things i remember of that relate to visualizations or ways to get data from the API into R. (i remember other people using R to do other things like modify EXIF data, etc.)
i just made my earlier post a wiki. so if you want to add to it, feel free to add to it, if you like.
Note that observation are tallied so there is 1 “vote” per user per species/state/month. This minimizes the effect of super-users, and also makes it so top species on the website do not necessarily match
it may be updated, but as far as i can tell, it still hits the deprecated iNat API. is there any reason to use rinat for new development rather than hitting the current /v1 API directly or using some other wrapper package that hits the /v1 API? (just for example, rOpenSci also provides the spocc package which will allow you to get info from iNat’s /v1 API, along with other sources like GBIF, eBird, etc.)