simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
Comparison · Analytics
healthyR.data vs soilDB
A side-by-side editorial comparison of healthyR.data and soilDB — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
healthyR.data vs soilDB: at a glance
What is healthyR.data?
From a bundled hospital dataset to a live CMS API client.
healthyR.data supplies the data layer for the healthyverse packages. It began by shipping hospital data inside the package and now fetches from CMS and provider endpoints at call time through get_cms_meta_data(), fetch_cms_data(), and their provider counterparts. The most recent release is a single httr2 compatibility fix.
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.
healthyR.data vs soilDB: editorial side-by-side
healthyR.data
0.0ANALYTICS
From a bundled hospital dataset to a live CMS API client.
◆ Current state
healthyR.data supplies the data layer for the healthyverse packages. It began by shipping hospital data inside the package and now fetches from CMS and provider endpoints at call time through get_cms_meta_data(), fetch_cms_data(), and their provider counterparts. The most recent release is a single httr2 compatibility fix.
◆ Where it's heading
The 2023 release added roughly twenty current_*_data() accessors, one per CMS measure file - a wide but static surface. The 2024 releases replaced that approach with metadata lookup plus generic fetchers, then taught the fetchers to handle CSV, Excel, and ZIP payloads rather than API responses alone. The package's weight has moved from what it ships to what it can retrieve.
◆ Prediction
With the fetch layer generalised, the next visible work is more likely record-limit and error handling around httr2 than further per-measure accessors.
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 healthyR.data 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 healthyR.data or soilDB.
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.
vinereg
Conditional density and log-likelihood fill out a vine copula regression package.
stringx
A drop-in string API for base R, kept alive by upstream check failures.
See all healthyR.data alternatives → · See all soilDB alternatives →
Recent activity from healthyR.data and soilDB
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 agohealthyR.datahttr2 compatibility fix
- 2y agohealthyR.dataFetchers handle CSV, Excel, and ZIP, with a record limit
- 2y agohealthyR.dataMetadata lookup and generic CMS fetchers replace bundled data ⚡
- 3y agohealthyR.dataTwenty CMS measure accessors added
- 3y agohealthyR.datacli, crayon, and rstudioapi dependencies dropped
- 5y agohealthyR.dataxz compression added to meet CRAN size policy
Frequently asked questions
What is the difference between healthyR.data and soilDB?
Both compete on the same themes — r-package — within Analytics. healthyR.data 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 healthyR.data better than soilDB?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. healthyR.data 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 healthyR.data?
Top healthyR.data alternatives in Analytics are ranked by recent ship velocity. Browse the "healthyR.data alternatives" section above for the current picks, or visit /alternatives/healthyr-data 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.