n2kanalysis
n2kanalysis has spent eight years wiring INLA models to an S3 bucket.
A side-by-side editorial comparison of mapSpain and tmap — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Two years after a from-scratch rewrite, tmap is filling in the layers v4 promised.
tmap draws thematic maps in R across static and interactive modes. The 4.0 rewrite replaced the layer syntax with explicit visual variables, scales, legends and charts, and opened the package to extensions; the 4.x line since has been steady capability fill-in. The 4.4 release adds tm_circles with fixed unit-based radii, a blend argument on every layer, and hitboxes so small objects stay clickable in view mode.
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.
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.
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.
tmap draws thematic maps in R across static and interactive modes. The 4.0 rewrite replaced the layer syntax with explicit visual variables, scales, legends and charts, and opened the package to extensions; the 4.x line since has been steady capability fill-in. The 4.4 release adds tm_circles with fixed unit-based radii, a blend argument on every layer, and hitboxes so small objects stay clickable in view mode.
The extension mechanism introduced in 4.0 is where the interesting work is migrating: PMTiles support arrived through a separate experimental tmap.sources package, mode cycling became configurable via tmap_mode_pool() so packages like tmap.mapgl can register themselves, and shiny dispatch methods were added specifically to let other modes integrate. The core package is increasingly a rendering contract that satellite packages plug into.
Expect more rendering backends to land as sibling packages rather than in tmap itself, with the core continuing to absorb the dispatch and mode-management plumbing they need.
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 tmap.
n2kanalysis has spent eight years wiring INLA models to an S3 bucket.
A Fortran-descended optimizer got thread-safe, then found two flags that never worked.
ggstatsplot reached 1.0 by adding tests, having outsourced its statistics years ago.
collapse got a JSS paper and a 7x fmean speedup in the same release.
gtsummary is quietly rebuilding itself around analysis results data, one table verb at a time.
broadcast is filling in NumPy-style array broadcasting for R, operator by operator.
See all mapSpain alternatives → · See all tmap alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. mapSpain and tmap 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. mapSpain and tmap 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 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.
Top tmap alternatives in Analytics are ranked by recent ship velocity. Browse the "tmap alternatives" section above for the current picks, or visit /alternatives/tmap-r for the full list with editorial commentary on each.