← Back to home
Comparison · Analytics

soilDB vs susier

A side-by-side editorial comparison of soilDB and susier — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:r-package

soilDB vs susier: at a glance

FeaturesoilDBsusier
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themessoil-data, usda-nasis, ssurgo, spatial-queriesr-package, statistical-genetics, fine-mapping, cpp-bindings
Last editorial update2h ago51m ago
WebsiteVisit →Visit →

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.

Read the full soilDB trajectory →

What is susier?

Fine-mapping workhorse susieR spends its releases hunting null-effect trimming bugs

susieR implements the Sum of Single Effects regression model for variable selection and fine-mapping, widely used in statistical genetics. The recent releases are a tight run of correctness work concentrated in one area: null effect trimming. Version 0.15.55 fixed trimming under the Servin-Stephens residual variance method, 0.15.56 fixed it again for non-uniform prior weights fourteen minutes later, 0.15.57 corrected an ELBO null space term for RSS with X and a matrix symmetry check, and 0.15.58 addressed an alpha0/beta0 issue. Version 0.16.0 migrates the C++ bindings from Rcpp to cpp11 with cpp11armadillo.

Read the full susier trajectory →

soilDB vs susier: editorial side-by-side

S
soilDB
ANALYTICS
0.0

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.

S
susier
ANALYTICS
0.0

Fine-mapping workhorse susieR spends its releases hunting null-effect trimming bugs

◆ Current state

susieR implements the Sum of Single Effects regression model for variable selection and fine-mapping, widely used in statistical genetics. The recent releases are a tight run of correctness work concentrated in one area: null effect trimming. Version 0.15.55 fixed trimming under the Servin-Stephens residual variance method, 0.15.56 fixed it again for non-uniform prior weights fourteen minutes later, 0.15.57 corrected an ELBO null space term for RSS with X and a matrix symmetry check, and 0.15.58 addressed an alpha0/beta0 issue. Version 0.16.0 migrates the C++ bindings from Rcpp to cpp11 with cpp11armadillo.

◆ Where it's heading

The version-number churn understates how narrow this work is — four consecutive releases touching the same trimming and residual-variance machinery suggests one area where the implementation and the intended behavior had drifted apart. The 0.16.0 binding migration is the only structural change, and it is invisible to users while mattering for build portability and long-term maintenance. Development is clearly active, with automated release tooling and dependency bumps flowing through the same stream.

◆ Prediction

With the binding migration just landed, near-term releases are likely to address fallout from it alongside continued fixes in the same trimming and residual-variance code.

Alternatives to soilDB and susier

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 susier.

See all soilDB alternatives → · See all susier alternatives →

Recent activity from soilDB and susier

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1mo agosoilDBFY26 soil maps reach OCONUS; SSURGO downloads go parallel
  2. 3mo agosusierMigrates C++ bindings from Rcpp to cpp11 and cpp11armadillo
  3. 3mo agosusierFixes alpha0/beta0 handling under Servin-Stephens
  4. 4mo agosoilDBROSETTA v2 lands as the deprecated NASIS aliases are removed
  5. 4mo agosusierCorrects the null space ELBO term for RSS with X
  6. 5mo agosusierFixes null effect trimming with non-uniform prior weights
  7. 5mo agosusierFixes null effect trimming under Servin-Stephens estimation
  8. 10mo agosoilDBNASIS record IDs now retrievable through Soil Data Access
  9. 11mo agosoilDBSpatial queries can pull columns from non-spatial tables
  10. 1y agosoilDBNASIS 7.4.3 metadata, plus HWSD and a local cache in 2.8.10
  11. 1y agosoilDBQuery internals rewritten as CTEs for local SQLite support

Frequently asked questions

What is the difference between soilDB and susier?

Both compete on the same themes — r-package — within Analytics. soilDB and susier 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 susier?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. soilDB and susier 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 susier?

Top susier alternatives in Analytics are ranked by recent ship velocity. Browse the "susier alternatives" section above for the current picks, or visit /alternatives/susier for the full list with editorial commentary on each.