r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
A side-by-side editorial comparison of ggsurvfit and osmapiR — release velocity, themes, recent moves, and the top alternatives to consider.
ggsurvfit is in correctness-and-compatibility mode, not feature mode.
The package draws survival and cumulative-incidence curves on a ggplot2 grammar, with risk tables, p-values and quantile annotations. Recent releases are entirely fixes and upstream tracking: ggplot2 v4.0.0 compatibility in 2025, and a 2026 patch correcting a Gray-test p-value that could be reported for the wrong competing event.
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`.
The package draws survival and cumulative-incidence curves on a ggplot2 grammar, with risk tables, p-values and quantile annotations. Recent releases are entirely fixes and upstream tracking: ggplot2 v4.0.0 compatibility in 2025, and a 2026 patch correcting a Gray-test p-value that could be reported for the wrong competing event.
The feature surface settled around 1.0.0, when risk-table alignment was exported and colour and linetype defaults became configurable. Since then the work is keeping pace with survival, ggplot2 and tidycmprsk changes, and closing cases where the plotted curve and the annotation disagreed — the p-value matched by position rather than name, confidence limits swapped for multi-state models, quantiles read off a plateau.
Expect the next release to track upstream survival or ggplot2 changes rather than add plotting features; the CDISC censoring convention adopted in Surv_CNSR() suggests further alignment with clinical data standards is the likelier direction.
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 ggsurvfit 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
Six releases, six identical bodies — the feed carries the package abstract instead of release notes
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
See all ggsurvfit 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. ggsurvfit 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. ggsurvfit 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 ggsurvfit alternatives in Analytics are ranked by recent ship velocity. Browse the "ggsurvfit alternatives" section above for the current picks, or visit /alternatives/ggsurvfit 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.