eulerr
The area-proportional Euler diagram package is finished software, and maintained like it.
A side-by-side editorial comparison of bagyo and rdataone — release velocity, themes, recent moves, and the top alternatives to consider.
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.
The R client for DataONE ships slow, correctness-focused maintenance
rdataone is the R client for the DataONE federated research-data network, handling authentication, upload and retrieval of data packages against member nodes. Recent work is concentrated on correctness in the upload path — rightsHolder persistence, public-read flags applied across all objects in a package, and edge cases in archive() — plus dependency trimming. The feed's version stamps are unreliable: 2.2.2 carries a later publication date than 2.3.0, which cites 2.2.2 as its own predecessor.
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.
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.
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.
rdataone is the R client for the DataONE federated research-data network, handling authentication, upload and retrieval of data packages against member nodes. Recent work is concentrated on correctness in the upload path — rightsHolder persistence, public-read flags applied across all objects in a package, and edge cases in archive() — plus dependency trimming. The feed's version stamps are unreliable: 2.2.2 carries a later publication date than 2.3.0, which cites 2.2.2 as its own predecessor.
This is long-cycle infrastructure maintenance, not feature development. Release intervals run to years, and the content is dominated by access-control correctness, CRAN compliance and TLS/platform fixes rather than new client capability. The one consistent thread is hardening how permissions and checksums survive a round trip to a member node.
Expect continued low-frequency releases driven by CRAN check failures and platform TLS changes, with any functional work staying in the upload and permissions path rather than the query surface.
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 rdataone.
The area-proportional Euler diagram package is finished software, and maintained like it.
A Cox cure-rate model package woke up after four years to simplify its own interface.
A phyloseq toolbox keeps absorbing metabarcoding methods, and has started splitting into a family.
The R-ArcGIS plumbing layer grew a portal administration API and geoprocessing job support.
A parametric bootstrap for state-space models, shipped and then left alone.
A Brazilian housing-data palette package went from internal tooling to public 1.0 in five days.
See all bagyo alternatives → · See all rdataone alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. bagyo and rdataone 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. bagyo and rdataone 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 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.
Top rdataone alternatives in Analytics are ranked by recent ship velocity. Browse the "rdataone alternatives" section above for the current picks, or visit /alternatives/rdataone for the full list with editorial commentary on each.