arcgisutils
The R-ArcGIS plumbing layer grew a portal administration API and geoprocessing job support.
A side-by-side editorial comparison of dissmapr and randomwalk — release velocity, themes, recent moves, and the top alternatives to consider.
dissmapr spent its first releases becoming citable rather than adding methods.
dissmapr provides an R workflow for compositional dissimilarity and turnover — occurrence data through spatial gridding and environmental linkage to order-wise dissimilarity and bioregional mapping. All three releases to date are infrastructure: a first citable archive in June 2026, then a maturity release aligning the package with the B-Cubed software development guide. The ten-function pipeline described in the notes has not changed across them.
randomwalk spent every release getting an R simulation to run in the browser, not on a server.
A random walk and fractal-growth simulation package whose entire visible history is about its browser deployment. Six releases in four weeks moved a Shinylive dashboard from a blank black page to a working app — WebAssembly mounted from GitHub releases, CORS resolved by same-origin serving, missing plotting dependencies installed in-browser, then an async version using crew workers with its own debug log. A correctness fix followed, adding termination-position validation so simulations stop producing isolated pixels, and the most recent release publishes the package itself as a webR binary repository.
dissmapr provides an R workflow for compositional dissimilarity and turnover — occurrence data through spatial gridding and environmental linkage to order-wise dissimilarity and bioregional mapping. All three releases to date are infrastructure: a first citable archive in June 2026, then a maturity release aligning the package with the B-Cubed software development guide. The ten-function pipeline described in the notes has not changed across them.
The work is compliance-shaped rather than method-shaped: explicit @importFrom in place of whole-namespace imports, library() calls removed from package code, roughly 11 MB of development caches dropped, a runnable README quick-start, and Zenodo archival with CITATION.cff and codemeta.json. dissmapr moves in lockstep with its B-Cubed sibling invasimapr — both tagged 0.1.0 within three minutes of each other and 0.2.0 on the same day — so releases here reflect project-wide standards deadlines more than package-specific work. The stated roadmap of additional ecological distance metrics has not yet landed.
With standards work now signed off and R CMD check clean, the next release is the first real chance for the roadmap items — additional ecological distance metrics — to arrive.
A random walk and fractal-growth simulation package whose entire visible history is about its browser deployment. Six releases in four weeks moved a Shinylive dashboard from a blank black page to a working app — WebAssembly mounted from GitHub releases, CORS resolved by same-origin serving, missing plotting dependencies installed in-browser, then an async version using crew workers with its own debug log. A correctness fix followed, adding termination-position validation so simulations stop producing isolated pixels, and the most recent release publishes the package itself as a webR binary repository.
The package is being built as a browser artifact first and an R package second: the readme, the vignettes and the release notes all point at a hosted dashboard rather than at library(). The last release completes that by making the compiled WebAssembly build installable by anyone via webr::install(), which turns the deployment work into something reusable outside this project. Version numbers are unreliable here — v0.2.0 was published two weeks after v1.0.2 — so read the dates, not the tags.
With the webR repository published, the next work most likely moves back to the simulation itself, though the entries give no direct evidence of planned features.
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 dissmapr or randomwalk.
The R-ArcGIS plumbing layer grew a portal administration API and geoprocessing job support.
A parametric bootstrap for state-space models, shipped and then left alone.
A Brazilian housing-data palette package went from internal tooling to public 1.0 in five days.
The bridge between Stata/SPSS labelled data and tidy R keeps widening, one integration at a time.
flashlight hit 1.0 by giving away its SHAP feature and making most of its API internal.
A palette generator became a palette platform — and changed the metric behind every color it picks.
See all dissmapr alternatives → · See all randomwalk alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r package — within Analytics. dissmapr and randomwalk 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. dissmapr and randomwalk 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 dissmapr alternatives in Analytics are ranked by recent ship velocity. Browse the "dissmapr alternatives" section above for the current picks, or visit /alternatives/dissmapr for the full list with editorial commentary on each.
Top randomwalk alternatives in Analytics are ranked by recent ship velocity. Browse the "randomwalk alternatives" section above for the current picks, or visit /alternatives/randomwalk for the full list with editorial commentary on each.