rtflite
rtflite stopped being an RTF writer and became the conversion layer for clinical table output.
Comparison · Analytics
giscoR vs qualtRics
A side-by-side editorial comparison of giscoR and qualtRics — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:ropenscir-package
giscoR vs qualtRics: 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 qualtRics?
qualtRics moved its contact functions onto XM Directory days before the old endpoints died.
qualtRics is the R client for the Qualtrics v3 API — fetching survey responses, definitions, distributions, and contact lists into tidy data frames. Version 3.3.0 migrated all_mailinglists() and fetch_mailinglist() from the deprecated Research Core Contacts endpoints to XM Directory, ahead of Qualtrics retiring the old ones on June 30, 2026. Authentication and directory discovery are handled automatically, but the new endpoints return a different data shape, so column names changed. Before that, releases had been steady maintenance for two years, mostly around how survey response archives are unpacked.
giscoR vs qualtRics: 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.
qualtRics
0.0ANALYTICS
qualtRics moved its contact functions onto XM Directory days before the old endpoints died.
◆ Current state
qualtRics is the R client for the Qualtrics v3 API — fetching survey responses, definitions, distributions, and contact lists into tidy data frames. Version 3.3.0 migrated all_mailinglists() and fetch_mailinglist() from the deprecated Research Core Contacts endpoints to XM Directory, ahead of Qualtrics retiring the old ones on June 30, 2026. Authentication and directory discovery are handled automatically, but the new endpoints return a different data shape, so column names changed. Before that, releases had been steady maintenance for two years, mostly around how survey response archives are unpacked.
◆ Where it's heading
This package's roadmap is set by Qualtrics, not by its maintainers, and the release history reads as a sequence of accommodations — endpoint changes, retired APIs, and edge cases in exported files. The team's own recurring theme is reducing surprise: caching was removed from fetch_survey() in 3.2.0 so results are never stale, error handling was standardized on retry semantics, and column mappings were made inspectable via extract_colmap(). Feature additions, when they come, are new endpoints wrapped rather than new abstractions.
◆ Prediction
With the Contacts migration complete, the next likely work is bringing the remaining Research Core-era functions onto XM Directory equivalents before Qualtrics retires more of the old surface.
Alternatives to giscoR and qualtRics
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 qualtRics.
git2rdata
git2rdata keeps sharpening one idea: a data frame that produces a readable git diff.
osmextract
osmextract stopped throwing your OpenStreetMap downloads away at the end of every session.
nanoparquet
nanoparquet is chasing byte-level agreement with the Java and Rust Parquet readers, not feature count.
poissonreg
poissonreg gave its models away to parsnip and kept the glue — now it just keeps glmnet honest.
S7
S7 has stopped adding surface and started proving it holds up against R itself.
See all giscoR alternatives → · See all qualtRics alternatives →
Recent activity from giscoR and qualtRics
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agoqualtRicsMailing list functions migrated to the XM Directory API ⚡
- 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 ⚡
- 11mo agoqualtRicsZip extraction handles more special characters in survey titles
- 1y agogiscoRSource filtering fixed in gisco_get_lau()
- 1y agogiscoR2024 datasets and year arguments for education and healthcare
- 1y agoqualtRicsFix for questions with both recoded values and variable naming
- 1y agoqualtRicsBuild and CI housekeeping alongside the 3.2.1 release
- 2y agoqualtRicsSurvey response caching removed from fetch_survey()
- 3y agoqualtRicsArgument checking refactor and include_* NA fix
Frequently asked questions
What is the difference between giscoR and qualtRics?
Both compete on the same themes — ropensci, r-package — within Analytics. giscoR and qualtRics 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 qualtRics?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. giscoR and qualtRics 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 qualtRics?
Top qualtRics alternatives in Analytics are ranked by recent ship velocity. Browse the "qualtRics alternatives" section above for the current picks, or visit /alternatives/qualtrics for the full list with editorial commentary on each.