simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
A side-by-side editorial comparison of arcgisutils and lavaanExtra — release velocity, themes, recent moves, and the top alternatives to consider.
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.
SEM reporting helpers converging on APA output, one CRAN resubmission at a time.
lavaanExtra provides shorthand syntax and formatted output around lavaan structural equation models - write_lavaan() to build model strings, and nice_* functions for fit tables, plots, and modification indices. Three of the six visible releases exist only to satisfy CRAN resubmission: a unicode problem, a dependency version check, tests running without suggested packages. The substance sits in 0.1.5, 0.1.8, and 0.1.9.
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.
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.
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.
lavaanExtra provides shorthand syntax and formatted output around lavaan structural equation models - write_lavaan() to build model strings, and nice_* functions for fit tables, plots, and modification indices. Three of the six visible releases exist only to satisfy CRAN resubmission: a unicode problem, a dependency version check, tests running without suggested packages. The substance sits in 0.1.5, 0.1.8, and 0.1.9.
The package generalises its own vocabulary as it goes: lavaan_ind() became lavaan_defined() once it turned out to extract any user-defined parameter, and lavaan_cov() was split so lavaan_cor() covers actual correlations. Methodological positions are taken alongside the API - dropping the estimate argument from lavaan_reg() to force reporting both standardized and unstandardized values, and updating the RMSEA benchmark to Schreiber (2017). Rémi Thériault maintains it next to rempsyc, which formats output to match. Note that 0.1.5 restates the whole 0.1.4.x development series in one body.
The pattern points to another nice_* helper aimed at a reporting step that currently needs hand formatting, arriving with the usual CRAN resubmission behind it.
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 lavaanExtra.
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
A raster-to-terra migration is the only readable change in a feed of merge notes.
A nycflights13 generator whose recent work is all about the data being right.
Conditional density and log-likelihood fill out a vine copula regression package.
A drop-in string API for base R, kept alive by upstream check failures.
From a bundled hospital dataset to a live CMS API client.
See all arcgisutils alternatives → · See all lavaanExtra alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. arcgisutils and lavaanExtra 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. arcgisutils and lavaanExtra 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.
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.
Top lavaanExtra alternatives in Analytics are ranked by recent ship velocity. Browse the "lavaanExtra alternatives" section above for the current picks, or visit /alternatives/lavaanextra for the full list with editorial commentary on each.