← Back to home
Comparison · Analytics

Fulcrum vs mapSpain

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

Fulcrum vs mapSpain: at a glance

FeatureFulcrummapSpain
SectorAnalyticsAnalytics
Velocity score6.30.0
Sparks · 30d00
Top themesgis, esri-migration, offline-maps, field-data-capturespain, administrative-boundaries, geospatial, httr2
Last editorial update9h ago51m ago
WebsiteVisit →

What is Fulcrum?

Fulcrum is betting its whole map stack on Esri, with a hard Google Maps cutoff on September 1.

Fulcrum is a field data collection platform, and nearly every entry in the last month touches mapping. The web app ships weekly fix batches for layer rendering (KML/KMZ, MBTiles, ArcGIS Feature Services), while iOS and Android push near-weekly builds against the ArcGIS SDK. Feature work is thin right now; the visible surface is stabilization around a mapping engine migration already in flight.

Read the full Fulcrum trajectory →

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 →

Fulcrum vs mapSpain: editorial side-by-side

F
Fulcrum
ANALYTICS
6.3

Fulcrum is betting its whole map stack on Esri, with a hard Google Maps cutoff on September 1.

◆ Current state

Fulcrum is a field data collection platform, and nearly every entry in the last month touches mapping. The web app ships weekly fix batches for layer rendering (KML/KMZ, MBTiles, ArcGIS Feature Services), while iOS and Android push near-weekly builds against the ArcGIS SDK. Feature work is thin right now; the visible surface is stabilization around a mapping engine migration already in flight.

◆ Where it's heading

The direction is a full consolidation onto Esri. The legacy Google Maps engine is being retired on September 1 with automatic migration for anyone who hasn't switched, and Esri now carries Google's satellite and street basemaps so the imagery argument is neutralized. Underneath, the mobile SDK moved to ArcGIS 300.0.0 and ONNX on-device inference was dropped for a new INFERENCE format with labels.txt support. Offline is the second thread: downloadable layers can now be updated in place rather than deleted and recreated.

◆ Prediction

Expect the weeks before September 1 to stay dominated by migration-shaped fixes and Esri feature parity work, with the MMPK layer and Photo FastFill early-access programs the most likely to graduate to general availability next.

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.

Alternatives to Fulcrum and mapSpain

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

See all Fulcrum alternatives → · See all mapSpain alternatives →

Recent activity from Fulcrum and mapSpain

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

  1. 18h agoFulcrumWeb fixes: shared-view exports, MBTiles popups, KML and ArcGIS layers
  2. 3d agoFulcrumAndroid: update offline map layers in place, non-blocking Photo FastFill
  3. 4d agoFulcrumiOS fix: slow location resolution blocked record saves
  4. 8d agoFulcrumWeb: SSO email wording and ArcGIS/deck.gl version bumps
  5. 10d agoFulcrumAndroid fixes: ArcGIS stability, signature button, photo markup
  6. 10d agoFulcrumiOS fixes: basemap loading and black map screen
  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 Fulcrum and mapSpain?

They serve adjacent needs but don't currently overlap on shipped themes. Fulcrum is currently shipping more aggressively (velocity 6.3 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 Fulcrum better than mapSpain?

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

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

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.