tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of osmapiR and Tplyr — release velocity, themes, recent moves, and the top alternatives to consider.
osmapiR is the rare API client that tracks its server's wiki revision numbers in the changelog.
osmapiR wraps the full OpenStreetMap API from R — reading and writing map data, changesets, notes, GPX traces and user records — with OAuth2 where the endpoint requires it, pagination handled internally, and atomic calls vectorised. Recent releases have filled in the moderation and social surface: note subscription, user blocks, changeset discussion search. The newest release lets `bbox` arguments arrive as a character string, matrix, vector, an sf `bbox`, or a terra `SpatExtent`.
Tplyr made clinical summary tables explain where every number came from.
Tplyr builds clinical summary tables through a layered grammar — count, descriptive statistics, and shift layers assembled onto a table object. The 1.0.0 release added a traceability metadata framework that lets a user ask which source rows produced any given cell, and later releases extended it to cases the first pass missed. The package is maintained by Atorus within the pharmaverse ecosystem.
osmapiR wraps the full OpenStreetMap API from R — reading and writing map data, changesets, notes, GPX traces and user records — with OAuth2 where the endpoint requires it, pagination handled internally, and atomic calls vectorised. Recent releases have filled in the moderation and social surface: note subscription, user blocks, changeset discussion search. The newest release lets `bbox` arguments arrive as a character string, matrix, vector, an sf `bbox`, or a terra `SpatExtent`.
Four consecutive releases open with the same line — documentation and code updated for server-side changes, cited by OSM wiki revision range. That is a maintainer treating an evolving remote API as a versioned contract and auditing against it each cycle, which is unusual discipline and the main reason to trust this client over a hand-rolled wrapper. The second thread is fitting into R's spatial conventions rather than exposing OSM's, visible in the bbox coercion work and the httr2 upgrades landing with upstream help.
The pattern is stable enough to call: another release synchronised to the next OSM wiki revision range, adding whatever endpoints appeared and adjusting whatever changed shape.
Tplyr builds clinical summary tables through a layered grammar — count, descriptive statistics, and shift layers assembled onto a table object. The 1.0.0 release added a traceability metadata framework that lets a user ask which source rows produced any given cell, and later releases extended it to cases the first pass missed. The package is maintained by Atorus within the pharmaverse ecosystem.
Post-1.0 work has been about completing the metadata story and filling gaps in layer composition rather than adding table types — metadata for missing subjects, add_anti_join(), missing-subject rows, data limiting, and fixes to nested count layers where an inner value appears under several outer groups. Releases cluster tightly after a major version, then go quiet, and the window ends with a patch issued days after the release it corrects.
Further releases will most likely continue closing traceability and nested-layer edge cases rather than introducing new layer types, following the pattern of both post-1.0 feature releases.
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 osmapiR or Tplyr.
A tables-listings-graphs package that reached CRAN and then went quiet.
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
datasetjson rebuilt its object model to track the CDISC Dataset-JSON 1.1 schema.
See all osmapiR alternatives → · See all Tplyr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. osmapiR and Tplyr are shipping at a similar cadence (velocity 0.0 vs 0.0, 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. osmapiR and Tplyr are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top osmapiR alternatives in Analytics are ranked by recent ship velocity. Browse the "osmapiR alternatives" section above for the current picks, or visit /alternatives/osmapir for the full list with editorial commentary on each.
Top Tplyr alternatives in Analytics are ranked by recent ship velocity. Browse the "Tplyr alternatives" section above for the current picks, or visit /alternatives/tplyr for the full list with editorial commentary on each.