@spiphany Shannonâs Index within an area seems pretty straight forward (I understand it is usually calculated for a communiity, but I donât see why it couldnât be for an area). It only takes very few variables, and all of the required information is available on iNaturalist (within the bounds of the data available on iNaturalist ⌠as mentioned ⌠of course): number of species in an area, number of individuals of species x in an area, total number of individuals in an area, from which we can, by division, calculate the proportion of species x in an area.
In terms of computing power, which is not something we have discussed so far, it would require some estimation whether or not iNaturalist has the resources for these calculations. But this should not necessarily be a problem, as calculations can be done on a much less frequent periodic basis, they do not need to be re-calculated in real-time, if too expensive for the non-profit. However, I think providing the could also yield additional value and thus donations/funding, which could also be estimated when analysing feasability.
@spiphany I am flattered that you suggest I should be the one to propose exactly which metrics and parameters could be interesting in terms of biodiversity. I will do reading for sure, because this interests me greatly, but I believe we are stronger if we work together. My post here is categorised as a question for this very reason. I think we have a lot of experts in the field here, who could equally make some proposals.
There might be some experts in the field who will reply that such or such tool already exists which uses one of the iNaturalist APIs. Which was equally one of my questions.
Letâs take the simple formula of the Shannonâs Index. Do you see any variable which we are lacking? Or do you agree that we have all necessary variables in order to calculate the index with iNaturalist data (of course ⌠with the limitations of the bias of the data-points)? If so, we already have one possible metric (from my side, I am not saying it needs to be the Shannonâs Index that we incorporate, just mentioning it as an example as it was mentioned as notable by others above).
2. iNat data is not collected systematically or with any sort of consistency â that is, it is prone to all sorts of biases. Any algorithm for calculating biodiversity will not provide accurate results if you do not first identify what these biases are and how to correct for them. These biases may not be something that can be easily determined from the dataset alone, because it may require knowledge about things like where streets and public transit are located, or what sort of training observers have. iNat does not and cannot record this information.
Regarding your point 2. (and equally towards the comment above by @einsum). â While these are all interesting remarks; it is not a problem, in my view, that results will be biased due to the various factors influencing what type of observations/identifications exist on the platform where and at which level.
Even if the tool / metric(s) will be somewhat naive, and with obvious limitations because of the data-set, itâs better to have some visibility rather than none at all.
1. It is difficult to meaningfully measure biodiversity even if your data is collected systematically using consistent protocols, because there are different ways of defining biodiversity.
Regarding your point 1. â As outlined, there are different metrics to describe biodiversity. I would say it makes it much more interesting and it suggests including a dynamic feature, i.e. an option to switch between metrics within the tool.
Regarding all of the above, I am reminded of other functionalities of iNaturalist. When it comes to taxonomy, for example, iNaturalist by default counts the taxa represented by these observations using âleaf countâ. For the API, for example this has implications as it disregards subspecies/infraspecies (I have had some discussions on this with @elias105 and @pisum). So even though iNaturalist in general (taxonomy is a core business I would say) makes some choices in the back-end to default to a certain metric, and limits its API currently in this way for example ⌠nevertheless, on the analysis/reporting side of things, iNaturalist still allows for the user to choose many different ways to choose a different metric to count. This is also explained in the last sentence of the help page How does iNaturalist count taxa? (modified on Thu, 1 Aug, 2024):
âIf youâd prefer the species count rather than the leaf count on the Species tab in Explore, use the Rank control in the Filters menu and set High to Speciesâ.
Equally, the user currently has the option there to choose to switch the metric to include for example subspecies, if desired, in their reporting/analysis.
We are here not proposing to change the entire way iNaturalist works in the back-end. It is simply a matter of reporting/analysis. And so I do not see any reason why there could not be multiple metrics (options) implemented, for the user to choose from. Analogous to what was done for the filter options with the example regarding taxonomy:
- There are different ways to represent taxonomy
- â It makes it more difficult
- â iNaturalist proposes a default setting, and at the same time allows the users to filter/change to other metrics via options
Does that mean there are only 540259 species in The World, as the page https://www.inaturalist.org/observations?lrank=species&place_id=any&view=species suggests? No, it does not of course. The data, as mentioned, is skewed/limited/biased. It only shows us what is available based on the data-set of iNaturalist.
Another example, with regards to limitations/skewing/bias: I made an observation of a grain mite. iNaturalist shows me that there are only 32 total observations of this species in The World. Does that mean that nobody else observed/identified grain mites outside these 32 observations? No, of course not. Does that mean that this is a very rare species in the real world? No, of course not. Obviously, the data will be skewed. But that does not make it less interesting to start capturing and showing metrics within the ever-changing and growing data-set. Otherwise, we could make the case against iNaturalist as a platform as a whole, which I wouldnât be surprised if it was the case in the early beginnings, from some academics (or maybe still!).
Of course there can be political reasons why people are against providing easily accessible biodiversity metrics. But intrinsically, I would find it a very interesting exploratory feature, and a very important topic for science popularisation.