← Back to home
Comparison · Analytics

mapSpain vs OpenCTI

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

mapSpain vs OpenCTI: at a glance

FeaturemapSpainOpenCTI
SectorAnalyticsAnalytics
Velocity score0.06.3
Sparks · 30d01
Top themesspain, administrative-boundaries, geospatial, httr2threat-intelligence, connector-marketplace, xtm-hub, workflow-governance
Last editorial update3h 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 OpenCTI?

OpenCTI is rebuilding its connector layer into a marketplace and wiring the platform to XTM Hub

The mainline is working through the consequences of the connector catalog redesign, with each release closing gaps around it: filters and saved searches became shareable, dashboards can reuse them, and background tasks can now edit relationship start and stop times in bulk. Alongside that, an LTS branch is being maintained in parallel — 7.260309.0-lts.7 backports the security fixes and dependency updates from the recent mainline releases without any of the feature work.

Read the full OpenCTI trajectory →

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

O
OpenCTI
ANALYTICS
6.3

OpenCTI is rebuilding its connector layer into a marketplace and wiring the platform to XTM Hub

◆ Current state

The mainline is working through the consequences of the connector catalog redesign, with each release closing gaps around it: filters and saved searches became shareable, dashboards can reuse them, and background tasks can now edit relationship start and stop times in bulk. Alongside that, an LTS branch is being maintained in parallel — 7.260309.0-lts.7 backports the security fixes and dependency updates from the recent mainline releases without any of the feature work.

◆ Where it's heading

Two things are running at once. The product arc is about making the platform's own surfaces composable — a faceted connector marketplace, reusable filters, workflow approval and draft metadata — rather than adding threat-intel primitives. The engineering arc is a maintained LTS channel that gets security parity and nothing else, which is how a project behaves once it has deployments it cannot ask to track weekly releases.

◆ Prediction

Expect the mainline to keep landing XTM Hub integration and workflow-governance work at roughly a weekly cadence, with a matching lts.8 backport following whenever the next batch of security fixes accumulates.

Alternatives to mapSpain and OpenCTI

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

See all mapSpain alternatives → · See all OpenCTI alternatives →

Recent activity from mapSpain and OpenCTI

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

  1. 1d agoOpenCTILTS branch gets the security backport: access-scoped streams, dependency sweep
  2. 4d agoOpenCTIMass operations can now edit relation start and stop times
  3. 8d agoOpenCTISaved searches and dashboard filters become shareable and reusable
  4. 12d agoOpenCTIData sanity operations can be stopped mid-run
  5. 16d agoOpenCTIIntegrations experience reworked around the new catalog, plus draft approval workflows
  6. 24d agoOpenCTIConnector catalog is rebuilt as a faceted marketplace
  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 OpenCTI?

They serve adjacent needs but don't currently overlap on shipped themes. OpenCTI is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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 OpenCTI?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. OpenCTI is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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 OpenCTI?

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