← Back to home
Comparison · Analytics

mapSpain vs vellum

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

mapSpain vs vellum: at a glance

FeaturemapSpainvellum
SectorAnalyticsAnalytics
Velocity score0.05.0
Sparks · 30d00
Top themesspain, administrative-boundaries, geospatial, httr2r-graphics, rendering-engine, linting, accessibility
Last editorial update1h ago52m 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 vellum?

vellum's bugs are now found by using it, not testing it — the downstream grammar is doing the QA.

The rendering engine shipped nine releases in the two weeks around the end of July, six of them on a single day. Almost every entry is a correctness fix in a capability that worked when drawn and failed when measured, or worked in isolation and failed in composition. The release notes are unusually forensic: each one states the mechanism, the observable symptom, and why the fix mirrors the draw path rather than reimplementing it.

Read the full vellum trajectory →

mapSpain vs vellum: 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.

V
vellum
ANALYTICS
5.0

vellum's bugs are now found by using it, not testing it — the downstream grammar is doing the QA.

◆ Current state

The rendering engine shipped nine releases in the two weeks around the end of July, six of them on a single day. Almost every entry is a correctness fix in a capability that worked when drawn and failed when measured, or worked in isolation and failed in composition. The release notes are unusually forensic: each one states the mechanism, the observable symptom, and why the fix mirrors the draw path rather than reimplementing it.

◆ Where it's heading

The pivotal detail is stated outright in 0.6.3 — the first bug in the series found by using the engine from vellumplot rather than testing it in isolation. Every release since names the downstream as the source: the contrast rule's false positives, the lint rules that fired on all five sample plots, the keyed roundrect batch. A rendering engine with a real grammar built on top of it is now getting the integration coverage that unit tests structurally cannot provide, and the fixes are converging on one theme: the measurement path and the draw path must not drift.

◆ Prediction

Expect the release rate to fall as the vellumplot integration surface is exhausted, with remaining work concentrated in the lint rule set now that it is meant to gate builds rather than just inform.

Alternatives to mapSpain and vellum

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 vellum.

See all mapSpain alternatives → · See all vellum alternatives →

Recent activity from mapSpain and vellum

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

  1. 11d agovellumLinter grows to 20 rules and stops firing on every plot
  2. 13d agovellumAnimated SVGs no longer blink once and vanish or play in reverse
  3. 13d agovellumPick table now reports device pixels instead of two coordinate systems
  4. 14d agovellumContrast rule stops flagging every plot; gridlines become PDF artifacts
  5. 14d agovellumgrobwidth and grobheight now measure wrapped text, not the unwrapped line
  6. 14d agovellumKeyed roundrect becomes a real batch after downstream integration exposes it
  7. 1mo agomapSpainInternal helper refactor with the public API held fixed
  8. 4mo agomapSpainQuery timeout becomes configurable
  9. 7mo agomapSpain1.0.0 rebuilds on httr2 and invalidates every cache
  10. 1y agomapSpainComarcas and simplified INE geometries added
  11. 1y agomapSpainComarca types split across four official sources
  12. 1y agomapSpainAdapted to the SIANE 2024 databases

Frequently asked questions

What is the difference between mapSpain and vellum?

They serve adjacent needs but don't currently overlap on shipped themes. vellum is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is mapSpain better than vellum?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. vellum is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. 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 vellum?

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