← Back to home
Comparison · Analytics

arcgisutils vs intsurv

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

Shared themes:r-package

arcgisutils vs intsurv: at a glance

Featurearcgisutilsintsurv
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesarcgis, geospatial, api-client, authenticationsurvival-analysis, cure-models, censored-data, regularization
Last editorial update1h 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 intsurv?

A Cox cure-rate model package woke up after four years to simplify its own interface.

intsurv fits Cox cure rate models for right-censored survival data where event status may be uncertain — the case where you cannot tell whether a subject experienced the event or was never susceptible to it. The core has been stable since 2019: cox_cure() and its regularized counterpart cox_cure_net(), plus a weighted concordance index and a data simulator. After more than four years without a release, version 0.3.0 arrived in September 2025 and restructured how those two functions are configured rather than adding capability.

Read the full intsurv trajectory →

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

I
intsurv
ANALYTICS
0.0

A Cox cure-rate model package woke up after four years to simplify its own interface.

◆ Current state

intsurv fits Cox cure rate models for right-censored survival data where event status may be uncertain — the case where you cannot tell whether a subject experienced the event or was never susceptible to it. The core has been stable since 2019: cox_cure() and its regularized counterpart cox_cure_net(), plus a weighted concordance index and a data simulator. After more than four years without a release, version 0.3.0 arrived in September 2025 and restructured how those two functions are configured rather than adding capability.

◆ Where it's heading

The package has reached the point where the methods are settled and the remaining work is ergonomics. Moving control parameters, M-step settings and penalty specification into cox_cure.control(), cox_cure.mstep() and cox_cure_net.penalty() follows the established R convention of separating tuning from the model formula, and it arrives long after the arguments accumulated. The C++ headers were placed in inst/include as early as 2019 so other packages could link against them, which suggests the implementation was always intended to be reused.

◆ Prediction

The gap between 0.2.2 and 0.3.0 makes cadence a poor basis for prediction. What the entries do support is that the interface rework is unfinished business rather than a prelude to new methods, so consolidation around the new helper functions is the likelier next step.

Alternatives to arcgisutils and intsurv

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

See all arcgisutils alternatives → · See all intsurv alternatives →

Recent activity from arcgisutils and intsurv

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

  1. 10mo agoarcgisutilsPortal administration and geoprocessing jobs join the utility layer
  2. 10mo agointsurvModel configuration moves into dedicated control functions
  3. 1y agoarcgisutilsIntegers no longer encoded as floats in feature updates
  4. 2y agoarcgisutilsFirst stable release rebuilds token handling around a token store
  5. 5y agointsurvCross-validated model selection and offset terms added
  6. 6y agointsurvC++ headers relocated so other packages can link them
  7. 7y agointsurvCox cure models for uncertain event status arrive
  8. 7y agointsurvParameter initialization methods added to the alpha
  9. 7y agointsurvAlpha cut for paper submission and simulation reproducibility

Frequently asked questions

What is the difference between arcgisutils and intsurv?

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

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

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