mice
mice can finally predict, not just estimate, from multiply imputed data.
Comparison · Infra & APIs
goat vs usmapdata
A side-by-side editorial comparison of goat and usmapdata — release velocity, themes, recent moves, and the top alternatives to consider.
goat vs usmapdata: at a glance
What is goat?
A gene-set enrichment package that outgrew its human-only origins, then went quiet.
GOAT is a CRAN-published R package for gene set enrichment testing, now at 1.1.4. The visible arc runs from a 2024 beta through a first public CRAN release to a 1.1 line that broadened the package past human gene sets and added persistence for completed analyses. Recent releases are small: the newest ships an igraph handle on plot_network() plus bug fixes.
What is usmapdata?
usmapdata ships its 2025 shapefiles on the year-indexed model it adopted in 0.4.0.
usmapdata supplies the boundary data behind usmap's plotting functions. Since 0.4.0 it has been year-indexed: us_map(data_year = ) selects a vintage, and each Census release is added as its own year with older ones still reachable. 1.1.0 adds 2025. 1.0.0 closed the package's longest-standing gap by adding Puerto Rico, retroactively across every vintage.
goat vs usmapdata: editorial side-by-side
goat
0.0INFRA · APIS
A gene-set enrichment package that outgrew its human-only origins, then went quiet.
◆ Current state
GOAT is a CRAN-published R package for gene set enrichment testing, now at 1.1.4. The visible arc runs from a 2024 beta through a first public CRAN release to a 1.1 line that broadened the package past human gene sets and added persistence for completed analyses. Recent releases are small: the newest ships an igraph handle on plot_network() plus bug fixes.
◆ Where it's heading
The substantive expansion happened in the 1.1 cycle; everything since has been maintenance and plotting ergonomics. Each release since 1.1 touches one function and returns something callers previously had to reconstruct, which reads as a package settling into a stable API and responding to individual user requests rather than pursuing new scope. The 13-month gap between 1.1.2 and 1.1.4 puts it firmly in low-cadence maintenance.
◆ Prediction
Expect continued point releases that expose internals from the plotting functions or refresh the bundled GO release, not new analysis capability. The entries give no signal of a planned 1.2.
usmapdata
2.5INFRA · APIS
usmapdata ships its 2025 shapefiles on the year-indexed model it adopted in 0.4.0.
◆ Current state
usmapdata supplies the boundary data behind usmap's plotting functions. Since 0.4.0 it has been year-indexed: us_map(data_year = ) selects a vintage, and each Census release is added as its own year with older ones still reachable. 1.1.0 adds 2025. 1.0.0 closed the package's longest-standing gap by adding Puerto Rico, retroactively across every vintage.
◆ Where it's heading
The package has settled into a predictable rhythm — one shapefile vintage per year, with structural change rare and clustered. The two changes that mattered were data_year in 0.4.0, which turned a single-vintage dataset into a time series, and the tibble-to-data-frame switch in 0.6.0 that reduced what downstream callers have to depend on.
◆ Prediction
The stated policy — each year added going forward, previous years reachable through data_year — points to a 2026 vintage as the next release. Nothing in these notes suggests further change to the data model.
Alternatives to goat and usmapdata
Other Infra & APIs 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 goat or usmapdata.
PINstimation
A market-microstructure toolkit that keeps adding estimators as the papers land.
nzilbb.vowels
A vowel-analysis package trimming dependencies after an email address got it archived.
emuR
The R half of the EMU speech database system, fixing what was quietly broken.
BAS
A Bayesian model-averaging package spending its 2.0 on memory, not methods.
tidyplots
tidyplots keeps rebuilding its own foundations rather than layering around them.
See all goat alternatives → · See all usmapdata alternatives →
Recent activity from goat and usmapdata
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 23d agousmapdata2025 Census shapefiles added
- 6mo agogoatplot_network() now hands back the igraph object
- 0y agousmapdataPuerto Rico added across every map vintage
- 1y agousmapdataus_map() returns a data frame instead of a tibble
- 1y agousmapdata2024 Census shapefiles added
- 1y agousmapdatadata_year turns the package into a multi-vintage archive ⚡
- 1y agogoatFix for a reduce_genesets() infinite loop
- 1y agogoatGene sets beyond human, and analyses you can reload ⚡
- 2y agousmapdataMap data moves to 2023 shapefiles
- 2y agogoatFirst public release, now on CRAN ⚡
- 2y agogoatplot_lollipop() gains barplots and an effect-size axis
- 2y agogoatBeta 0.9.5 tagged, with no changes described
Frequently asked questions
What is the difference between goat and usmapdata?
They serve adjacent needs but don't currently overlap on shipped themes. usmapdata is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is goat better than usmapdata?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. usmapdata is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to goat?
Top goat alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "goat alternatives" section above for the current picks, or visit /alternatives/goat for the full list with editorial commentary on each.
What are the best alternatives to usmapdata?
Top usmapdata alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "usmapdata alternatives" section above for the current picks, or visit /alternatives/usmapdata for the full list with editorial commentary on each.