metatools
SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.
Comparison · Analytics
giscoR vs pharmaversesdtm
A side-by-side editorial comparison of giscoR and pharmaversesdtm — release velocity, themes, recent moves, and the top alternatives to consider.
giscoR vs pharmaversesdtm: 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 pharmaversesdtm?
pharmaversesdtm is the test-data layer every pharmaverse package now builds against.
The package ships example SDTM datasets and has grown one therapeutic area at a time — ophthalmology, oncology response criteria, vaccines, metabolic, neurology, and now lymphoma under Lugano 2014. Sibling packages keep moving their internal test data here, so its release notes double as a record of what the rest of the pharmaverse is building.
giscoR vs pharmaversesdtm: 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.
pharmaversesdtm
0.0ANALYTICS
pharmaversesdtm is the test-data layer every pharmaverse package now builds against.
◆ Current state
The package ships example SDTM datasets and has grown one therapeutic area at a time — ophthalmology, oncology response criteria, vaccines, metabolic, neurology, and now lymphoma under Lugano 2014. Sibling packages keep moving their internal test data here, so its release notes double as a record of what the rest of the pharmaverse is building.
◆ Where it's heading
Two kinds of work alternate: adding domains and biomarkers for a new indication, and making the existing data easier to reach — CSV copies under inst/extdata for non-R programmers, a datasets preview vignette, reference pages categorised by therapeutic area, variable-by-variable breakdowns. Consistency fixes against CDISC terminology and SDTM guidelines run through every release.
◆ Prediction
New therapeutic areas will keep arriving in step with the admiral extension packages that need them; the neurology and metabolic datasets landed just ahead of admiralneuro and admiralmetabolic needing them, and lymphoma looks like the next in that sequence.
Alternatives to giscoR and pharmaversesdtm
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 pharmaversesdtm.
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 pharmaversesdtm alternatives →
Recent activity from giscoR and pharmaversesdtm
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agopharmaversesdtmLymphoma response data and geographic-atrophy tests
- 1mo agogiscoRInternal refactor with faster mocked tests
- 4mo agopharmaversesdtmCSV exports and microbiology domains for wider access
- 4mo agogiscoRDownload timeout becomes configurable
- 6mo agogiscoRCache persistence fixed; urban audit defaults to 2024
- 7mo agopharmaversesdtmNeurological SDTM datasets and Alzheimer's biomarkers
- 7mo agogiscoR1.0 caches the dataset index so new vintages need no release ⚡
- 11mo agopharmaversesdtmMaintainer and licensing update
- 1y agopharmaversesdtmMetabolic SDTM datasets and PCWG3 oncology response
- 1y agogiscoRSource filtering fixed in gisco_get_lau()
- 1y agopharmaversesdtmGCIG response data and automated reference pages
- 1y agogiscoR2024 datasets and year arguments for education and healthcare
Frequently asked questions
What is the difference between giscoR and pharmaversesdtm?
They serve adjacent needs but don't currently overlap on shipped themes. giscoR and pharmaversesdtm 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 pharmaversesdtm?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. giscoR and pharmaversesdtm 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 pharmaversesdtm?
Top pharmaversesdtm alternatives in Analytics are ranked by recent ship velocity. Browse the "pharmaversesdtm alternatives" section above for the current picks, or visit /alternatives/pharmaversesdtm for the full list with editorial commentary on each.