rnpn
The USA phenology data client rebuilt its entire stack and stopped handing users -9999 as a number.
Comparison · Analytics
bagyo vs rATTAINS
A side-by-side editorial comparison of bagyo and rATTAINS — release velocity, themes, recent moves, and the top alternatives to consider.
bagyo vs rATTAINS: at a glance
What is bagyo?
bagyo reached CRAN as a Philippine tropical cyclone dataset, with its tags stamped out of order.
A data package distributing Philippine Area of Responsibility tropical cyclone records, developed through 2024 pre-releases and accepted by CRAN in early 2026. The substantive release is v0.2.0: 2021 and 2022 typhoon data added, an unexported helper for downloading cyclone reports, CITATION.cff, an R 4.1 dependency for the base pipe, and a full pass over vignettes, tests and README. The v0.1.1 tag announcing the first CRAN release carries no content and is stamped two hours after v0.2.0.
What is rATTAINS?
The R client for EPA water quality data spent two releases undoing its own promises about data shape.
rATTAINS wraps the EPA's ATTAINS API, which holds state water quality assessments and impaired-waters listings. The package reached 1.0.0 by promising stable, consistently rectangled return structures, then walked that promise back in 1.1.0 when it dropped the dependency doing the rectangling. As of 1.2.0 it also requires an API key, because ATTAINS itself began requiring one in May 2026.
bagyo vs rATTAINS: editorial side-by-side
bagyo
0.0ANALYTICS
bagyo reached CRAN as a Philippine tropical cyclone dataset, with its tags stamped out of order.
◆ Current state
A data package distributing Philippine Area of Responsibility tropical cyclone records, developed through 2024 pre-releases and accepted by CRAN in early 2026. The substantive release is v0.2.0: 2021 and 2022 typhoon data added, an unexported helper for downloading cyclone reports, CITATION.cff, an R 4.1 dependency for the base pipe, and a full pass over vignettes, tests and README. The v0.1.1 tag announcing the first CRAN release carries no content and is stamped two hours after v0.2.0.
◆ Where it's heading
The package is establishing itself as a citable, yearly-updated dataset rather than a one-off scrape — the download helper and the '2022 data and general yearly upkeep' commit both point at a recurring refresh, and the CRAN DOI and CITATION file exist so the data can be cited in papers. It sits alongside the same maintainer's other public-health and survey data packages, which received matching repository upkeep in the same month.
◆ Prediction
Expect an annual data release adding the next typhoon season, since that is the only recurring change in the history and the download helper was written to support it.
rATTAINS
0.0ANALYTICS
The R client for EPA water quality data spent two releases undoing its own promises about data shape.
◆ Current state
rATTAINS wraps the EPA's ATTAINS API, which holds state water quality assessments and impaired-waters listings. The package reached 1.0.0 by promising stable, consistently rectangled return structures, then walked that promise back in 1.1.0 when it dropped the dependency doing the rectangling. As of 1.2.0 it also requires an API key, because ATTAINS itself began requiring one in May 2026.
◆ Where it's heading
The direction is toward a thinner, lower-maintenance wrapper. Caching went in 0.1.4 when hoardr was archived, tidyjson and janitor went earlier, tibblify went in 1.1.0, and each removal handed a little more data-shaping responsibility back to the user — the current advice is to pass .unnest = FALSE and rectangle the results with whatever tidying package you prefer. Release cadence is slow and mostly reactive: upstream API terms, archived dependencies, and compatibility with test tooling account for most of the log. The package's centre of gravity is staying installable and honest about what ATTAINS returns rather than smoothing it over.
◆ Prediction
Given the pattern, the next release is likelier to be a compatibility or upstream-driven fix than new endpoint coverage; how the API key requirement affects users in scripted and CI contexts is the obvious open question the entries do not yet answer.
Alternatives to bagyo and rATTAINS
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 bagyo or rATTAINS.
GeneNMF
GeneNMF rebuilt how it derives meta-programs, changing every result it had produced.
rempsyc
Publication-ready psychology tables and plots, tracking APA style as closely as the software allows.
sdsfun
A spatial-statistics utility package exists to be depended on, and is built accordingly.
eulerr
The area-proportional Euler diagram package is finished software, and maintained like it.
intsurv
A Cox cure-rate model package woke up after four years to simplify its own interface.
See all bagyo alternatives → · See all rATTAINS alternatives →
Recent activity from bagyo and rATTAINS
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agorATTAINSATTAINS now requires an API key, and the package follows
- 7mo agobagyobagyo v0.1.1
- 7mo agobagyo2021 and 2022 typhoon data added
- 8mo agorATTAINSThe tibblify dependency goes, and with it the stable data shapes ⚡
- 1y agorATTAINSTest suite updated for vcr v2
- 2y agobagyoPre-release for Zenodo archiving
- 2y agobagyoInitial pre-release
- 3y agorATTAINS1.0.0 commits to stable return structures via tibblify
- 3y agorATTAINSCaching removed after hoardr was archived
- 4y agorATTAINSRequests retry on timeout, with offline detection
Frequently asked questions
What is the difference between bagyo and rATTAINS?
They serve adjacent needs but don't currently overlap on shipped themes. bagyo and rATTAINS 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 bagyo better than rATTAINS?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. bagyo and rATTAINS 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 bagyo?
Top bagyo alternatives in Analytics are ranked by recent ship velocity. Browse the "bagyo alternatives" section above for the current picks, or visit /alternatives/bagyo for the full list with editorial commentary on each.
What are the best alternatives to rATTAINS?
Top rATTAINS alternatives in Analytics are ranked by recent ship velocity. Browse the "rATTAINS alternatives" section above for the current picks, or visit /alternatives/rattains for the full list with editorial commentary on each.