Skip to main content
Dryad

Data from: Identifying Key Biodiversity Areas based on distinct genetic diversity

Data files

Nov 07, 2025 version files 133.01 GB
Dec 04, 2025 version files 133.01 GB

Click names to download individual files Select up to 11 GB of files for zip download

Abstract

Key Biodiversity Areas (KBAs) are sites that contribute significantly to the global persistence of biodiversity. Distinct genetic diversity has been introduced as one of the metrics to estimate whether a site holds a threshold proportion of a species’ global genetic diversity during the KBA identification process. However, genetic data has so far not been used due to the lack of thoroughly tested methods and guidance. We tested the applicability of Analyses of Molecular Variance (AMOVA), allelic overlap, the diversity index Simpson's λ, Δ+, Dest, and effective population size (Ne) for identification of KBAs. We conclude that Δ+, a measure that has originally been developed to measure taxonomic distinctness of biotic communities, performs best in the context of KBA identification reflects the unique nature of a species’ genetic diversity, is based on simple allele frequencies, and can be easily applied and calculated. AMOVA, Ne, allelic overlap, and our modified version of λ, were difficult to apply, interpret, or both. Dest is easily applied for measuring genetic distinctiveness but not genetic diversity. For this reason, it may not be suitable for prioritizing areas for the long-term protection of the species.

Here, we deposited additional information on which methods, and how they were calculated on which data sets, including references. We included additional information on how these methods performed. Moreover we included raw reads, an already processed .str file and additional information of additional data set we created to add a case study to our publication. The code we used for our analyzes can be found on GitHub and Zenodo. For more information about the code and the detailed procedure, view the associated publication, the readme on GitHub, and the Supplemental_Information.pdf file we publish here.