TidyDensity
A distribution catalogue that grows by one family at a time, and rarely breaks anything.
A side-by-side editorial comparison of arcgisutils and bagyo — release velocity, themes, recent moves, and the top alternatives to consider.
The R-ArcGIS plumbing layer grew a portal administration API and geoprocessing job support.
arcgisutils is the foundation of the R interface to ArcGIS — token handling, standardized httr2 request construction, and conversion between Esri JSON and R types for the packages built on top of it. Version 0.4.0 in October 2025 broadened it well past that role, adding functions to enumerate a portal's federated servers, users and resources, search content with automatic pagination, and submit geoprocessing jobs through new S7 classes. Token management has been on its current footing since 0.2.0, which moved tokens into an internal environment supporting multiple named keys.
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.
arcgisutils is the foundation of the R interface to ArcGIS — token handling, standardized httr2 request construction, and conversion between Esri JSON and R types for the packages built on top of it. Version 0.4.0 in October 2025 broadened it well past that role, adding functions to enumerate a portal's federated servers, users and resources, search content with automatic pagination, and submit geoprocessing jobs through new S7 classes. Token management has been on its current footing since 0.2.0, which moved tokens into an internal environment supporting multiple named keys.
The package is expanding from request plumbing into direct coverage of the ArcGIS Enterprise administrative and geoprocessing surface, which is a different kind of work from what it existed to support. Much of the new surface is marked experimental, so the shape is still being settled. Alongside the expansion runs steady API tidying — three deprecations and two functions removed outright in the same release, one of which dropped the dbplyr dependency.
The experimental sharing-API and URL-parsing functions are the most likely to change or firm up next, and the geoprocessing classes suggest job execution will be built out further. Given this package sits beneath arcgislayers, the deprecations introduced here will need a corresponding pass downstream.
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.
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 arcgisutils or bagyo.
A distribution catalogue that grows by one family at a time, and rarely breaks anything.
College football's open data client hit v2 — and now reports how many API calls you have left.
The USA phenology data client rebuilt its entire stack and stopped handing users -9999 as a number.
GeneNMF rebuilt how it derives meta-programs, changing every result it had produced.
Publication-ready psychology tables and plots, tracking APA style as closely as the software allows.
A spatial-statistics utility package exists to be depended on, and is built accordingly.
See all arcgisutils alternatives → · See all bagyo alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. arcgisutils and bagyo 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. arcgisutils and bagyo 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 arcgisutils alternatives in Analytics are ranked by recent ship velocity. Browse the "arcgisutils alternatives" section above for the current picks, or visit /alternatives/arcgisutils for the full list with editorial commentary on each.
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.