TAF
TAF keeps turning ICES stock assessments into reproducible, dependency-pinned projects.
A side-by-side editorial comparison of geomander and gwasvcf — release velocity, themes, recent moves, and the top alternatives to consider.
A redistricting toolkit that grows mostly by wiring in new public data sources
geomander provides geographic tools for redistricting analysis in R — matching and aggregating across block, VTD and district geometries, spatial diagnostics, and download helpers for the datasets the field relies on. Recent work splits between data access, with fetchers added for Jeffrey B. Lewis's historical congressional districts and RPV Near Me, and performance, with 2.5.0 delivering large speed gains in geo_match().
gwasvcf has stopped adding features and now just keeps proxy matching from failing.
gwasvcf reads and queries GWAS summary statistics stored as VCF, with LD proxy lookup as its most-used entry point. Every release in the visible window is a fix, and all but one land in or around proxy_match(). The last functional addition was gwasvcf_to_summaryset() in 0.1.2, which hands data to gwasglue2 rather than doing new work here.
geomander provides geographic tools for redistricting analysis in R — matching and aggregating across block, VTD and district geometries, spatial diagnostics, and download helpers for the datasets the field relies on. Recent work splits between data access, with fetchers added for Jeffrey B. Lewis's historical congressional districts and RPV Near Me, and performance, with 2.5.0 delivering large speed gains in geo_match().
The package is consolidating as infrastructure rather than expanding its analytical surface. Each release either adds a source of redistricting data that users would otherwise download by hand, or makes the core geographic matching operations faster and more correct — the normalized global Moran's I correction and the block-level geometry mismatch fix both fall in the second category. geo_match() being the target of the most recent release confirms where the hot path is.
With geo_match() now optimised, the remaining friction is in the download helpers, several of which have needed repair after upstream changes; expect the next release to consolidate or harden those fetchers rather than add analysis functions.
gwasvcf reads and queries GWAS summary statistics stored as VCF, with LD proxy lookup as its most-used entry point. Every release in the visible window is a fix, and all but one land in or around proxy_match(). The last functional addition was gwasvcf_to_summaryset() in 0.1.2, which hands data to gwasglue2 rather than doing new work here.
The package is in custodial maintenance inside the MRC IEU OpenGWAS stack, and its releases are reactive: each one answers a specific user-reported failure, credited to the reporter. The 0.1.6 pattern is telling — rather than replace the proxy VCF construction, it keeps the original path and adds a fallback only for inputs that fail, so existing results are left bit-for-bit unchanged.
Expect further narrow robustness fixes to proxy_match() driven by user-reported VCF shapes; nothing in the entries suggests new analysis capability is being built here rather than in gwasglue2.
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 geomander or gwasvcf.
TAF keeps turning ICES stock assessments into reproducible, dependency-pinned projects.
parallelDist is in pure preservation mode — one build fix every few years.
Cairo finally catches R's graphics engine, all the way to GE API 16.
rjdqa keeps refining one screen: the seasonal adjustment quality dashboard
epikit narrows to field-epidemiology helpers, handing proportions to a sibling package
SimInf 10.0 turns an epidemic simulator into a tool that fits models to real time series
See all geomander alternatives → · See all gwasvcf alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. geomander and gwasvcf 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. geomander and gwasvcf 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 geomander alternatives in Analytics are ranked by recent ship velocity. Browse the "geomander alternatives" section above for the current picks, or visit /alternatives/geomander-r for the full list with editorial commentary on each.
Top gwasvcf alternatives in Analytics are ranked by recent ship velocity. Browse the "gwasvcf alternatives" section above for the current picks, or visit /alternatives/gwasvcf for the full list with editorial commentary on each.