simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
Comparison · Analytics
gdverse vs healthyR.data
A side-by-side editorial comparison of gdverse and healthyR.data — release velocity, themes, recent moves, and the top alternatives to consider.
gdverse vs healthyR.data: at a glance
What is gdverse?
gdverse is turning geographical detector methods into inference, not just point estimates.
A geographical detector toolkit for spatial stratified heterogeneity, shipping small numbered releases every few months. Recent work centres on statistical rigour: confidence intervals for the q-statistic (experimental in 1.3-2, made more robust in 1.6), reported significance for interaction detection, and a fix for stratification collision in that same interaction path. The rest is Python-interop maintenance — reticulate compatibility, parallel stability in cpd_disc, and dependency configuration.
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.
gdverse vs healthyR.data: editorial side-by-side
gdverse
0.0ANALYTICS
gdverse is turning geographical detector methods into inference, not just point estimates.
◆ Current state
A geographical detector toolkit for spatial stratified heterogeneity, shipping small numbered releases every few months. Recent work centres on statistical rigour: confidence intervals for the q-statistic (experimental in 1.3-2, made more robust in 1.6), reported significance for interaction detection, and a fix for stratification collision in that same interaction path. The rest is Python-interop maintenance — reticulate compatibility, parallel stability in cpd_disc, and dependency configuration.
◆ Where it's heading
The arc is from computing detector statistics to qualifying them. Confidence intervals, significance reporting and non-centrality parameter estimation are all about telling users how much to trust a q-value, which is the gap between a research script and a package other people cite. The Python-dependency work is the recurring tax on that: several releases exist mainly to keep reticulate-backed models passing checks.
◆ Prediction
Expect the experimental q-statistic confidence intervals to be promoted to a stable, documented interface across the detector family, since the last two releases have both worked on their robustness and reporting.
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.
Alternatives to gdverse and healthyR.data
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 gdverse or healthyR.data.
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 gdverse alternatives → · See all healthyR.data alternatives →
Recent activity from gdverse and healthyR.data
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 6mo agogdverseInteraction detection reports significance; stratification collision fixed
- 10mo agogdversePython examples wrapped to stop CRAN check failures
- 10mo agogdversecpd_disc refactored for parallel stability and reticulate compatibility
- 1y agogdverseAdds package citation metadata
- 1y agogdverseExperimental confidence intervals for the q statistic
- 1y agohealthyR.datahttr2 compatibility fix
- 1y agogdversePlot method bug fixes across four detector models
- 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 gdverse and healthyR.data?
They serve adjacent needs but don't currently overlap on shipped themes. gdverse and healthyR.data 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 gdverse better than healthyR.data?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. gdverse and healthyR.data 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 gdverse?
Top gdverse alternatives in Analytics are ranked by recent ship velocity. Browse the "gdverse alternatives" section above for the current picks, or visit /alternatives/gdverse for the full list with editorial commentary on each.
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.