← Back to home
Comparison · Analytics

probmed vs soilDB

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

probmed vs soilDB: at a glance

FeatureprobmedsoilDB
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themescausal mediation, effect size, semiparametric inference, cross-fittingsoil-data, usda-nasis, ssurgo, spatial-queries
Last editorial update2h ago41m ago
WebsiteVisit →Visit →

What is probmed?

probmed went from one probabilistic effect size to a family of them in sixteen days.

probmed computes P_med, a scale-free probabilistic effect size for causal mediation, as part of the Data-Wise mediationverse alongside medfit, medsim and RMediation. Three releases in three weeks took it from a single estimator to four additional families built on a shared cross-fitted corner-EIF core, covering gauge-calibrated, incremental-elasticity and Sobol variance-share versions of the proportion mediated. Distribution is GitHub and r-universe rather than CRAN, with a load-bearing Remotes pin on medfit.

Read the full probmed trajectory →

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 →

probmed vs soilDB: editorial side-by-side

P
probmed
ANALYTICS
0.0

probmed went from one probabilistic effect size to a family of them in sixteen days.

◆ Current state

probmed computes P_med, a scale-free probabilistic effect size for causal mediation, as part of the Data-Wise mediationverse alongside medfit, medsim and RMediation. Three releases in three weeks took it from a single estimator to four additional families built on a shared cross-fitted corner-EIF core, covering gauge-calibrated, incremental-elasticity and Sobol variance-share versions of the proportion mediated. Distribution is GitHub and r-universe rather than CRAN, with a load-bearing Remotes pin on medfit.

◆ Where it's heading

The pace is manuscript-driven — estimators arrive with their citations attached and vignettes alongside, and the 0.1.0 notes correct the estimand itself against a manuscript definition rather than fixing a bug in code. Each release adds inference machinery as well as point estimates: percentile-bootstrap intervals and Fieller sets in 0.3.0, a deterministic MBCO interval in 0.2.0 that avoids resampling entirely. The gauge residual and the pmed_sensitivity() helper suggest a growing concern with when the estimand does not decompose at all.

◆ Prediction

0.3.0 shipped a sensitivity helper for shared mediator-outcome confounding and a diagnostic that flags non-decomposability, so the next release most likely extends that diagnostic side rather than adding a fifth estimator family.

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.

Alternatives to probmed and soilDB

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 probmed or soilDB.

See all probmed alternatives → · See all soilDB alternatives →

Recent activity from probmed and soilDB

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

  1. 1mo agosoilDBFY26 soil maps reach OCONUS; SSURGO downloads go parallel
  2. 1mo agoprobmedFour estimator families on a cross-fitted corner-EIF core
  3. 2mo agoprobmedParallel mediators and a resampling-free MBCO interval
  4. 2mo agoprobmedFirst release: pmed() with the estimand corrected
  5. 4mo agosoilDBROSETTA v2 lands as the deprecated NASIS aliases are removed
  6. 10mo agosoilDBNASIS record IDs now retrievable through Soil Data Access
  7. 11mo agosoilDBSpatial queries can pull columns from non-spatial tables
  8. 1y agosoilDBNASIS 7.4.3 metadata, plus HWSD and a local cache in 2.8.10
  9. 1y agosoilDBQuery internals rewritten as CTEs for local SQLite support

Frequently asked questions

What is the difference between probmed and soilDB?

They serve adjacent needs but don't currently overlap on shipped themes. probmed and soilDB 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 probmed better than soilDB?

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

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

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.