osmapiR
osmapiR is the rare API client that tracks its server's wiki revision numbers in the changelog.
A side-by-side editorial comparison of naijR and qualtRics — release velocity, themes, recent moves, and the top alternatives to consider.
naijR is assembling the Nigerian reference data R analysts otherwise hand-code every time.
naijR packages Nigeria-specific data and utilities for R: state and Local Government Area names, choropleth mapping, and phone-number repair. The newest release adds `ngdist`, a UNDP-sourced distance matrix covering road distances between all 37 state capitals, with `ng_distance()` for pairwise lookup in kilometres or miles. The spatial foundation was rebased on sf in 0.6.0, retiring the rgdal-era code.
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.
naijR packages Nigeria-specific data and utilities for R: state and Local Government Area names, choropleth mapping, and phone-number repair. The newest release adds `ngdist`, a UNDP-sourced distance matrix covering road distances between all 37 state capitals, with `ng_distance()` for pairwise lookup in kilometres or miles. The spatial foundation was rebased on sf in 0.6.0, retiring the rgdal-era code.
The package keeps converting local knowledge into checked data structures. LGA names shared between states got `disambiguate_lga()` with interactive selection; misspellings in the original reference document were corrected; mobile numbers with inconsistent separators, or with the letter O typed for zero, get repaired rather than rejected. Each addition targets a specific way Nigerian administrative or contact data breaks generic tooling, which is a narrower and more durable brief than most country packages take on.
With a distance matrix now in place alongside the boundary and naming data, the plausible next step is more derived geography of the same kind rather than new utility functions, though the entries do not say which dataset is next.
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.
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.
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.
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 naijR or qualtRics.
osmapiR is the rare API client that tracks its server's wiki revision numbers in the changelog.
ymlthis retired itself, naming Quarto as the reason it no longer needs to exist.
forestly built an interactive safety review tool, then taught it to produce submission-ready RTF.
pharmaverseadam is the pharmaverse's test-data mirror, and it now covers neurology.
pkglite's whole job is knowing which files in an R package are text — and it keeps getting better at guessing.
gMCPLite exists to be gMCP without Java, and its releases guard that boundary rather than extend it.
See all naijR alternatives → · See all qualtRics alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. naijR 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. naijR 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.
Top naijR alternatives in Analytics are ranked by recent ship velocity. Browse the "naijR alternatives" section above for the current picks, or visit /alternatives/naijr for the full list with editorial commentary on each.
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.