← Back to home
Comparison · Analytics

arcgisutils vs ggmapinset

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

Shared themes:geospatial

arcgisutils vs ggmapinset: at a glance

Featurearcgisutilsggmapinset
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesarcgis, geospatial, api-client, authenticationggplot2, geospatial, inset-maps, extension-api
Last editorial update46m ago2h 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 ggmapinset?

A ggplot2 inset-map extension that is now infrastructure for other packages

ggmapinset adds magnified inset panels to ggplot2 sf maps, handling the coordinate transformation, the inset frame and the sf-related stat layers that have to follow it. The 0.5.0 release is aimed less at end users than at extension authors: coerce_centre() is a new extension point required by sibling package ggautomap, and the inset parameter drops NA in favour of waiver() as its default. It comes from cidm-ph, alongside nswgeo.

Read the full ggmapinset trajectory →

arcgisutils vs ggmapinset: 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.

G
ggmapinset
ANALYTICS
0.0

A ggplot2 inset-map extension that is now infrastructure for other packages

◆ Current state

ggmapinset adds magnified inset panels to ggplot2 sf maps, handling the coordinate transformation, the inset frame and the sf-related stat layers that have to follow it. The 0.5.0 release is aimed less at end users than at extension authors: coerce_centre() is a new extension point required by sibling package ggautomap, and the inset parameter drops NA in favour of waiver() as its default. It comes from cidm-ph, alongside nswgeo.

◆ Where it's heading

The package has moved steadily from feature to foundation. 0.3.0 replaced confusing parameter names and rebuilt everything on stat_sf_inset() so coordinate limits stayed correct, then exposed transform_to_inset() explicitly for extension developers. 0.4.0 generalised inset shapes beyond circles to rectangles and arbitrary sf geometries. 0.5.0 continues in that direction, changing defaults in ways that require downstream extensions to adapt — the cost of being depended upon.

◆ Prediction

Expect further extension points driven by what ggautomap and the other cidm-ph mapping packages need, with the user-facing inset API staying largely settled after the shape generalisation.

Alternatives to arcgisutils and ggmapinset

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

See all arcgisutils alternatives → · See all ggmapinset alternatives →

Recent activity from arcgisutils and ggmapinset

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

  1. 4mo agoggmapinsetNew extension point for ggautomap; waiver() replaces NA
  2. 10mo agoarcgisutilsPortal administration and geoprocessing jobs join the utility layer
  3. 1y agoggmapinsetRectangular and arbitrary sf inset shapes
  4. 1y agoarcgisutilsIntegers no longer encoded as floats in feature updates
  5. 2y agoarcgisutilsFirst stable release rebuilds token handling around a token store
  6. 3y agoggmapinsetRebuilt on stat_sf_inset() with corrected coordinate limits

Frequently asked questions

What is the difference between arcgisutils and ggmapinset?

Both compete on the same themes — geospatial — within Analytics. arcgisutils and ggmapinset 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 ggmapinset?

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

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