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.

soiltillr: Analyse Soil Tillage Depth and Erosion Over Time

Provides tools to record, validate, and analyse soil tillage depth and erosion across years and field treatments. Includes functions for year-wise tillage operation summaries, erosion depth tracking, compaction detection, soil loss estimation, and visualisation of temporal changes in tillage and erosion profiles. Methods follow Lal (2001) <doi:10.1201/9780203739280> and Renard et al. (1997) "Predicting Soil Erosion by Water: A Guide to Conservation Planning with the Revised Universal Soil Loss Equation (RUSLE)" <https://ntrl.ntis.gov/NTRL/dashboard/searchResults/titleDetail/PB97153704.xhtml>.

Version: 0.1.0
Depends: R (≥ 3.5.0)
Imports: dplyr (≥ 1.1.0), ggplot2 (≥ 3.4.0)
Suggests: testthat (≥ 3.0.0), knitr, rmarkdown
Published: 2026-03-23
DOI: 10.32614/CRAN.package.soiltillr
Author: Sadikul Islam ORCID iD [aut, cre]
Maintainer: Sadikul Islam <sadikul.islamiasri at gmail.com>
License: MIT + file LICENSE
NeedsCompilation: no
Language: en-US
Citation: soiltillr citation info
Materials: README, NEWS
CRAN checks: soiltillr results

Documentation:

Reference manual: soiltillr.html , soiltillr.pdf
Vignettes: Introduction to soiltillr (source, R code)

Downloads:

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

Linking:

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