← Back to home
Comparison · Analytics

dfms vs FedData

A side-by-side editorial comparison of dfms and FedData — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:ropensci

dfms vs FedData: at a glance

FeaturedfmsFedData
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesnowcasting, state-space-models, econometrics, ropensciropensci, geospatial, r-package, open-data
Last editorial update1h ago2h ago
WebsiteVisit →Visit →

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.

Read the full dfms trajectory →

What is FedData?

FedData has spent two major versions migrating US federal geodata off R's retiring spatial stack.

FedData downloads and standardises US federal geospatial datasets — NLCD, NHD, NED, SSURGO, Daymet, GHCN, PAD-US, NASS — into consistent R objects. Two breaking majors define the current package: 3.0.0 moved returns to sf and raster and pulled data from cloud-optimised GeoTIFFs, and 4.0.0 finished the job by dropping sp and raster entirely for terra and sf. Recent releases are dataset refreshes, most recently PAD-US 4.0.

Read the full FedData trajectory →

dfms vs FedData: editorial side-by-side

D
dfms
ANALYTICS
0.0

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.

F
FedData
ANALYTICS
0.0

FedData has spent two major versions migrating US federal geodata off R's retiring spatial stack.

◆ Current state

FedData downloads and standardises US federal geospatial datasets — NLCD, NHD, NED, SSURGO, Daymet, GHCN, PAD-US, NASS — into consistent R objects. Two breaking majors define the current package: 3.0.0 moved returns to sf and raster and pulled data from cloud-optimised GeoTIFFs, and 4.0.0 finished the job by dropping sp and raster entirely for terra and sf. Recent releases are dataset refreshes, most recently PAD-US 4.0.

◆ Where it's heading

The package tracks two moving targets at once: the R spatial stack, which it has now fully migrated onto terra and sf, and the federal agencies whose URLs, file naming and hosting keep shifting. With the dependency migration finished, releases have shrunk to single-dataset updates such as annual NLCD and PAD-US 4.0, which suggests the structural work is done and the ongoing cost is data-source maintenance.

◆ Prediction

Expect continued small releases pinned to new vintages of the underlying federal datasets, plus fixes when an agency moves or reformats a source; no further dependency-level upheaval is visible in these entries.

Alternatives to dfms and FedData

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 FedData.

See all dfms alternatives → · See all FedData alternatives →

Recent activity from dfms and FedData

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1mo agodfmsconvert() exports models to dlm and KFAS state-space objects
  2. 6mo agodfms1.0: rOpenSci review passed, news decomposition added
  3. 6mo agodfmsMixed-frequency estimation gains AR(1) idiosyncratic errors
  4. 9mo agodfmsC++ compatibility with RcppArmadillo 15.0.2
  5. 1y agodfmsFixes estimation with a single quarterly variable
  6. 1y agodfmsAdds mixed-frequency estimation via quarterly.vars
  7. 1y agoFedDataget_padus() updated to PAD-US 4.0
  8. 1y agoFedDataAnnual NLCD access added; get_nass() retired
  9. 2y agoFedDatasp and raster dropped; everything returns terra or sf
  10. 3y agoFedDataGHCN moves to https; NHD handles empty and odd geometries
  11. 3y agoFedDataAll raster writing moves to terra
  12. 3y agoFedDataVersion 3 rebuilds on sf and cloud-optimised GeoTIFFs

Frequently asked questions

What is the difference between dfms and FedData?

Both compete on the same themes — ropensci — within Analytics. dfms and FedData 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 FedData?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dfms and FedData 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 FedData?

Top FedData alternatives in Analytics are ranked by recent ship velocity. Browse the "FedData alternatives" section above for the current picks, or visit /alternatives/feddata for the full list with editorial commentary on each.