The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.
3D systematic conservation planning, conducting nested prioritization analyses across multiple depth levels and ensuring efficient resource allocation throughout the water column (Doxa et al. 2024 <doi:10.1111/gcb.16268>). It provides a structured workflow designed to address biodiversity conservation and management challenges in the 3 dimensions, such as the incorporation of multiple costs at different depth levels, while facilitating users’ choices and parameterization.
Version: | 0.1.0 |
Depends: | R (≥ 2.10) |
Imports: | prioritizr (≥ 8.0.4), terra, maps (≥ 3.4.2), highs, viridis (≥ 0.6.5), readxl (≥ 1.4.3), rasterdiv (≥ 0.3.4), geodiv (≥ 1.1.0), methods, stats, utils, graphics |
Suggests: | knitr, rmarkdown, testthat (≥ 3.0.0) |
Published: | 2024-08-23 |
DOI: | 10.32614/CRAN.package.prior3D |
Author: | Christos Adam [aut, cre], Nikolaos Nagkoulis [aut], Aggeliki Doxa [aut] |
Maintainer: | Christos Adam <econp266 at econ.soc.uoc.gr> |
BugReports: | https://github.com/cadam00/prior3D/issues |
License: | GPL-3 |
URL: | https://github.com/cadam00/prior3D |
NeedsCompilation: | no |
Materials: | README NEWS |
CRAN checks: | prior3D results |
Reference manual: | prior3D.pdf |
Vignettes: |
Introduction to prior3D (source, R code) |
Package source: | prior3D_0.1.0.tar.gz |
Windows binaries: | r-devel: prior3D_0.1.0.zip, r-release: prior3D_0.1.0.zip, r-oldrel: prior3D_0.1.0.zip |
macOS binaries: | r-release (arm64): prior3D_0.1.0.tgz, r-oldrel (arm64): prior3D_0.1.0.tgz, r-release (x86_64): prior3D_0.1.0.tgz, r-oldrel (x86_64): prior3D_0.1.0.tgz |
Please use the canonical form https://CRAN.R-project.org/package=prior3D to link to this page.
These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.