← Back to home
Comparison · Analytics

arcgisutils vs rphylopic

A side-by-side editorial comparison of arcgisutils and rphylopic — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:r-package

arcgisutils vs rphylopic: at a glance

Featurearcgisutilsrphylopic
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesarcgis, geospatial, api-client, authenticationphylogenetics, data-visualization, r-package, ggplot2
Last editorial update46m ago4h ago
WebsiteVisit →Visit →

What is arcgisutils?

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.

Read the full arcgisutils trajectory →

What is rphylopic?

The R package that puts organism silhouettes on plots keeps widening where they can be drawn.

rphylopic fetches PhyloPic silhouettes and places them into R graphics — base plots, ggplot2 layers, legends, and now phylogenetic trees and igraph networks. The 1.x line has been consistent about two things: adding a new plotting context per release, and steadily replacing its early sizing vocabulary with explicit width and height arguments. Attribution handling is unusually developed for a package this size, with permalinks and per-image credit built into the retrieval functions.

Read the full rphylopic trajectory →

arcgisutils vs rphylopic: editorial side-by-side

A
arcgisutils
ANALYTICS
0.0

The R-ArcGIS plumbing layer grew a portal administration API and geoprocessing job support.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

R
rphylopic
ANALYTICS
0.0

The R package that puts organism silhouettes on plots keeps widening where they can be drawn.

◆ Current state

rphylopic fetches PhyloPic silhouettes and places them into R graphics — base plots, ggplot2 layers, legends, and now phylogenetic trees and igraph networks. The 1.x line has been consistent about two things: adding a new plotting context per release, and steadily replacing its early sizing vocabulary with explicit width and height arguments. Attribution handling is unusually developed for a package this size, with permalinks and per-image credit built into the retrieval functions.

◆ Where it's heading

Development is expanding the set of places a silhouette can appear rather than changing what the package does. Base plots came first, then ggplot2 aesthetics and legend glyphs, then trees, then network vertices via an igraph shape registered automatically when both packages load. The other running thread is defensive maintenance against upstream churn: retries on failed API calls, fixes for ggplot2 4.0.0, and now an in-memory cache so repeated calls stop hammering the PhyloPic API. The ysize and size deprecation, opened in 1.5.0, is now complete and the arguments are scheduled for removal.

◆ Prediction

The deprecated ysize and size arguments look set to be removed in the next release, and on the pattern of the last four, another plotting context is a likelier addition than a change to the retrieval layer.

Alternatives to arcgisutils and rphylopic

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 rphylopic.

See all arcgisutils alternatives → · See all rphylopic alternatives →

Recent activity from arcgisutils and rphylopic

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1mo agorphylopicSilhouettes become igraph vertices; API responses cached
  2. 8mo agorphylopicBase R phylogenies gain silhouette annotation
  3. 10mo agoarcgisutilsPortal administration and geoprocessing jobs join the utility layer
  4. 1y agoarcgisutilsIntegers no longer encoded as floats in feature updates
  5. 1y agorphylopicExplicit width and height replace the old sizing arguments
  6. 2y agorphylopicSilhouette legends and attribution permalinks
  7. 2y agoarcgisutilsFirst stable release rebuilds token handling around a token store
  8. 2y agorphylopicSilhouette resolution helper and safer colour defaults
  9. 2y agorphylopicRendering dependencies bumped for grImport2 and rsvg

Frequently asked questions

What is the difference between arcgisutils and rphylopic?

Both compete on the same themes — r-package — within Analytics. arcgisutils and rphylopic 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 arcgisutils better than rphylopic?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. arcgisutils and rphylopic 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 arcgisutils?

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.

What are the best alternatives to rphylopic?

Top rphylopic alternatives in Analytics are ranked by recent ship velocity. Browse the "rphylopic alternatives" section above for the current picks, or visit /alternatives/rphylopic for the full list with editorial commentary on each.