simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
A side-by-side editorial comparison of r-owidapi and rtrek — release velocity, themes, recent moves, and the top alternatives to consider.
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.
A Star Trek data package that became a Memory Alpha web client and has been patching scrapers ever since.
rtrek bundles Star Trek datasets — book series, timelines, episode transcripts, species and homeworlds, map tile sets — and layers live retrieval on top through memory_alpha() and memory_beta() plus their ma_* and mb_* helpers. Recent releases are almost entirely repairs to that retrieval layer as the source wikis change their page structure.
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.
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.
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.
rtrek bundles Star Trek datasets — book series, timelines, episode transcripts, species and homeworlds, map tile sets — and layers live retrieval on top through memory_alpha() and memory_beta() plus their ma_* and mb_* helpers. Recent releases are almost entirely repairs to that retrieval layer as the source wikis change their page structure.
The package's centre of gravity shifted once, at 0.2.0, from shipping static data to querying Memory Alpha and Memory Beta at runtime. Everything since has been the maintenance bill for that decision: HTML update fixes, parser improvements, portal retrieval bugs. Note that version numbers on this feed do not track time — 0.2.5 is stamped a year before 0.1.0, and three tags were backfilled within four minutes in November 2020 — so neither rank nor version ordering here indicates release sequence.
Expect the next release to fix retrieval against another Memory Alpha layout change, which is what the last four have done. The entries give no indication of new datasets or functions in progress.
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 rtrek.
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
SEM reporting helpers converging on APA output, one CRAN resubmission at a time.
A raster-to-terra migration is the only readable change in a feed of merge notes.
A nycflights13 generator whose recent work is all about the data being right.
Conditional density and log-likelihood fill out a vine copula regression package.
A drop-in string API for base R, kept alive by upstream check failures.
See all r-owidapi alternatives → · See all rtrek alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — 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.
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.
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.
Top rtrek alternatives in Analytics are ranked by recent ship velocity. Browse the "rtrek alternatives" section above for the current picks, or visit /alternatives/rtrek for the full list with editorial commentary on each.