lavaanExtra
SEM reporting helpers converging on APA output, one CRAN resubmission at a time.
A side-by-side editorial comparison of r-owidapi and simlandr — 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.
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
simlandr builds potential landscape plots from simulations of dynamic systems, with barrier-height calculations and batch simulation grids. Its three substantive releases are all consolidation: parameters renamed, functions renamed, defaults removed. By 0.3.0 the bespoke accessors had been replaced by ggplot2's autolayer() and base summary(), and the package carried print, summary, and plot methods for its own classes.
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.
simlandr builds potential landscape plots from simulations of dynamic systems, with barrier-height calculations and batch simulation grids. Its three substantive releases are all consolidation: parameters renamed, functions renamed, defaults removed. By 0.3.0 the bespoke accessors had been replaced by ggplot2's autolayer() and base summary(), and the package carried print, summary, and plot methods for its own classes.
Every release trades a package-specific name for a conventional one - var and par became arg and ele, get_geom() became an autolayer() method, get_barrier_height() became a summary() method, hash_big.matrix became hash_big_matrix. The one methodological change, an adjusted minimal energy path algorithm, arrived inside a release otherwise full of renames. Removing default values for barrier calculation because they were often unsuitable reads as the maintainer deciding the defaults were doing harm.
The feed stops at 0.3.0 in late 2022, mid-consolidation; these entries give no indication of what followed, if anything did.
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 simlandr.
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.
From a bundled hospital dataset to a live CMS API client.
See all r-owidapi alternatives → · See all simlandr 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 simlandr alternatives in Analytics are ranked by recent ship velocity. Browse the "simlandr alternatives" section above for the current picks, or visit /alternatives/simlandr for the full list with editorial commentary on each.