simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
Comparison · Analytics
soilDB vs vinereg
A side-by-side editorial comparison of soilDB and vinereg — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
soilDB vs vinereg: at a glance
What is soilDB?
The R front door to USDA soil data finishes a long deprecation cleanup and turns local-first.
soilDB is the R access layer for USDA-NRCS soil data: NASIS local databases, Soil Data Access, SoilWeb coverage services, and a widening set of curated national grids. The 2.9.x line closed out a multi-release deprecation cycle — column aliases and stringsAsFactors are gone, R 4.1 is the floor, and the bundled sample profile collections were rebuilt against the new schema. Recent work has shifted from adding query functions to making existing ones faster and usable against local SQLite or GeoPackage copies.
What is vinereg?
Conditional density and log-likelihood fill out a vine copula regression package.
vinereg fits D-vine copula-based regression models on top of rvinecopulib and kde1d, in Thomas Nagler's package stack. The January 2025 pair - 0.10.0 and 0.11.0 tagged the same day - adds a pdf() function and then fixes conditional density computation for discrete variables while requiring the newer kde1d. Release notes run to one or two bullets each.
soilDB vs vinereg: editorial side-by-side
soilDB
0.0ANALYTICS
The R front door to USDA soil data finishes a long deprecation cleanup and turns local-first.
◆ Current state
soilDB is the R access layer for USDA-NRCS soil data: NASIS local databases, Soil Data Access, SoilWeb coverage services, and a widening set of curated national grids. The 2.9.x line closed out a multi-release deprecation cycle — column aliases and stringsAsFactors are gone, R 4.1 is the floor, and the bundled sample profile collections were rebuilt against the new schema. Recent work has shifted from adding query functions to making existing ones faster and usable against local SQLite or GeoPackage copies.
◆ Where it's heading
The arc points at offline and local-first workflows. downloadSSURGO() and createSSURGO() keep gaining arguments for building and querying local SSURGO databases, and the query internals were rewritten as common table expressions so identical code runs against the remote service or a local file. Coverage is widening in parallel: FY26 SoilWeb maps now reach most OCONUS surveys, while fetchHWSD() and fetchSOLUS() pull in datasets outside the core NASIS/SSURGO pair. Federal URL churn — EDIT, SoilWeb, S3-hosted geometry — is a recurring maintenance tax the package absorbs on users' behalf.
◆ Prediction
Expect the next releases to keep extending parallel and offline SSURGO handling, since LAPPLY.FUN has just opened the door to arbitrary parallel backends, and to fold more curated SoilWeb and FAO datasets behind fetch* wrappers.
vinereg
0.0ANALYTICS
Conditional density and log-likelihood fill out a vine copula regression package.
◆ Current state
vinereg fits D-vine copula-based regression models on top of rvinecopulib and kde1d, in Thomas Nagler's package stack. The January 2025 pair - 0.10.0 and 0.11.0 tagged the same day - adds a pdf() function and then fixes conditional density computation for discrete variables while requiring the newer kde1d. Release notes run to one or two bullets each.
◆ Where it's heading
Work has concentrated on evaluation rather than fitting: cll() in 0.9.0, pdf() in 0.10.0, and the discrete-variable correction in 0.11.0 all concern what can be computed from a model already fitted. Releases arrive in same-day pairs, and the notes are terse enough that 0.10.0 reuses 0.9.0's wording verbatim, describing pdf() with cll()'s sentence. Version floors also track the sibling packages - kde1d here, rvinecopulib in 0.8.3.
◆ Prediction
Given the shared release rhythm across the stack, the next entry is as likely to be a dependency-driven bump as a new function; the discrete-variable path is the one area these notes show as recently unstable.
Alternatives to soilDB and vinereg
Other Analytics products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either soilDB or vinereg.
lavaanExtra
SEM reporting helpers converging on APA output, one CRAN resubmission at a time.
ibis.iSDM
A raster-to-terra migration is the only readable change in a feed of merge notes.
anyflights
A nycflights13 generator whose recent work is all about the data being right.
stringx
A drop-in string API for base R, kept alive by upstream check failures.
healthyR.data
From a bundled hospital dataset to a live CMS API client.
See all soilDB alternatives → · See all vinereg alternatives →
Recent activity from soilDB and vinereg
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agosoilDBFY26 soil maps reach OCONUS; SSURGO downloads go parallel
- 4mo agosoilDBROSETTA v2 lands as the deprecated NASIS aliases are removed ⚡
- 10mo agosoilDBNASIS record IDs now retrievable through Soil Data Access
- 11mo agosoilDBSpatial queries can pull columns from non-spatial tables
- 1y agosoilDBNASIS 7.4.3 metadata, plus HWSD and a local cache in 2.8.10
- 1y agosoilDBQuery internals rewritten as CTEs for local SQLite support
- 1y agovineregDiscrete conditional densities fixed; kde1d 1.1.0 required
- 1y agovineregpdf() added for conditional density
- 2y agovineregBoost compile flag and a weights error fixed
- 2y agovineregcll() computes conditional log-likelihood
- 4y agovineregvinecopulib floor raised for RcppThread compatibility
- 4y agovineregcpit() fixed and external marginals allowed via uscale
Frequently asked questions
What is the difference between soilDB and vinereg?
Both compete on the same themes — r-package — within Analytics. soilDB and vinereg are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is soilDB better than vinereg?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. soilDB and vinereg are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to soilDB?
Top soilDB alternatives in Analytics are ranked by recent ship velocity. Browse the "soilDB alternatives" section above for the current picks, or visit /alternatives/soildb for the full list with editorial commentary on each.
What are the best alternatives to vinereg?
Top vinereg alternatives in Analytics are ranked by recent ship velocity. Browse the "vinereg alternatives" section above for the current picks, or visit /alternatives/vinereg for the full list with editorial commentary on each.