simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
A side-by-side editorial comparison of aqp and healthyR.data — release velocity, themes, recent moves, and the top alternatives to consider.
The 1.x line, tagged retroactively after a decade of SoilProfileCollection redesign.
aqp provides the SoilProfileCollection class and the algorithms built on it for soil profile data, colour, and taxonomy. The most recent tag in this feed is explicitly retroactive: 1.42 was cut in 2025 to mark the last CRAN state before the 2.0 release. Between 2018 and 2021 the class internals were reworked twice, the Munsell colour tooling grew substantially, and data.table replaced reshape underneath the wide-to-long transformations.
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.
aqp provides the SoilProfileCollection class and the algorithms built on it for soil profile data, colour, and taxonomy. The most recent tag in this feed is explicitly retroactive: 1.42 was cut in 2025 to mark the last CRAN state before the 2.0 release. Between 2018 and 2021 the class internals were reworked twice, the Munsell colour tooling grew substantially, and data.table replaced reshape underneath the wide-to-long transformations.
Two threads run through the window. The core object was progressively rebuilt - a new horizon-ID slot in 1.17, then a wave of renames and argument removals in 1.25 that broke code deliberately ahead of 2.0. Alongside it, colour work compounded: mixMunsell, spectral mixing, colour quantiles, a chip-frequency chart, and PMS conversion. Tag order here is not release order, since 1.42 was applied to an older commit.
This feed reads as a closed chapter - further entries on it would be backfill, with active work having moved to the 2.x series.
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 aqp 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 aqp alternatives → · See all healthyR.data alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. aqp 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. aqp 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.
Top aqp alternatives in Analytics are ranked by recent ship velocity. Browse the "aqp alternatives" section above for the current picks, or visit /alternatives/aqp 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.