← Back to home
Comparison · Analytics

cfr vs giscoR

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

cfr vs giscoR: at a glance

FeaturecfrgiscoR
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesepidemiology, severity-estimation, outbreak-analytics, epiverseeurostat, geospatial, ropensci, r-package
Last editorial update1h ago48m 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 giscoR?

giscoR's 1.0 moved its dataset index into the cache, so new Eurostat releases arrive without a package update.

giscoR downloads Eurostat GISCO administrative and statistical geodata — countries, NUTS regions, LAUs, urban audit units — as sf objects. The 1.0.0 release in December 2025 rebuilt the package on httr2, preferred GeoPackage downloads, reorganised the cache into topic folders, and moved the dataset database itself into the cache so it can be refreshed independently. Releases since have been a cache-persistence fix, a configurable timeout and an internals refactor.

Read the full giscoR trajectory →

cfr vs giscoR: 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.

G
giscoR
ANALYTICS
0.0

giscoR's 1.0 moved its dataset index into the cache, so new Eurostat releases arrive without a package update.

◆ Current state

giscoR downloads Eurostat GISCO administrative and statistical geodata — countries, NUTS regions, LAUs, urban audit units — as sf objects. The 1.0.0 release in December 2025 rebuilt the package on httr2, preferred GeoPackage downloads, reorganised the cache into topic folders, and moved the dataset database itself into the cache so it can be refreshed independently. Releases since have been a cache-persistence fix, a configurable timeout and an internals refactor.

◆ Where it's heading

The package is decoupling itself from Eurostat's publication calendar. Historically each new GISCO vintage required a release that bumped default years and rebuilt an internal dataset; after 1.0.0 a user can call gisco_get_cached_db(update_cache = TRUE) and reach new data without waiting. The follow-up releases are consistent with a project in consolidation — fixing the cache it just introduced, exposing a timeout for slow downloads, and tidying internals.

◆ Prediction

With the database now self-updating, expect releases to shift toward download reliability and new GISCO endpoints rather than annual dataset bumps; the timeout option in 1.1.0 suggests large downloads are the current pain point.

Alternatives to cfr and giscoR

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

See all cfr alternatives → · See all giscoR alternatives →

Recent activity from cfr and giscoR

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

  1. 1mo agogiscoRInternal refactor with faster mocked tests
  2. 4mo agogiscoRDownload timeout becomes configurable
  3. 6mo agogiscoRCache persistence fixed; urban audit defaults to 2024
  4. 7mo agogiscoR1.0 caches the dataset index so new vintages need no release
  5. 1y agocfrR-devel difftime patch and an individual-data vignette
  6. 1y agogiscoRSource filtering fixed in gisco_get_lau()
  7. 1y agogiscoR2024 datasets and year arguments for education and healthcare
  8. 2y agocfrSeverity estimator picks its own likelihood approximation
  9. 2y agocfrDelay-corrected severity and ascertainment estimation on CRAN

Frequently asked questions

What is the difference between cfr and giscoR?

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

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

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