PurpleAir
The R client for PurpleAir sensors keeps finding its time-averaging was wrong.
Comparison · Analytics
medrobust vs soilDB
A side-by-side editorial comparison of medrobust and soilDB — release velocity, themes, recent moves, and the top alternatives to consider.
medrobust vs soilDB: at a glance
What is medrobust?
medrobust made its partial-identification bounds usable by giving them confidence intervals.
medrobust computes partial-identification bounds for mediation effects when exposure or mediator is differentially misclassified, part of the Data-Wise mediationverse. Its 0.2.0 release corrected three estimator defects against population oracles and added Imbens-Manski confidence intervals for the bounds; the two releases since have paired each identification path with a real public-domain dataset and a worked vignette. CRAN is deferred, with distribution through GitHub and r-universe.
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.
medrobust vs soilDB: editorial side-by-side
medrobust
0.0ANALYTICS
medrobust made its partial-identification bounds usable by giving them confidence intervals.
◆ Current state
medrobust computes partial-identification bounds for mediation effects when exposure or mediator is differentially misclassified, part of the Data-Wise mediationverse. Its 0.2.0 release corrected three estimator defects against population oracles and added Imbens-Manski confidence intervals for the bounds; the two releases since have paired each identification path with a real public-domain dataset and a worked vignette. CRAN is deferred, with distribution through GitHub and r-universe.
◆ Where it's heading
The pattern is deliberate and symmetric: 0.3.0 shipped the mediator-side example on NCHS natality data, 0.4.0 its exposure-side mirror on NHANES, each demonstrating what the bounds do when reporting accuracy is allowed to depend on the outcome. Alongside that runs a consistent concern with failing usefully rather than loudly — bound_ne() returns NA bounds with a machine-readable reason and a typed condition instead of aborting, so a simulation replicate is recorded rather than lost, and non-finite endpoint standard errors produce a documented NA rather than a silent one. That is a package expecting to be run thousands of times inside someone else's loop.
◆ Prediction
Both identification paths now have a dataset, a vignette and interval coverage, so the next release is most likely the deferred CRAN submission rather than new methodology.
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.
Alternatives to medrobust 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 medrobust or soilDB.
piecepackr
A board game graphics package runs one of the most disciplined deprecation cycles in R.
e2tree
The explainable-ensemble-tree package now measures whether its own explanations are faithful.
discretefdr
The discrete-data FDR package is being pared into one piece of a larger multiple-testing suite.
contentanalysis
A scientific-text analysis package moved from counting citations to classifying argument structure.
relialearnr
The teaching arm of an R reliability suite keeps pace with whatever its analysis siblings ship.
See all medrobust alternatives → · See all soilDB alternatives →
Recent activity from medrobust and soilDB
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agosoilDBFY26 soil maps reach OCONUS; SSURGO downloads go parallel
- 2mo agomedrobustNHANES exposure-side misclassification example dataset
- 2mo agomedrobustNatality example dataset; bounds degrade instead of aborting
- 2mo agomedrobustBounds corrected against oracles; Imbens-Manski intervals added ⚡
- 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
Frequently asked questions
What is the difference between medrobust and soilDB?
They serve adjacent needs but don't currently overlap on shipped themes. medrobust 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 medrobust better than soilDB?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. medrobust 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 medrobust?
Top medrobust alternatives in Analytics are ranked by recent ship velocity. Browse the "medrobust alternatives" section above for the current picks, or visit /alternatives/medrobust 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.