distributions3
distributions3 0.3.0 adds sample-based distributions and likelihood derivatives
Comparison · Analytics
climaemet vs Omni
A side-by-side editorial comparison of climaemet and Omni — release velocity, themes, recent moves, and the top alternatives to consider.
climaemet vs Omni: at a glance
What is climaemet?
climaemet added weather alerts and wildfire risk, then spent two years managing rate limits.
climaemet wraps Spain's AEMET meteorological API — station data, historical climate series, forecasts, and the plotting helpers that go with them. Its capability surface widened decisively in 1.4.0 with meteorological alerts and wildfire risk rasters. Everything since has been about surviving the API rather than extending it: multiple API keys, quota-aware key selection, and httr2 throttling pinned to AEMET's stated 40-connections-per-minute policy.
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.
climaemet vs Omni: editorial side-by-side
climaemet
0.0ANALYTICS
climaemet added weather alerts and wildfire risk, then spent two years managing rate limits.
◆ Current state
climaemet wraps Spain's AEMET meteorological API — station data, historical climate series, forecasts, and the plotting helpers that go with them. Its capability surface widened decisively in 1.4.0 with meteorological alerts and wildfire risk rasters. Everything since has been about surviving the API rather than extending it: multiple API keys, quota-aware key selection, and httr2 throttling pinned to AEMET's stated 40-connections-per-minute policy.
◆ Where it's heading
Two forces shape this package, and neither is feature demand. The first is AEMET's own churn — new response codes, a fires endpoint that switched to six risk levels returned as named factors, municipality datasets refreshed annually. The second is the maintainer's cross-package modernization, visible here as the API key store moving to tools::R_user_dir() with automatic migration, a configurable timeout, cli messaging, and an R 4.1 floor. The 1.6.0 refactor is stated as AI-assisted, matching the maintainer's other packages.
◆ Prediction
Expect the next release to track another AEMET endpoint change rather than add a data domain; the throttling and multi-key machinery suggests quota pressure is the constraint the maintainer keeps returning to.
Omni
6.3ANALYTICS
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 climaemet 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 climaemet or Omni.
Basedash
Basedash keeps pushing its data out of the workspace — now to people without accounts
RStudio
RStudio ships through release branches, and the notes are commit messages
dbt Core
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
Fulcrum
Fulcrum is betting its whole map stack on Esri, with a hard Google Maps cutoff on September 1.
Holistics
Holistics keeps fencing in the AI layer it spent the summer building.
See all climaemet alternatives → · See all Omni alternatives →
Recent activity from climaemet and Omni
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoOmniOmni adds default filters on composite topics and query stopping
- 9d agoOmniOmni adds presentation mode and a searchDashboards MCP tool
- 16d agoOmniOmni adds AI credit controls per user and embed entity group
- 23d agoOmniAI semantic model generation goes generally available in Omni ⚡
- 1mo agoOmniOmni adds AI suggestion endpoints and OAuth for database connections
- 1mo agoOmniOmni brings AI routines to Slack and adds in-app MCP settings
- 2mo agoclimaemetAPI keys move to R_user_dir; fire risk returns named factors
- 4mo agoclimaemetVignettes migrated to Quarto
- 7mo agoclimaemetRequest throttling pinned to AEMET's 40-per-minute policy
- 1y agoclimaemetggwindrose rebuilt on coord_radial
- 1y agoclimaemetHighest-quota API key now chosen per call
- 1y agoclimaemetWeather alerts and wildfire risk rasters added ⚡
Frequently asked questions
What is the difference between climaemet 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 climaemet 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 climaemet?
Top climaemet alternatives in Analytics are ranked by recent ship velocity. Browse the "climaemet alternatives" section above for the current picks, or visit /alternatives/climaemet 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.