← Back to home
Comparison · Analytics

arcgisutils vs kde1d

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

Shared themes:r-package

arcgisutils vs kde1d: at a glance

Featurearcgisutilskde1d
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesarcgis, geospatial, api-client, authenticationdensity-estimation, kernel-methods, zero-inflation, cpp-library
Last editorial update2h ago1h 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 kde1d?

A univariate density estimator that added zero-inflated data and reopened its C++ API to do it.

kde1d estimates univariate densities with local polynomial kernel methods, handling bounded, discrete and now zero-inflated variables through a single type argument, with the numerical work in a header-only C++ library usable outside R. Version 1.1.0 added the zero-inflated discrete-continuous mixture case and shipped a new C++ API as an explicit breaking change; 1.1.1 followed in June with auto-generated notes and no description.

Read the full kde1d trajectory →

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

K
kde1d
ANALYTICS
0.0

A univariate density estimator that added zero-inflated data and reopened its C++ API to do it.

◆ Current state

kde1d estimates univariate densities with local polynomial kernel methods, handling bounded, discrete and now zero-inflated variables through a single type argument, with the numerical work in a header-only C++ library usable outside R. Version 1.1.0 added the zero-inflated discrete-continuous mixture case and shipped a new C++ API as an explicit breaking change; 1.1.1 followed in June with auto-generated notes and no description.

◆ Where it's heading

The package has alternated between performance work and widening the class of data it accepts. The 1.0.0 release was the performance milestone — FFT-based estimation, a better integration algorithm for the p, q and r functions, deterministic jittering replacing randomness, and standalone C++ headers. The 1.1.0 release is the scope milestone, adding a third data type to the two it already handled. Releases come from the same maintainer as svines and cluster on shared dates, so changes in the underlying C++ surface across the vine and density stack tend to ship together.

◆ Prediction

With the C++ API deliberately reworked for standalone use at 1.1.0, further work most plausibly consolidates that interface rather than adding data types. What 1.1.1 actually changed is not readable from its body.

Alternatives to arcgisutils and kde1d

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

See all arcgisutils alternatives → · See all kde1d alternatives →

Recent activity from arcgisutils and kde1d

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

  1. 10mo agoarcgisutilsPortal administration and geoprocessing jobs join the utility layer
  2. 1y agokde1dkde1d 1.1.1
  3. 1y agokde1dZero-inflated mixtures and a new standalone C++ API
  4. 1y agoarcgisutilsIntegers no longer encoded as floats in feature updates
  5. 2y agoarcgisutilsFirst stable release rebuilds token handling around a token store
  6. 4y agokde1dBit-wise Boolean operations removed
  7. 5y agokde1ddkde1d() invisible output fixed
  8. 5y agokde1dValgrind false positive silenced
  9. 6y agokde1dqrng dependency dropped; undefined behaviour fixed

Frequently asked questions

What is the difference between arcgisutils and kde1d?

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

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

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