tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of forcis and osmapiR — release velocity, themes, recent moves, and the top alternatives to consider.
A foraminifera data-access package whose entire release history is the rOpenSci review process.
forcis provides R access to the FORCIS database of planktonic foraminifera occurrences. All three releases in the window are review milestones rather than feature work: first stable release, the release answering rOpenSci reviewer comments, and a post-CRAN-review polish. Release notes point at NEWS.md rather than enumerating changes.
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`.
forcis provides R access to the FORCIS database of planktonic foraminifera occurrences. All three releases in the window are review milestones rather than feature work: first stable release, the release answering rOpenSci reviewer comments, and a post-CRAN-review polish. Release notes point at NEWS.md rather than enumerating changes.
The package is moving from research artifact to reviewed, distributable infrastructure — submitted to rOpenSci at 0.1.0, integrated review feedback at 1.0.0, cleared CRAN at 1.0.1. That arc is complete, so the next phase should be the first release driven by users rather than reviewers.
With review and CRAN acceptance both behind it, the next release is most likely to track upstream FORCIS database changes or add query conveniences; the entries themselves say nothing about planned features.
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.
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 forcis or osmapiR.
A tables-listings-graphs package that reached CRAN and then went quiet.
Tplyr made clinical summary tables explain where every number came from.
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.
See all forcis alternatives → · See all osmapiR alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. forcis and osmapiR 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. forcis and osmapiR 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 forcis alternatives in Analytics are ranked by recent ship velocity. Browse the "forcis alternatives" section above for the current picks, or visit /alternatives/forcis for the full list with editorial commentary on each.
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.