← Back to home
Comparison · Analytics

bbk vs r-owidapi

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

Shared themes:r-packageapi-wrapper

bbk vs r-owidapi: at a glance

Featurebbkr-owidapi
SectorAnalyticsAnalytics
Velocity score0.02.5
Sparks · 30d00
Top themescentral-bank-data, macro-statistics, r-package, api-wrapperopen-data, our-world-in-data, r-package, api-wrapper
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

What is bbk?

One R interface is absorbing the world's central bank data portals, one API at a time.

bbk began as a Bundesbank client and has become a single R interface to central bank statistics generally: the ECB, BIS, and the national banks of Switzerland, Canada, the UK, France, Spain, Austria, Sweden, Norway, Portugal, Japan, Poland, the Czech Republic, and now Brazil and Mexico. Each provider gets a consistent set of verbs — a data function, a dimension function for the dataflow structure, and provider-specific extras like PRIBOR or CZEONIA fixings. Response caching, data.table returns, and an updated_after argument for incremental retrieval are shared plumbing rather than per-provider features.

Read the full bbk trajectory →

What is r-owidapi?

The R client for Our World in Data found its search had been reading a tenth of the catalog.

owidapi is a small R client for Our World in Data, covering chart data retrieval, metadata, the full chart catalog, and search over it, with experimental Shiny output helpers. It is three releases old and the most recent one is almost entirely repair: the catalog function was silently truncating at 1000 rows because of a Datasette row cap, which meant search had been operating on a fraction of what exists.

Read the full r-owidapi trajectory →

bbk vs r-owidapi: editorial side-by-side

B
bbk
ANALYTICS
0.0

One R interface is absorbing the world's central bank data portals, one API at a time.

◆ Current state

bbk began as a Bundesbank client and has become a single R interface to central bank statistics generally: the ECB, BIS, and the national banks of Switzerland, Canada, the UK, France, Spain, Austria, Sweden, Norway, Portugal, Japan, Poland, the Czech Republic, and now Brazil and Mexico. Each provider gets a consistent set of verbs — a data function, a dimension function for the dataflow structure, and provider-specific extras like PRIBOR or CZEONIA fixings. Response caching, data.table returns, and an updated_after argument for incremental retrieval are shared plumbing rather than per-provider features.

◆ Where it's heading

The expansion is steady and the integration work is what makes it more than a list of wrappers: arguments introduced for one provider get pushed to the others, dimension introspection is being generalised across dataflows, and the bug fixes in recent releases are almost all about the same class of problem — series with missing observations, unsupported frequency codes, or date/value misalignment breaking a parser written for a tidier feed. The maintainer ships the same infrastructure across their packages in lockstep; bbk 0.9.0 and the sibling treasury package's 0.5.0 landed identical opt-in caching within minutes of each other. Geography is the visible frontier, but consistency across an increasingly ragged set of upstream APIs is the actual work.

◆ Prediction

Expect more national central banks to be added on the same template, and the newer providers to be retrofitted with the dimension and updated_after functions the older ones already have.

R
r-owidapi
ANALYTICS
2.5

The R client for Our World in Data found its search had been reading a tenth of the catalog.

◆ Current state

owidapi is a small R client for Our World in Data, covering chart data retrieval, metadata, the full chart catalog, and search over it, with experimental Shiny output helpers. It is three releases old and the most recent one is almost entirely repair: the catalog function was silently truncating at 1000 rows because of a Datasette row cap, which meant search had been operating on a fraction of what exists.

◆ Where it's heading

Development is about making a thin wrapper trustworthy against an upstream that moves without notice. The truncation fix pages through the catalog properly; a separate fix stops the function breaking when Our World in Data dropped a column, by parsing typed columns only when present. Tests moved to mocked responses, with a small live suite retained purely to detect schema drift and skipped on CRAN — a sensible design for a package whose main risk is that the API changes shape rather than that the code is wrong. The user-facing surface has not grown since the initial release; the work is in defending it.

◆ Prediction

On this pattern the next release is likelier to be another upstream-compatibility fix than new functionality, with the schema-drift tests the mechanism that surfaces it.

Alternatives to bbk and r-owidapi

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 bbk or r-owidapi.

See all bbk alternatives → · See all r-owidapi alternatives →

Recent activity from bbk and r-owidapi

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

  1. 20d agor-owidapiCatalog was silently capped at 1000 charts; now paged in full
  2. 1mo agobbkBrazil and Mexico join, bringing survey expectations data
  3. 2mo agobbkCzech National Bank support lands with a broad parser repair
  4. 3mo agobbkIncremental retrieval generalised beyond the ECB endpoint
  5. 4mo agobbkOpt-in response caching plus dimension introspection everywhere
  6. 10mo agobbkBank of Canada data and exchange rates added
  7. 11mo agobbkFour European central banks added; validation moves to checkmate
  8. 1y agor-owidapiRequest logic consolidated, with graceful catalog errors
  9. 1y agor-owidapiFirst release: data, metadata, catalog and search

Frequently asked questions

What is the difference between bbk and r-owidapi?

Both compete on the same themes — r-package, api-wrapper — within Analytics. r-owidapi is currently shipping more aggressively (velocity 2.5 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 bbk better than r-owidapi?

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

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

What are the best alternatives to r-owidapi?

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