arcgisutils
The R-ArcGIS plumbing layer grew a portal administration API and geoprocessing job support.
A side-by-side editorial comparison of bagyo and bbk — 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.
One R interface is absorbing the world's central bank data portals, one API at a time.
bbk began as a Bundesbank client and has become a single R interface to central bank statistics generally: the ECB, BIS, and the national banks of Switzerland, Canada, the UK, France, Spain, Austria, Sweden, Norway, Portugal, Japan, Poland, the Czech Republic, and now Brazil and Mexico. Each provider gets a consistent set of verbs — a data function, a dimension function for the dataflow structure, and provider-specific extras like PRIBOR or CZEONIA fixings. Response caching, data.table returns, and an updated_after argument for incremental retrieval are shared plumbing rather than per-provider features.
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.
bbk began as a Bundesbank client and has become a single R interface to central bank statistics generally: the ECB, BIS, and the national banks of Switzerland, Canada, the UK, France, Spain, Austria, Sweden, Norway, Portugal, Japan, Poland, the Czech Republic, and now Brazil and Mexico. Each provider gets a consistent set of verbs — a data function, a dimension function for the dataflow structure, and provider-specific extras like PRIBOR or CZEONIA fixings. Response caching, data.table returns, and an updated_after argument for incremental retrieval are shared plumbing rather than per-provider features.
The expansion is steady and the integration work is what makes it more than a list of wrappers: arguments introduced for one provider get pushed to the others, dimension introspection is being generalised across dataflows, and the bug fixes in recent releases are almost all about the same class of problem — series with missing observations, unsupported frequency codes, or date/value misalignment breaking a parser written for a tidier feed. The maintainer ships the same infrastructure across their packages in lockstep; bbk 0.9.0 and the sibling treasury package's 0.5.0 landed identical opt-in caching within minutes of each other. Geography is the visible frontier, but consistency across an increasingly ragged set of upstream APIs is the actual work.
Expect more national central banks to be added on the same template, and the newer providers to be retrofitted with the dimension and updated_after functions the older ones already have.
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 bbk.
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.
The bridge between Stata/SPSS labelled data and tidy R keeps widening, one integration at a time.
flashlight hit 1.0 by giving away its SHAP feature and making most of its API internal.
A palette generator became a palette platform — and changed the metric behind every color it picks.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. bagyo and bbk 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 bbk 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 bbk alternatives in Analytics are ranked by recent ship velocity. Browse the "bbk alternatives" section above for the current picks, or visit /alternatives/bbk for the full list with editorial commentary on each.