← Back to home
Comparison · Analytics

cholera vs Omni

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

cholera vs Omni: at a glance

FeaturecholeraOmni
SectorAnalyticsAnalytics
Velocity score0.06.3
Sparks · 30d01
Top themeshistorical-epidemiology, geospatial, r-package, reproducible-researchbusiness-intelligence, semantic-model, ai-routines, mcp
Last editorial update3d ago1h ago
WebsiteVisit →Visit →

What is cholera?

John Snow's 1854 cholera map is being rebuilt on real geographic coordinates.

cholera packages the Broad Street cholera outbreak data with tools to recompute pump neighbourhoods by Voronoi and walking distance. The last two releases carried the dataset from Snow's original plate coordinates onto georeferenced longitude and latitude, exposed through a latlong = TRUE argument on most functions. Function naming and plotting APIs are being tidied at the same pace.

Read the full cholera 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 →

cholera vs Omni: editorial side-by-side

C
cholera
ANALYTICS
0.0

John Snow's 1854 cholera map is being rebuilt on real geographic coordinates.

◆ Current state

cholera packages the Broad Street cholera outbreak data with tools to recompute pump neighbourhoods by Voronoi and walking distance. The last two releases carried the dataset from Snow's original plate coordinates onto georeferenced longitude and latitude, exposed through a latlong = TRUE argument on most functions. Function naming and plotting APIs are being tidied at the same pace.

◆ Where it's heading

The direction is clear and sustained: convert a historical, self-referential coordinate system into one that interoperates with modern GIS. Each release extends latlong coverage to more datasets — pumps, roads, landmarks, and now the plague pit and map frame — while archiving the older prototypes. Parallelisation and the walking-distance solver were reworked along the way to keep the heavier computations usable.

◆ Prediction

Remaining non-georeferenced pieces and the archived latlong prototypes are the obvious next targets, alongside continued consolidation of the add*()/plot*() function pairs.

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

See all cholera alternatives → · See all Omni alternatives →

Recent activity from cholera and Omni

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

  1. 15h 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. 1y agocholeraGeoreferences the plague pit and road segments
  8. 1y agocholeraLongitude and latitude support across nearly all data and functions
  9. 3y agocholeraFirst longitude/latitude prototypes and new distance functions
  10. 4y agocholeraAdds streetNames(); fixes Delaunay and pump-token plotting
  11. 5y agocholeraIsochrone helpers, weather data and Voronoi location options
  12. 6y agocholeraParallel computation support on Windows

Frequently asked questions

What is the difference between cholera 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 cholera 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 cholera?

Top cholera alternatives in Analytics are ranked by recent ship velocity. Browse the "cholera alternatives" section above for the current picks, or visit /alternatives/cholera-r 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.