← Back to home
Comparison · Analytics

arcgisutils vs probmed

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

arcgisutils vs probmed: at a glance

Featurearcgisutilsprobmed
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesarcgis, geospatial, api-client, authenticationcausal mediation, effect size, semiparametric inference, cross-fitting
Last editorial update45m ago6h 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 probmed?

probmed went from one probabilistic effect size to a family of them in sixteen days.

probmed computes P_med, a scale-free probabilistic effect size for causal mediation, as part of the Data-Wise mediationverse alongside medfit, medsim and RMediation. Three releases in three weeks took it from a single estimator to four additional families built on a shared cross-fitted corner-EIF core, covering gauge-calibrated, incremental-elasticity and Sobol variance-share versions of the proportion mediated. Distribution is GitHub and r-universe rather than CRAN, with a load-bearing Remotes pin on medfit.

Read the full probmed trajectory →

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

P
probmed
ANALYTICS
0.0

probmed went from one probabilistic effect size to a family of them in sixteen days.

◆ Current state

probmed computes P_med, a scale-free probabilistic effect size for causal mediation, as part of the Data-Wise mediationverse alongside medfit, medsim and RMediation. Three releases in three weeks took it from a single estimator to four additional families built on a shared cross-fitted corner-EIF core, covering gauge-calibrated, incremental-elasticity and Sobol variance-share versions of the proportion mediated. Distribution is GitHub and r-universe rather than CRAN, with a load-bearing Remotes pin on medfit.

◆ Where it's heading

The pace is manuscript-driven — estimators arrive with their citations attached and vignettes alongside, and the 0.1.0 notes correct the estimand itself against a manuscript definition rather than fixing a bug in code. Each release adds inference machinery as well as point estimates: percentile-bootstrap intervals and Fieller sets in 0.3.0, a deterministic MBCO interval in 0.2.0 that avoids resampling entirely. The gauge residual and the pmed_sensitivity() helper suggest a growing concern with when the estimand does not decompose at all.

◆ Prediction

0.3.0 shipped a sensitivity helper for shared mediator-outcome confounding and a diagnostic that flags non-decomposability, so the next release most likely extends that diagnostic side rather than adding a fifth estimator family.

Alternatives to arcgisutils and probmed

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

See all arcgisutils alternatives → · See all probmed alternatives →

Recent activity from arcgisutils and probmed

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

  1. 1mo agoprobmedFour estimator families on a cross-fitted corner-EIF core
  2. 2mo agoprobmedParallel mediators and a resampling-free MBCO interval
  3. 2mo agoprobmedFirst release: pmed() with the estimand corrected
  4. 10mo agoarcgisutilsPortal administration and geoprocessing jobs join the utility layer
  5. 1y agoarcgisutilsIntegers no longer encoded as floats in feature updates
  6. 2y agoarcgisutilsFirst stable release rebuilds token handling around a token store

Frequently asked questions

What is the difference between arcgisutils and probmed?

They serve adjacent needs but don't currently overlap on shipped themes. arcgisutils and probmed 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 probmed?

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

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