simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
A side-by-side editorial comparison of eiaapi and nipnTK — release velocity, themes, recent moves, and the top alternatives to consider.
A thin EIA energy-data client whose whole story is making bulk queries survive the API's limits.
eiaapi wraps the US Energy Information Administration API: eia_get() issues a single query, and eia_backfill() decomposes a large date range into chunks the API will actually serve. Three releases across two years cover the package's entire history, and the second and third both exist because of eia_backfill().
nipnTK's toolkit is settled; the last two years have gone into packaging, not methods.
An R implementation of the NiPN anthropometric data-quality checks — age heaping, age ratio tests, digit preference and the rest. The methods have been stable since the first CRAN release in 2020; the substantive change since was fixing ageRatioTest() for missing and numeric age values, shipped as a GitHub development release in April 2024 and to CRAN the next day. The most recent release is explicitly routine upkeep: refactored functions, a test for age heaping, pkgdown moved to the nutriverse template, citation and funding metadata.
eiaapi wraps the US Energy Information Administration API: eia_get() issues a single query, and eia_backfill() decomposes a large date range into chunks the API will actually serve. Three releases across two years cover the package's entire history, and the second and third both exist because of eia_backfill().
The package's development is a single problem being worked: pulling more data than one request allows. Version 0.1.2 introduced eia_backfill() for exactly that, and 0.2.0 fixed it for non-hourly frequencies by adding the frequency and data arguments so it matches eia_get()'s interface and by reworking Date handling. That convergence of the two functions' signatures is the visible design direction — one query idiom regardless of range size.
With the two functions now taking aligned arguments, further work most plausibly extends coverage to more EIA endpoints or response shapes. The entries name no specific target.
An R implementation of the NiPN anthropometric data-quality checks — age heaping, age ratio tests, digit preference and the rest. The methods have been stable since the first CRAN release in 2020; the substantive change since was fixing ageRatioTest() for missing and numeric age values, shipped as a GitHub development release in April 2024 and to CRAN the next day. The most recent release is explicitly routine upkeep: refactored functions, a test for age heaping, pkgdown moved to the nutriverse template, citation and funding metadata.
This is a maintained reference implementation rather than an evolving product. Release notes are dominated by repository plumbing — CI workflows, website templates, badges, CITATION files — which is what a package looks like once its statistical surface is complete and the work shifts to keeping it installable and citable. The nutriverse pkgdown template and shared conventions place it inside a family of nutrition packages from the same maintainer rather than standing alone.
Expect continued maintenance releases driven by CRAN policy and the nutriverse template rather than new checks, since two of the last three releases contained no method changes at all.
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 eiaapi or nipnTK.
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 eiaapi alternatives → · See all nipnTK alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. eiaapi and nipnTK 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. eiaapi and nipnTK 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 eiaapi alternatives in Analytics are ranked by recent ship velocity. Browse the "eiaapi alternatives" section above for the current picks, or visit /alternatives/eiaapi for the full list with editorial commentary on each.
Top nipnTK alternatives in Analytics are ranked by recent ship velocity. Browse the "nipnTK alternatives" section above for the current picks, or visit /alternatives/nipntk for the full list with editorial commentary on each.