metatools
SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.
A side-by-side editorial comparison of giscoR and sivirep — release velocity, themes, recent moves, and the top alternatives to consider.
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.
sivirep turned Colombia's SIVIGILA surveillance data into a one-call reporting package.
The 1.0.0 release of December 2024 is the substance of this feed: incidence calculation and plotting for the country, departments and municipalities, ethnicity and case-classification breakdowns, multi-year retrospectives, and a Reporte Evento template that assembles them. It was shaped by usability testing and expert review with Colombia's National Institute of Health. The two patches since are fixes, warnings and documentation.
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.
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.
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.
The 1.0.0 release of December 2024 is the substance of this feed: incidence calculation and plotting for the country, departments and municipalities, ethnicity and case-classification breakdowns, multi-year retrospectives, and a Reporte Evento template that assembles them. It was shaped by usability testing and expert review with Colombia's National Institute of Health. The two patches since are fixes, warnings and documentation.
Work after 1.0.0 has gone into making the report template survive bad input rather than adding analyses — warnings when a municipality or department has no data, handlers that surface import and geo-filter errors during rendering, and an explicit note that first use of any import function needs an internet connection. English-language articles were added alongside the Spanish function interface.
Spanish-named functions paired with new English articles point at a widening audience; more translation of the guides looks likelier than new epidemiological methods.
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 sivirep.
SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.
marquee is filling in the typographic details — outlines, border types, real font metrics for underlines.
A clinical-script logger that stopped shipping after its 0.2 line, changelogs made of merged PRs.
R's object inspector is losing its view of the internals as CRAN closes off the private C API.
A weather-station data client that broke one return type to hand back distances instead of bare IDs.
FedData has spent two major versions migrating US federal geodata off R's retiring spatial stack.
See all giscoR alternatives → · See all sivirep alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. giscoR and sivirep 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. giscoR and sivirep 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.
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.
Top sivirep alternatives in Analytics are ranked by recent ship velocity. Browse the "sivirep alternatives" section above for the current picks, or visit /alternatives/sivirep for the full list with editorial commentary on each.