TAF
TAF keeps turning ICES stock assessments into reproducible, dependency-pinned projects.
A side-by-side editorial comparison of geomander and modeltime.ensemble — release velocity, themes, recent moves, and the top alternatives to consider.
A redistricting toolkit that grows mostly by wiring in new public data sources
geomander provides geographic tools for redistricting analysis in R — matching and aggregating across block, VTD and district geometries, spatial diagnostics, and download helpers for the datasets the field relies on. Recent work splits between data access, with fetchers added for Jeffrey B. Lewis's historical congressional districts and RPV Near Me, and performance, with 2.5.0 delivering large speed gains in geo_match().
modeltime.ensemble wakes after four years, and the work is all tune 2.0 compatibility.
modeltime.ensemble builds average, weighted and stacked ensembles over modeltime forecast models. After a four-year gap it shipped twice in a fortnight during August and September 2025, both releases devoted to tracking breaking changes in tidymodels' tune package — new resampling column conventions, key uniqueness across resamples, recipe preparation. The tidyverse dependency was dropped in the same pass.
geomander provides geographic tools for redistricting analysis in R — matching and aggregating across block, VTD and district geometries, spatial diagnostics, and download helpers for the datasets the field relies on. Recent work splits between data access, with fetchers added for Jeffrey B. Lewis's historical congressional districts and RPV Near Me, and performance, with 2.5.0 delivering large speed gains in geo_match().
The package is consolidating as infrastructure rather than expanding its analytical surface. Each release either adds a source of redistricting data that users would otherwise download by hand, or makes the core geographic matching operations faster and more correct — the normalized global Moran's I correction and the block-level geometry mismatch fix both fall in the second category. geo_match() being the target of the most recent release confirms where the hot path is.
With geo_match() now optimised, the remaining friction is in the download helpers, several of which have needed repair after upstream changes; expect the next release to consolidate or harden those fetchers rather than add analysis functions.
modeltime.ensemble builds average, weighted and stacked ensembles over modeltime forecast models. After a four-year gap it shipped twice in a fortnight during August and September 2025, both releases devoted to tracking breaking changes in tidymodels' tune package — new resampling column conventions, key uniqueness across resamples, recipe preparation. The tidyverse dependency was dropped in the same pass.
This is a package whose forecasting capability was settled by 2021 — recursive ensembles, per-series calibration — and whose recent life is dictated entirely by upstream tidymodels churn. New contributors did that compatibility work, including one from the tidymodels side. It now requires tune 2.0.0 and modeltime.resample 0.3.0, pinning it to the current tidymodels generation rather than straddling versions.
Expect the next release to follow the next tune or modeltime.resample breaking change rather than to introduce new ensembling methods.
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 geomander or modeltime.ensemble.
TAF keeps turning ICES stock assessments into reproducible, dependency-pinned projects.
parallelDist is in pure preservation mode — one build fix every few years.
Cairo finally catches R's graphics engine, all the way to GE API 16.
rjdqa keeps refining one screen: the seasonal adjustment quality dashboard
epikit narrows to field-epidemiology helpers, handing proportions to a sibling package
SimInf 10.0 turns an epidemic simulator into a tool that fits models to real time series
See all geomander alternatives → · See all modeltime.ensemble alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. geomander and modeltime.ensemble 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. geomander and modeltime.ensemble 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 geomander alternatives in Analytics are ranked by recent ship velocity. Browse the "geomander alternatives" section above for the current picks, or visit /alternatives/geomander-r for the full list with editorial commentary on each.
Top modeltime.ensemble alternatives in Analytics are ranked by recent ship velocity. Browse the "modeltime.ensemble alternatives" section above for the current picks, or visit /alternatives/modeltime-ensemble for the full list with editorial commentary on each.