metatools
SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.
Comparison · Analytics
giscoR vs superspreading
A side-by-side editorial comparison of giscoR and superspreading — release velocity, themes, recent moves, and the top alternatives to consider.
giscoR vs superspreading: at a glance
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.
What is superspreading?
superspreading now asks whether a pathogen will emerge at all, not just how unevenly it spreads.
superspreading quantifies individual-level variation in transmission — the offspring distributions and summary metrics behind the 20/80 rule — and calculates probabilities of epidemic, extinction and containment. With 0.4.0 it added probability_emergence(), estimating whether an introduced pathogen can evolve into sustained human-to-human transmission. The package moved from experimental to stable in the same release.
giscoR vs superspreading: editorial side-by-side
giscoR
0.0ANALYTICS
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.
superspreading
0.0ANALYTICS
superspreading now asks whether a pathogen will emerge at all, not just how unevenly it spreads.
◆ Current state
superspreading quantifies individual-level variation in transmission — the offspring distributions and summary metrics behind the 20/80 rule — and calculates probabilities of epidemic, extinction and containment. With 0.4.0 it added probability_emergence(), estimating whether an introduced pathogen can evolve into sustained human-to-human transmission. The package moved from experimental to stable in the same release.
◆ Where it's heading
Scope has widened one published framework at a time. 0.2.0 added network-based reproduction numbers, 0.3.0 added the Lloyd-Smith formulation of proportion_transmission() and vendored a branching-process simulator to drop the {bpmodels} dependency, and 0.4.0 implemented and extended the Antia et al. emergence model. Each addition brings a vignette reproducing the source paper's figures, which is how this package treats a method as delivered.
◆ Prediction
The established pattern — implement a published framework, extend it, document it against the original figures — makes another literature-derived addition likelier than internal refactoring.
Alternatives to giscoR and superspreading
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 giscoR or superspreading.
marquee
marquee is filling in the typographic details — outlines, border types, real font metrics for underlines.
logrx
A clinical-script logger that stopped shipping after its 0.2 line, changelogs made of merged PRs.
lobstr
R's object inspector is losing its view of the internals as CRAN closes off the private C API.
GSODR
A weather-station data client that broke one return type to hand back distances instead of bare IDs.
FedData
FedData has spent two major versions migrating US federal geodata off R's retiring spatial stack.
See all giscoR alternatives → · See all superspreading alternatives →
Recent activity from giscoR and superspreading
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agogiscoRInternal refactor with faster mocked tests
- 4mo agogiscoRDownload timeout becomes configurable
- 6mo agogiscoRCache persistence fixed; urban audit defaults to 2024
- 7mo agogiscoR1.0 caches the dataset index so new vintages need no release ⚡
- 1y agosuperspreadingprobability_emergence() extends the package into pathogen emergence risk ⚡
- 1y agosuperspreadingLloyd-Smith transmission proportions; bpmodels dependency removed
- 1y agogiscoRSource filtering fixed in gisco_get_lau()
- 1y agogiscoR2024 datasets and year arguments for education and healthcare
- 2y agosuperspreadingNetwork reproduction numbers and joint individual/population control
- 2y agosuperspreadingFirst release: offspring distributions and epidemic risk metrics
Frequently asked questions
What is the difference between giscoR and superspreading?
They serve adjacent needs but don't currently overlap on shipped themes. giscoR and superspreading 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 giscoR better than superspreading?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. giscoR and superspreading 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 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.
What are the best alternatives to superspreading?
Top superspreading alternatives in Analytics are ranked by recent ship velocity. Browse the "superspreading alternatives" section above for the current picks, or visit /alternatives/superspreading for the full list with editorial commentary on each.