nflreadr
The nflverse data loader, whose releases are dictated by the NFL calendar and CRAN's archive policy
Comparison · Analytics
r-owidapi vs treasury
A side-by-side editorial comparison of r-owidapi and treasury — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-packageapi-wrapper
r-owidapi vs treasury: at a glance
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.
What is treasury?
A thin Treasury rates wrapper has stopped adding endpoints and started making its tables self-describing.
treasury wraps the US Treasury's published rate feeds — bill rates, par yields, forward rates, long-term extrapolated rates, and the HQM and breakeven inflation curves — into one set of R functions. Since 0.3.0 every function returns a data.table, and 0.5.0 added optional on-disk response caching with a one-day default. The most recent release is about data fidelity rather than reach: identifying columns, correct maturity labels, and locale-safe date parsing.
r-owidapi vs treasury: editorial side-by-side
r-owidapi
2.5ANALYTICS
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.
treasury
0.0ANALYTICS
A thin Treasury rates wrapper has stopped adding endpoints and started making its tables self-describing.
◆ Current state
treasury wraps the US Treasury's published rate feeds — bill rates, par yields, forward rates, long-term extrapolated rates, and the HQM and breakeven inflation curves — into one set of R functions. Since 0.3.0 every function returns a data.table, and 0.5.0 added optional on-disk response caching with a one-day default. The most recent release is about data fidelity rather than reach: identifying columns, correct maturity labels, and locale-safe date parsing.
◆ Where it's heading
Endpoint coverage looks essentially complete, so the work has moved to the metadata a downstream analyst needs to join and audit results — cusip and maturity_date on bill quotes, the feed's updated_at stamp, and the extrapolation factor behind 2002-2006 long-term rate estimates. Error handling is tightening in the same direction: an out-of-range month now fails with a message instead of quietly returning nothing. That is the profile of a wrapper moving from coverage to correctness, where the remaining bugs are the subtle ones that only surface in other people's locales.
◆ Prediction
Expect further column-level enrichment and input validation on the endpoints already covered rather than new data sources, since the structural pieces — data.table returns and caching — are already in place.
Alternatives to r-owidapi and treasury
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 r-owidapi or treasury.
susier
Fine-mapping workhorse susieR spends its releases hunting null-effect trimming bugs
UCell
A rank-based gene signature scorer that has grown by adapting to whatever object format single-cell R uses next
detectseparation
A diagnostic package that generalized past its own name, then learned to say which kind of separation it found
brglm2
A bias-reduction package reaches 1.0 by adding an estimator built for high-dimensional logistic regression
bayestools
The JAGS toolkit under RoBMA, shipping the standardization machinery its downstream rewrite needed
See all r-owidapi alternatives → · See all treasury alternatives →
Recent activity from r-owidapi and treasury
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 20d agor-owidapiCatalog was silently capped at 1000 charts; now paged in full
- 1mo agotreasuryBill rates gain CUSIP and maturity date; locale bug fixed
- 4mo agotreasuryOptional response caching, one day by default
- 11mo agotreasuryRate functions renamed to singular for consistency
- 1y agotreasuryEvery function now returns a data.table ⚡
- 1y agor-owidapiRequest logic consolidated, with graceful catalog errors
- 1y agor-owidapiFirst release: data, metadata, catalog and search
- 2y agotreasuryHQM, coupon-issue and breakeven inflation curves added
Frequently asked questions
What is the difference between r-owidapi and treasury?
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 r-owidapi better than treasury?
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 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.
What are the best alternatives to treasury?
Top treasury alternatives in Analytics are ranked by recent ship velocity. Browse the "treasury alternatives" section above for the current picks, or visit /alternatives/treasury for the full list with editorial commentary on each.