r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
Comparison · Analytics
dfms vs osmapiR
A side-by-side editorial comparison of dfms and osmapiR — release velocity, themes, recent moves, and the top alternatives to consider.
dfms vs osmapiR: at a glance
What is dfms?
Peer-reviewed, feature-complete, and now able to hand its models to other forecasting engines.
dfms estimates dynamic factor models in R, the workhorse for nowcasting economic activity from ragged, mixed-frequency data. The package worked through the Banbura and Modugno (2014) specification in stages — quarterly variables in 0.3.0, AR(1) idiosyncratic errors combined with mixed frequency in 0.4.0 — then declared 1.0.0 feature-complete on completing rOpenSci peer review, adding news decomposition to attribute forecast revisions to specific data releases. Version 1.0.1 adds convert(), which exports fitted models to dlm or KFAS state-space objects.
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`.
dfms vs osmapiR: editorial side-by-side
dfms
0.0ANALYTICS
Peer-reviewed, feature-complete, and now able to hand its models to other forecasting engines.
◆ Current state
dfms estimates dynamic factor models in R, the workhorse for nowcasting economic activity from ragged, mixed-frequency data. The package worked through the Banbura and Modugno (2014) specification in stages — quarterly variables in 0.3.0, AR(1) idiosyncratic errors combined with mixed frequency in 0.4.0 — then declared 1.0.0 feature-complete on completing rOpenSci peer review, adding news decomposition to attribute forecast revisions to specific data releases. Version 1.0.1 adds convert(), which exports fitted models to dlm or KFAS state-space objects.
◆ Where it's heading
The package has finished the implementation programme it set out in its 2023 vignette and is now working on the edges: interoperability with other state-space packages rather than more estimation methods of its own. The convert() function is the clearest signal — instead of implementing smoothing and prediction intervals natively, it hands the model to packages that already have them. The rOpenSci move also puts it on a review-backed, documented footing that research users can cite.
◆ Prediction
Expect continued interoperability and diagnostic work rather than new estimators, since the maintainer has explicitly scoped the package as complete. Bug fixes against RcppArmadillo releases will likely remain the other recurring driver.
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.
Alternatives to dfms and osmapiR
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 dfms or osmapiR.
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 dfms alternatives → · See all osmapiR alternatives →
Recent activity from dfms and osmapiR
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agodfmsconvert() exports models to dlm and KFAS state-space objects
- 5mo agoosmapiRbbox arguments accept sf and terra objects
- 6mo agodfms1.0: rOpenSci review passed, news decomposition added ⚡
- 6mo agodfmsMixed-frequency estimation gains AR(1) idiosyncratic errors
- 9mo agodfmsC++ compatibility with RcppArmadillo 15.0.2
- 0y agoosmapiRNote search defaults to creation order; JSON for GPX metadata
- 1y agodfmsFixes estimation with a single quarterly variable
- 1y agodfmsAdds mixed-frequency estimation via quarterly.vars
- 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 ⚡
Frequently asked questions
What is the difference between dfms and osmapiR?
They serve adjacent needs but don't currently overlap on shipped themes. dfms 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.
Is dfms better than osmapiR?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dfms 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.
What are the best alternatives to dfms?
Top dfms alternatives in Analytics are ranked by recent ship velocity. Browse the "dfms alternatives" section above for the current picks, or visit /alternatives/dfms for the full list with editorial commentary on each.
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.