← Back to home
Comparison · Analytics

cfr vs FedData

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

cfr vs FedData: at a glance

FeaturecfrFedData
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesepidemiology, severity-estimation, outbreak-analytics, epiverseropensci, geospatial, r-package, open-data
Last editorial update1h ago50m ago
WebsiteVisit →Visit →

What is cfr?

cfr packaged delay-corrected severity estimation, then went quiet on maintenance.

The package estimates disease severity and case ascertainment while correcting for the delay between a case being reported and its outcome being known. After the 0.1.1 rework of the estimation internals and a maintainer handover to Adam Kucharski, activity dropped to a vignette and an R-devel compatibility patch in February 2025.

Read the full cfr 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 →

cfr vs FedData: editorial side-by-side

C
cfr
ANALYTICS
0.0

cfr packaged delay-corrected severity estimation, then went quiet on maintenance.

◆ Current state

The package estimates disease severity and case ascertainment while correcting for the delay between a case being reported and its outcome being known. After the 0.1.1 rework of the estimation internals and a maintainer handover to Adam Kucharski, activity dropped to a vignette and an R-devel compatibility patch in February 2025.

◆ Where it's heading

The methodological work is done and consolidated: likelihood approximation is now selected automatically from outbreak size and an initial severity estimate, and the internals were renamed with a dot prefix to close the public surface down to cfr_static(), cfr_rolling() and the data-preparation generic. Releases since have been documentation and compatibility only.

◆ Prediction

The 0.1.0 notes flagged time-varying ascertainment as future work and it has not appeared in the two releases since; nothing in these entries indicates when or whether it lands.

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

See all cfr alternatives → · See all FedData alternatives →

Recent activity from cfr and FedData

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

  1. 1y agoFedDataget_padus() updated to PAD-US 4.0
  2. 1y agocfrR-devel difftime patch and an individual-data vignette
  3. 1y agoFedDataAnnual NLCD access added; get_nass() retired
  4. 2y agocfrSeverity estimator picks its own likelihood approximation
  5. 2y agocfrDelay-corrected severity and ascertainment estimation on CRAN
  6. 2y agoFedDatasp and raster dropped; everything returns terra or sf
  7. 3y agoFedDataGHCN moves to https; NHD handles empty and odd geometries
  8. 3y agoFedDataAll raster writing moves to terra
  9. 3y agoFedDataVersion 3 rebuilds on sf and cloud-optimised GeoTIFFs

Frequently asked questions

What is the difference between cfr and FedData?

They serve adjacent needs but don't currently overlap on shipped themes. cfr 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 cfr better than FedData?

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

Top cfr alternatives in Analytics are ranked by recent ship velocity. Browse the "cfr alternatives" section above for the current picks, or visit /alternatives/cfr 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.