r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
Comparison · Analytics
osmapiR vs poissonreg
A side-by-side editorial comparison of osmapiR and poissonreg — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-language
osmapiR vs poissonreg: at a glance
What is osmapiR?
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`.
What is poissonreg?
poissonreg gave its models away to parsnip and kept the glue — now it just keeps glmnet honest.
poissonreg is a tidymodels extension that wires Poisson and zero-inflated count regression into the parsnip interface. Its defining event was giving up ownership: the model definition functions moved into parsnip itself, leaving this package as engine bindings and prediction plumbing. The current dev release is entirely correctness and hygiene work — glmnet predictions now default to mean counts rather than the linear predictor, and single-observation prediction works at last.
osmapiR vs poissonreg: editorial side-by-side
osmapiR
0.0ANALYTICS
osmapiR is the rare API client that tracks its server's wiki revision numbers in the changelog.
◆ Current state
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`.
◆ Where it's heading
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.
◆ Prediction
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.
poissonreg
0.0ANALYTICS
poissonreg gave its models away to parsnip and kept the glue — now it just keeps glmnet honest.
◆ Current state
poissonreg is a tidymodels extension that wires Poisson and zero-inflated count regression into the parsnip interface. Its defining event was giving up ownership: the model definition functions moved into parsnip itself, leaving this package as engine bindings and prediction plumbing. The current dev release is entirely correctness and hygiene work — glmnet predictions now default to mean counts rather than the linear predictor, and single-observation prediction works at last.
◆ Where it's heading
Release cadence has collapsed from yearly to a four-year gap between 1.0.1 and the current development version, and the content has shifted from features to deduplication against parsnip — copied helper functions replaced by the upstream originals, obsolete generic registrations removed, tests migrated to the shared extension-package pattern. This is what a stabilized tidymodels satellite looks like: the interface lives upstream, and the package's job is to not drift from it.
◆ Prediction
The dev version's accumulated fixes point to a CRAN release of 1.0.2 as the next move, with content limited to the glmnet prediction corrections rather than any new engine or model type.
Alternatives to osmapiR and poissonreg
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 poissonreg.
DoseFinding
New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing
webmockr
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
crul
crul took mocking back from webmockr and made it a property of the client itself
dendroNetwork
Six releases, six identical bodies — the feed carries the package abstract instead of release notes
chattr
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
See all osmapiR alternatives → · See all poissonreg alternatives →
Recent activity from osmapiR and poissonreg
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3mo agopoissonregglmnet predictions now default to mean counts
- 5mo agoosmapiRbbox arguments accept sf and terra objects
- 0y agoosmapiRNote search defaults to creation order; JSON for GPX metadata
- 1y agoosmapiRNote subscriptions and user block endpoints added
- 1y agoosmapiRChangeset queries gain from and to parameters
- 1y agoosmapiRJOSS citation added; single-tag conversion fixed
- 2y agoosmapiRComplete OSM API coverage arrives in one release ⚡
- 3y agopoissonregDocumentation regenerated for valid HTML5
- 4y agopoissonregCase weight support tracks parsnip 1.0.0
- 4y agopoissonregModel definitions move out of poissonreg into parsnip ⚡
- 4y agopoissonregglm becomes the default engine; tidy() for hurdle models
- 5y agopoissonregFirst release, with a glmnet column-order safeguard
Frequently asked questions
What is the difference between osmapiR and poissonreg?
Both compete on the same themes — r-language — within Analytics. osmapiR and poissonreg 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.
Is osmapiR better than poissonreg?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. osmapiR and poissonreg 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.
What are the best alternatives to osmapiR?
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.
What are the best alternatives to poissonreg?
Top poissonreg alternatives in Analytics are ranked by recent ship velocity. Browse the "poissonreg alternatives" section above for the current picks, or visit /alternatives/poissonreg for the full list with editorial commentary on each.