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.

geoDeltaAudit: Quantifying Variable Change Induced by Administrative Boundary Transformations

Tools for auditing how analytic variables change when data are transformed across administrative boundary systems. The package is agnostic to data source, variable type, and administrative geography, and is designed to quantify transformation-induced change without attributing blame to any specific boundary definition or allocation scheme.

Version: 0.1.0
Depends: R (≥ 4.1.0)
Imports: dplyr, janitor, rlang, stringr, tibble
Suggests: knitr, readr, rmarkdown, testthat (≥ 3.0.0)
Published: 2026-05-13
DOI: 10.32614/CRAN.package.geoDeltaAudit (may not be active yet)
Author: Phinn Markson [aut, cre]
Maintainer: Phinn Markson <markson.2 at osu.edu>
BugReports: https://github.com/phinnphace/geoDeltaAudit/issues
License: MIT + file LICENSE
URL: https://github.com/phinnphace/geoDeltaAudit
NeedsCompilation: no
Materials: README, NEWS
CRAN checks: geoDeltaAudit results

Documentation:

Reference manual: geoDeltaAudit.html , geoDeltaAudit.pdf
Vignettes: Audit walkthrough (source, R code)
Audit workflow (source, R code)
Hennepin County Visualizations (source, R code)
introduction (source)
Proportionality considerations (source, R code)

Downloads:

Package source: geoDeltaAudit_0.1.0.tar.gz
Windows binaries: r-devel: not available, r-release: not available, r-oldrel: not available
macOS binaries: r-release (arm64): geoDeltaAudit_0.1.0.tgz, r-oldrel (arm64): geoDeltaAudit_0.1.0.tgz, r-release (x86_64): geoDeltaAudit_0.1.0.tgz, r-oldrel (x86_64): geoDeltaAudit_0.1.0.tgz

Linking:

Please use the canonical form https://CRAN.R-project.org/package=geoDeltaAudit 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.