← Back to home
Comparison · Analytics

quanteda vs r-owidapi

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

Shared themes:r-package

quanteda vs r-owidapi: at a glance

Featurequantedar-owidapi
SectorAnalyticsAnalytics
Velocity score2.52.5
Sparks · 30d00
Top themestext-analysis, natural-language-processing, r-package, torchopen-data, our-world-in-data, r-package, api-wrapper
Last editorial update1h ago45m ago
WebsiteVisit →Visit →

What is quanteda?

Text analysis in R keeps optimising its token internals — and builds a path out to torch

quanteda is a mature framework for quantitative text analysis in R. Since the 4.0 rewrite around external-pointer tokens objects, releases have concentrated on the internals: recompilation control, memory reduction on concatenation, type-table consistency between tokens and dfm objects. The newest release adds tokens_recompile() for explicit ID reassignment, stops query functions from recompiling implicitly, and returns dense rather than sparse tensors from as.tensor() with arguments passed through to torch.

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

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

Q
quanteda
ANALYTICS
2.5

Text analysis in R keeps optimising its token internals — and builds a path out to torch

◆ Current state

quanteda is a mature framework for quantitative text analysis in R. Since the 4.0 rewrite around external-pointer tokens objects, releases have concentrated on the internals: recompilation control, memory reduction on concatenation, type-table consistency between tokens and dfm objects. The newest release adds tokens_recompile() for explicit ID reassignment, stops query functions from recompiling implicitly, and returns dense rather than sparse tensors from as.tensor() with arguments passed through to torch.

◆ Where it's heading

Two threads run in parallel. The dominant one is performance and correctness housekeeping on the tokens_xptr representation introduced in 4.0 — each release closes another case where the external-pointer path diverged from the plain tokens path. The quieter thread points outward: as.matrix() returning a document-by-position integer matrix and as.tensor() handing off to torch::torch_tensor() make the tokenised corpus directly consumable by neural models rather than only by quanteda's own bag-of-words machinery.

◆ Prediction

The tensor and matrix export path is the least mature part of the surface and gained arguments in this release rather than settling, so expect further work there before the token internals change again.

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

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

Recent activity from quanteda and r-owidapi

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

  1. 12d agoquantedaExplicit token recompilation and a denser path out to torch
  2. 20d agor-owidapiCatalog was silently capped at 1000 charts; now paged in full
  3. 1y agor-owidapiRequest logic consolidated, with graceful catalog errors
  4. 1y agoquantedaCorpus chunking and cheaper token concatenation
  5. 1y agor-owidapiFirst release: data, metadata, catalog and search
  6. 1y agoquantedaFaster concatenation and a dfm_lookup naming fix
  7. 2y agoquantedaMinor test and documentation fixes
  8. 2y agoquantedaPlatform-specific test and installation fixes
  9. 2y agoquantedaCRAN v4.0

Frequently asked questions

What is the difference between quanteda and r-owidapi?

Both compete on the same themes — r-package — within Analytics. quanteda and r-owidapi are shipping at a similar cadence (velocity 2.5 vs 2.5, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is quanteda better than r-owidapi?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. quanteda and r-owidapi are shipping at a similar cadence (velocity 2.5 vs 2.5, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.

What are the best alternatives to quanteda?

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