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 dissmapr — 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.
dissmapr spent its first releases becoming citable rather than adding methods.
dissmapr provides an R workflow for compositional dissimilarity and turnover — occurrence data through spatial gridding and environmental linkage to order-wise dissimilarity and bioregional mapping. All three releases to date are infrastructure: a first citable archive in June 2026, then a maturity release aligning the package with the B-Cubed software development guide. The ten-function pipeline described in the notes has not changed across them.
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.
dissmapr provides an R workflow for compositional dissimilarity and turnover — occurrence data through spatial gridding and environmental linkage to order-wise dissimilarity and bioregional mapping. All three releases to date are infrastructure: a first citable archive in June 2026, then a maturity release aligning the package with the B-Cubed software development guide. The ten-function pipeline described in the notes has not changed across them.
The work is compliance-shaped rather than method-shaped: explicit @importFrom in place of whole-namespace imports, library() calls removed from package code, roughly 11 MB of development caches dropped, a runnable README quick-start, and Zenodo archival with CITATION.cff and codemeta.json. dissmapr moves in lockstep with its B-Cubed sibling invasimapr — both tagged 0.1.0 within three minutes of each other and 0.2.0 on the same day — so releases here reflect project-wide standards deadlines more than package-specific work. The stated roadmap of additional ecological distance metrics has not yet landed.
With standards work now signed off and R CMD check clean, the next release is the first real chance for the roadmap items — additional ecological distance metrics — to arrive.
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 dissmapr.
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 dissmapr 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 dissmapr 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 dissmapr 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 dissmapr alternatives in Analytics are ranked by recent ship velocity. Browse the "dissmapr alternatives" section above for the current picks, or visit /alternatives/dissmapr for the full list with editorial commentary on each.