← Back to home
Comparison · Analytics

CatastRo vs Omni

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

CatastRo vs Omni: at a glance

FeatureCatastRoOmni
SectorAnalyticsAnalytics
Velocity score0.06.3
Sparks · 30d01
Top themesspatial-data, open-government-data, spain, httr2business-intelligence, semantic-model, ai-routines, mcp
Last editorial update3d ago3h ago
WebsiteVisit →Visit →

What is CatastRo?

Spain's cadastre client spent 1.0.0 breaking its own cache to become a tidy, httr2-native package.

CatastRo pulls parcels, buildings, addresses and WMS map layers from the Spanish Cadastre into R. The 1.0.0 line rebuilt the codebase on httr2, reorganized the cache into topic-based subfolders and moved persistent storage from rappdirs to tools::R_user_dir(), a change that invalidates every pre-1.0.0 cache. The two releases since are documentation and an AI-assisted internal refactor.

Read the full CatastRo trajectory →

What is Omni?

Omni ships weekly, and almost every week the headline item is an AI feature.

Omni publishes a dated weekly digest whose body is a single line listing that week's items, so each entry compresses several releases into a sentence. Across the window the pattern is unmistakable: AI-powered semantic model generation reaching general availability, AI Routines creatable from chat and deliverable to Slack, AI model suggestion endpoints, AI credit controls scoped to embed entity groups and individual users, AI Evals on Azure, and MCP surfaces appearing both in-app and as a searchDashboards tool. The most recent week breaks that streak — default filters on composite topics, stopping a running dashboard query, full-screen preview editing — the first digest in two months led by conventional BI work.

Read the full Omni trajectory →

CatastRo vs Omni: editorial side-by-side

C
CatastRo
ANALYTICS
0.0

Spain's cadastre client spent 1.0.0 breaking its own cache to become a tidy, httr2-native package.

◆ Current state

CatastRo pulls parcels, buildings, addresses and WMS map layers from the Spanish Cadastre into R. The 1.0.0 line rebuilt the codebase on httr2, reorganized the cache into topic-based subfolders and moved persistent storage from rappdirs to tools::R_user_dir(), a change that invalidates every pre-1.0.0 cache. The two releases since are documentation and an AI-assisted internal refactor.

◆ Where it's heading

The arc is consolidation, not expansion: the retrieval surface has been stable since 0.3.0 added street names to addresses, while the maintainer has spent the releases since standardizing transport, output types and messaging. All functions now return tibbles or sf objects with tibble data, and cli handles user-facing output. The same modernization is being applied across the maintainer's other Spanish-data packages.

◆ Prediction

Expect the next releases to stay in the 1.0.x patch range — documentation, cli wording and CRAN upkeep — unless the Cadastre publishes a new service worth wrapping.

O
Omni
ANALYTICS
6.3

Omni ships weekly, and almost every week the headline item is an AI feature.

◆ Current state

Omni publishes a dated weekly digest whose body is a single line listing that week's items, so each entry compresses several releases into a sentence. Across the window the pattern is unmistakable: AI-powered semantic model generation reaching general availability, AI Routines creatable from chat and deliverable to Slack, AI model suggestion endpoints, AI credit controls scoped to embed entity groups and individual users, AI Evals on Azure, and MCP surfaces appearing both in-app and as a searchDashboards tool. The most recent week breaks that streak — default filters on composite topics, stopping a running dashboard query, full-screen preview editing — the first digest in two months led by conventional BI work.

◆ Where it's heading

Two things have been happening in parallel and they are related. Omni pushed AI into the modelling layer rather than only the query layer, which is what semantic model generation reaching GA signified, then built the commercial and access controls those features require — credit limits per user and per embed entity group arrived within weeks of the capabilities that consume them. The MCP work points at a third direction, exposing Omni's content to external agents rather than only serving its own chat. The latest week's return to filters and query controls suggests the AI surface has reached the point where the surrounding product has to catch up to it.

◆ Prediction

With searchDashboards already shipped as an MCP tool, more of Omni's catalog is the obvious next thing to expose that way, and credit controls should keep extending to cover newer AI surfaces. Whether the non-AI week is a pause or a genuine rebalancing is not something one digest can settle.

Alternatives to CatastRo and Omni

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 CatastRo or Omni.

See all CatastRo alternatives → · See all Omni alternatives →

Recent activity from CatastRo and Omni

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

  1. 17h agoOmniOmni adds default filters on composite topics and query stopping
  2. 8d agoOmniOmni adds presentation mode and a searchDashboards MCP tool
  3. 15d agoOmniOmni adds AI credit controls per user and embed entity group
  4. 22d agoOmniAI semantic model generation goes generally available in Omni
  5. 29d agoOmniOmni adds AI suggestion endpoints and OAuth for database connections
  6. 1mo agoOmniOmni brings AI routines to Slack and adds in-app MCP settings
  7. 2mo agoCatastRoAI-assisted internal refactor and cli message pass
  8. 3mo agoCatastRoDocumentation-only patch release
  9. 5mo agoCatastRo1.0.0 rebuilds on httr2 and invalidates every existing cache
  10. 1y agoCatastRoDocumentation and URL refresh
  11. 2y agoCatastRoCadastre service entry points updated
  12. 2y agoCatastRohttr to httr2 migration, declared invisible to users

Frequently asked questions

What is the difference between CatastRo and Omni?

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

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

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

What are the best alternatives to Omni?

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