simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
A side-by-side editorial comparison of b3gbi and healthyR.data — release velocity, themes, recent moves, and the top alternatives to consider.
b3gbi pulled confidence intervals out of its indicator workflow and handed them to dubicube.
b3gbi computes biodiversity indicators from GBIF occurrence cubes for the B-Cubed project, and sits at 0.9.4 in a JOSS review run-up. The 0.9 release decoupled uncertainty from indicator calculation: confidence intervals are no longer produced inline but added afterward with add_ci(), backed by whole-cube bootstrapping from the sibling dubicube package. Everything since has been grid-parsing and compatibility repair around that split.
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.
b3gbi computes biodiversity indicators from GBIF occurrence cubes for the B-Cubed project, and sits at 0.9.4 in a JOSS review run-up. The 0.9 release decoupled uncertainty from indicator calculation: confidence intervals are no longer produced inline but added afterward with add_ci(), backed by whole-cube bootstrapping from the sibling dubicube package. Everything since has been grid-parsing and compatibility repair around that split.
Two forces are shaping releases. Internally, the uncertainty split produced an indicator-specific rule book — species-level indicators bootstrap the whole cube, raw counts resample within year, evenness gets a logit transform — and that rule book is where the statistical thinking now lives. Externally, GBIF's taxonomic backbone migration to the Catalogue of Life forced string taxon keys through process_cube() and the plotting paths, while recurring EEA and MGRS grid-code fixes mark coordinate parsing as the least settled area.
The 0.9.4 notes are entirely JOSS review items — contributors, examples, tracked datasets — so the next release is most likely a JOSS-accepted 1.0 rather than new indicator work.
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.
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.
With the fetch layer generalised, the next visible work is more likely record-limit and error handling around httr2 than further per-measure accessors.
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 b3gbi or healthyR.data.
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
SEM reporting helpers converging on APA output, one CRAN resubmission at a time.
A raster-to-terra migration is the only readable change in a feed of merge notes.
A nycflights13 generator whose recent work is all about the data being right.
Conditional density and log-likelihood fill out a vine copula regression package.
A drop-in string API for base R, kept alive by upstream check failures.
See all b3gbi alternatives → · See all healthyR.data alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. b3gbi is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. b3gbi is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top b3gbi alternatives in Analytics are ranked by recent ship velocity. Browse the "b3gbi alternatives" section above for the current picks, or visit /alternatives/b3gbi for the full list with editorial commentary on each.
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.