metatools
SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.
Comparison · Analytics
giscoR vs teal.modules.clinical
A side-by-side editorial comparison of giscoR and teal.modules.clinical — release velocity, themes, recent moves, and the top alternatives to consider.
giscoR vs teal.modules.clinical: 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 teal.modules.clinical?
Roche's clinical teal modules have settled into slow, decorator-driven maintenance.
The module library took its architectural break in 0.9.0, when every module moved to teal_data objects and dropped data_extract_spec inputs. Work since then is narrower: formatting arguments, decorator plumbing, and per-module bug fixes. The 0.13.0 candidates cut in July 2026 are a two-tag same-day release where the first tag carries all the notes.
giscoR vs teal.modules.clinical: 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.
teal.modules.clinical
0.0ANALYTICS
Roche's clinical teal modules have settled into slow, decorator-driven maintenance.
◆ Current state
The module library took its architectural break in 0.9.0, when every module moved to teal_data objects and dropped data_extract_spec inputs. Work since then is narrower: formatting arguments, decorator plumbing, and per-module bug fixes. The 0.13.0 candidates cut in July 2026 are a two-tag same-day release where the first tag carries all the notes.
◆ Where it's heading
Development has shifted from reshaping the module API to making outputs configurable — numeric formatting in tm_t_summary, several decorators applied to one output object, categorical statistics in summary_by. Changes arrive from a wide bench of Roche engineers with occasional outside contributors, and releases go through candidates rather than straight to final.
◆ Prediction
A 0.13.0 final should follow the candidates with little beyond a dependency bump; the decorator work ported from teal.modules.general is the most likely source of the next batch of changes.
Alternatives to giscoR and teal.modules.clinical
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 teal.modules.clinical.
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 teal.modules.clinical alternatives →
Recent activity from giscoR and teal.modules.clinical
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agoteal.modules.clinicalNumeric formatting control and multi-decorator outputs
- 1mo agoteal.modules.clinicalteal.transform dependency bump
- 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 agogiscoRSource filtering fixed in gisco_get_lau()
- 1y agogiscoR2024 datasets and year arguments for education and healthcare
- 2y agoteal.modules.clinicalForest and Kaplan-Meier plots move to ggplot objects
- 2y agoteal.modules.clinicalEvery clinical module migrates to teal_data objects ⚡
Frequently asked questions
What is the difference between giscoR and teal.modules.clinical?
They serve adjacent needs but don't currently overlap on shipped themes. giscoR and teal.modules.clinical 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 teal.modules.clinical?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. giscoR and teal.modules.clinical 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 teal.modules.clinical?
Top teal.modules.clinical alternatives in Analytics are ranked by recent ship velocity. Browse the "teal.modules.clinical alternatives" section above for the current picks, or visit /alternatives/teal-modules-clinical for the full list with editorial commentary on each.