← Back to home
Comparison · Analytics

geomander vs modeltime.ensemble

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

geomander vs modeltime.ensemble: at a glance

Featuregeomandermodeltime.ensemble
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesredistricting, geospatial, political-data, r-packagetime series forecasting, ensembles, tidymodels, compatibility maintenance
Last editorial update58m ago7h ago
WebsiteVisit →Visit →

What is geomander?

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().

Read the full geomander trajectory →

What is modeltime.ensemble?

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.

Read the full modeltime.ensemble trajectory →

geomander vs modeltime.ensemble: editorial side-by-side

G
geomander
ANALYTICS
0.0

A redistricting toolkit that grows mostly by wiring in new public data sources

◆ Current state

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().

◆ Where it's heading

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.

◆ Prediction

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.

M0.0

modeltime.ensemble wakes after four years, and the work is all tune 2.0 compatibility.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

Expect the next release to follow the next tune or modeltime.resample breaking change rather than to introduce new ensembling methods.

Alternatives to geomander and modeltime.ensemble

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.

See all geomander alternatives → · See all modeltime.ensemble alternatives →

Recent activity from geomander and modeltime.ensemble

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

  1. 8mo agogeomanderLarge speed gains in geo_match()
  2. 11mo agomodeltime.ensembleRealigned for tune 2.0.0 resampling changes
  3. 11mo agomodeltime.ensembleDrops the tidyverse dependency ahead of tune 2.0
  4. 2y agogeomanderFetchers for Lewis historical districts and RPV Near Me
  5. 3y agogeomanderMaximum inscribed circle centres and BAF-to-VTD approximation
  6. 5y agomodeltime.ensemblePer-series calibration IDs and parallel refitting
  7. 5y agogeomanderRepository tag marking CRAN release 1.0.8
  8. 5y agomodeltime.ensembleRecursive ensembles for single and panel series

Frequently asked questions

What is the difference between geomander and modeltime.ensemble?

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.

Is geomander better than modeltime.ensemble?

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.

What are the best alternatives to geomander?

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.

What are the best alternatives to modeltime.ensemble?

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.