r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
A side-by-side editorial comparison of dendroNetwork and osmapiR — release velocity, themes, recent moves, and the top alternatives to consider.
Six releases, six identical bodies — the feed carries the package abstract instead of release notes
dendroNetwork builds networks of dendrochronological series from similarity between tree-ring measurements, applies community detection to find matching material, and hands the result to Cytoscape for visualisation. That description is all the feed provides: every one of the six visible releases carries the same package abstract as its body, with no record of what changed in any of them. Version 0.5.5 in July 2025 is the most recent.
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`.
dendroNetwork builds networks of dendrochronological series from similarity between tree-ring measurements, applies community detection to find matching material, and hands the result to Cytoscape for visualisation. That description is all the feed provides: every one of the six visible releases carries the same package abstract as its body, with no record of what changed in any of them. Version 0.5.5 in July 2025 is the most recent.
What the timestamps show is more informative than the text. Versions 0.5.0 through 0.5.3 were all published within two minutes of each other on 12 April 2024, and in descending version order, which is the signature of a release history backfilled in one pass rather than four separate releases. Real releases follow at 0.5.4 a fortnight later and 0.5.5 fifteen months after that. Development is slow and, on this evidence, undocumented.
No prediction is supportable from these entries — none of them describe a change. Any read on where this package is heading would need the NEWS file or the commit history rather than the feed.
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 dendroNetwork or osmapiR.
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
crul took mocking back from webmockr and made it a property of the client itself
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
Six years since the last functional change, and Google renamed the service it wraps in the release before that
See all dendroNetwork 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. dendroNetwork 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. dendroNetwork 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 dendroNetwork alternatives in Analytics are ranked by recent ship velocity. Browse the "dendroNetwork alternatives" section above for the current picks, or visit /alternatives/dendronetwork 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.