mlr3proba
mlr3proba is shedding weight as its survival work moves into sibling packages
A side-by-side editorial comparison of ggspatial and workflows — release velocity, themes, recent moves, and the top alternatives to consider.
ggspatial finishes its move off raster and onto terra
ggspatial puts spatial data into ggplot2. Its recent history is a single multi-year migration: terra support arrived alongside raster in 1.1.6, and by 1.1.10 terra is the default in the bundled data loaders while raster is described as deprecated. Everything between those two releases is ggplot2 compatibility patching.
The tidymodels pipeline grew a third stage, and it happens after the model runs.
workflows bundles a preprocessor and a model into one object that tidymodels can fit, tune and extract from. Version 1.3.0 added a post stage backed by the tailor package, wired through every generic a workflow supports — augment, tidy, tunable, tune_args, required_pkgs and parameter extraction. Version 1.2.0 added sparse data support so fit() and predict() accept dgCMatrix and sparse tibbles. Earlier releases in view are boundary tightening: erroring on unknown model modes, on trained recipes, and on silently ignored formula offsets.
ggspatial puts spatial data into ggplot2. Its recent history is a single multi-year migration: terra support arrived alongside raster in 1.1.6, and by 1.1.10 terra is the default in the bundled data loaders while raster is described as deprecated. Everything between those two releases is ggplot2 compatibility patching.
The package tracks the R spatial stack's own generational shift rather than setting direction itself — sf and stars support, then terra, then preparing S3 methods for the next ggplot2. Feature work is rare; the value it delivers is staying current with the layers underneath it.
The likely next step is completing the ggplot2 S3 method preparation that 1.1.10 started, with raster support eventually dropped rather than maintained in parallel.
workflows bundles a preprocessor and a model into one object that tidymodels can fit, tune and extract from. Version 1.3.0 added a post stage backed by the tailor package, wired through every generic a workflow supports — augment, tidy, tunable, tune_args, required_pkgs and parameter extraction. Version 1.2.0 added sparse data support so fit() and predict() accept dgCMatrix and sparse tibbles. Earlier releases in view are boundary tightening: erroring on unknown model modes, on trained recipes, and on silently ignored formula offsets.
The object is filling out into a complete pipeline description rather than a preprocessing-plus-model pair. Postprocessing is the structural addition — calibration and threshold selection were previously done by hand after prediction, outside anything tidymodels could tune or record — and the fact that it arrived integrated with tunable() and tune_args() rather than as a standalone step is the point. The rest of the arc is the steady tidymodels habit of converting silent guesses into errors.
Expect tailor postprocessors to spread through tune and workflowsets next, since the parameter and tuning generics were wired up first, and expect sparse support to extend to more engines after lightgbm.
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 ggspatial or workflows.
mlr3proba is shedding weight as its survival work moves into sibling packages
mlr3viz keeps the ecosystem's plots working while the plots themselves move out
mlr3tuning is rebuilding its async machinery under a stable public surface
timetk swallowed anomalize whole, then went quiet for two years
modelbased is turning marginal effects into a full contrast grammar
easystats' parameters package absorbs one more model class every few weeks
See all ggspatial alternatives → · See all workflows alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. ggspatial and workflows 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. ggspatial and workflows 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 ggspatial alternatives in Analytics are ranked by recent ship velocity. Browse the "ggspatial alternatives" section above for the current picks, or visit /alternatives/ggspatial for the full list with editorial commentary on each.
Top workflows alternatives in Analytics are ranked by recent ship velocity. Browse the "workflows alternatives" section above for the current picks, or visit /alternatives/workflows-r for the full list with editorial commentary on each.