← Back to home
Comparison · Analytics

mapSpain vs redist

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

mapSpain vs redist: at a glance

FeaturemapSpainredist
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesspain, administrative-boundaries, geospatial, httr2r, redistricting, monte-carlo, sampling
Last editorial update4h ago1h ago
WebsiteVisit →Visit →

What is mapSpain?

mapSpain's 1.0.0 broke every user cache to get the package onto modern foundations.

mapSpain provides administrative boundaries, tile providers and geographic dictionaries for Spain, pulling from GISCO, SIANE, INE and IGN sources. The 1.0.0 release in January 2026 rebuilt it: requests moved to httr2, the cache reorganized into topic-based subfolders under tools::R_user_dir() instead of rappdirs, R 4.1 became the floor, and every function now returns tidy objects. Existing caches are explicitly incompatible and must be rebuilt.

Read the full mapSpain trajectory →

What is redist?

redist keeps rewriting the sampler underneath a district-drawing API it has held stable since 4.0.

redist simulates redistricting plans via sequential Monte Carlo, merge-split MCMC and short-burst optimization, and it is the analysis tool behind a good deal of published districting work. The user-facing shape was set by 4.0.1's constraint interface and the split of metrics into the redistmetrics package; since then the changes are in the algorithms. The most consequential recent one replaces the SMC label-counting adjustment with a backward kernel that removes approximation error outright.

Read the full redist trajectory →

mapSpain vs redist: editorial side-by-side

M
mapSpain
ANALYTICS
0.0

mapSpain's 1.0.0 broke every user cache to get the package onto modern foundations.

◆ Current state

mapSpain provides administrative boundaries, tile providers and geographic dictionaries for Spain, pulling from GISCO, SIANE, INE and IGN sources. The 1.0.0 release in January 2026 rebuilt it: requests moved to httr2, the cache reorganized into topic-based subfolders under tools::R_user_dir() instead of rappdirs, R 4.1 became the floor, and every function now returns tidy objects. Existing caches are explicitly incompatible and must be rebuilt.

◆ Where it's heading

The package has finished its modernization and moved into consolidation. 1.1.0 added a configurable query timeout and pinned httr2 for compatibility with giscoR, the sibling package it shares plumbing with; 1.2.0 was a declared internal-only refactor with the public API held fixed and the work described as AI-assisted with human review. The data-source expansion that characterized the 0.9.x and 0.10.x line — comarcas by type, simplified INE geometries, SIANE vintages — has paused while the foundations settle.

◆ Prediction

Expect a return to source coverage now that the refactor is done: new SIANE or INE vintages and additional boundary types are the pattern this package has repeated. The entries show no further architectural work queued.

R
redist
ANALYTICS
0.0

redist keeps rewriting the sampler underneath a district-drawing API it has held stable since 4.0.

◆ Current state

redist simulates redistricting plans via sequential Monte Carlo, merge-split MCMC and short-burst optimization, and it is the analysis tool behind a good deal of published districting work. The user-facing shape was set by 4.0.1's constraint interface and the split of metrics into the redistmetrics package; since then the changes are in the algorithms. The most consequential recent one replaces the SMC label-counting adjustment with a backward kernel that removes approximation error outright.

◆ Where it's heading

The direction is toward exactness and throughput at once — the new kernel is described as both eliminating approximation error and costing far less computation, and successive releases keep adding parallelism, most recently to the flip algorithm. Feature growth has moved into the optimization side, where short-burst gained multiple independent scorers and a Pareto frontier. The release notes are not a reliable ledger: 4.3.1 ships the identical text as 4.3.0.

◆ Prediction

Expect the remaining single-threaded algorithms to gain the chains-style parallelism that flip just received, following the pattern SMC established several releases ago.

Alternatives to mapSpain and redist

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 mapSpain or redist.

See all mapSpain alternatives → · See all redist alternatives →

Recent activity from mapSpain and redist

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

  1. 1mo agomapSpainInternal helper refactor with the public API held fixed
  2. 4mo agomapSpainQuery timeout becomes configurable
  3. 6mo agoredistParallel chains for redist_flip()
  4. 6mo agoredistPatch release reusing the 4.3.0 notes
  5. 7mo agomapSpain1.0.0 rebuilds on httr2 and invalidates every cache
  6. 10mo agoredistSMC backward kernel removes label-counting approximation error
  7. 1y agomapSpainComarcas and simplified INE geometries added
  8. 1y agomapSpainComarca types split across four official sources
  9. 1y agomapSpainAdapted to the SIANE 2024 databases
  10. 2y agoredistMulti-objective short-burst search with Pareto frontier
  11. 3y agoredistredist_ci interface and faster loop-erased random walk
  12. 4y agoredistredist_constr() unifies constraints and admits user-defined ones

Frequently asked questions

What is the difference between mapSpain and redist?

They serve adjacent needs but don't currently overlap on shipped themes. mapSpain and redist 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 mapSpain better than redist?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. mapSpain and redist 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 mapSpain?

Top mapSpain alternatives in Analytics are ranked by recent ship velocity. Browse the "mapSpain alternatives" section above for the current picks, or visit /alternatives/mapspain for the full list with editorial commentary on each.

What are the best alternatives to redist?

Top redist alternatives in Analytics are ranked by recent ship velocity. Browse the "redist alternatives" section above for the current picks, or visit /alternatives/redist-r for the full list with editorial commentary on each.