← Back to home
Comparison · Analytics

duckspatial vs glystats

A side-by-side editorial comparison of duckspatial and glystats — release velocity, themes, recent moves, and the top alternatives to consider.

duckspatial vs glystats: at a glance

Featureduckspatialglystats
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesr, duckdb, geospatial, lazy evaluationglycomics, statistics, differential analysis, breaking changes
Last editorial update15m ago1h ago
WebsiteVisit →Visit →

What is duckspatial?

duckspatial rebuilt itself around a lazy DuckDB class, then spent four releases filling in the geometry surface

duckspatial exposes DuckDB's spatial extension to R. In March 2026 it stopped being an sf convenience wrapper: 1.0.0 made duckspatial_df the primary class, a lazy table-like object that stays in DuckDB until explicitly materialized. Every function accepts and returns it by default, with mode = 'sf' as the opt-out. The four releases since have added roughly forty geometry functions on top of that foundation.

Read the full duckspatial trajectory →

What is glystats?

glystats keeps deleting analyses it decided belong somewhere else.

glystats provides the statistical tests behind glycoverse: differential analysis, clustering, dimensionality reduction, and until recently enrichment. The last four releases are mostly subtraction. WGCNA and consensus clustering were removed in 0.10.0 as too interactive for a pipeline package, the enrichment functions were deprecated in the same release and deleted in 0.11.0 in favor of glyfun, and 0.11.0 also removed every gly_*_() matrix and vector interface. What remains accepts SummarizedExperiment inputs.

Read the full glystats trajectory →

duckspatial vs glystats: editorial side-by-side

D
duckspatial
ANALYTICS
0.0

duckspatial rebuilt itself around a lazy DuckDB class, then spent four releases filling in the geometry surface

◆ Current state

duckspatial exposes DuckDB's spatial extension to R. In March 2026 it stopped being an sf convenience wrapper: 1.0.0 made duckspatial_df the primary class, a lazy table-like object that stays in DuckDB until explicitly materialized. Every function accepts and returns it by default, with mode = 'sf' as the opt-out. The four releases since have added roughly forty geometry functions on top of that foundation.

◆ Where it's heading

The direction is to keep work inside DuckDB and make R the orchestration layer rather than the compute layer. 1.1.0 added macros so duckspatial functions work inside dplyr verbs; 1.1.1 moved the default to DuckDB v1.5.0 native spatial storage so CRS metadata persists in GEOMETRY columns; 1.2.0 added vector-tile output via ddbs_write_mbtiles() and the full family of geometry deserializers. Feature velocity has been high and consistent since the rewrite.

◆ Prediction

The remaining gaps are in PostGIS parity — the deserializers and tile writers landed in 1.2.0, so raster support or spatial indexing are the plausible next targets. 1.2.1 being a single message-capture fix suggests the 1.2.x line is now stabilizing.

G
glystats
ANALYTICS
0.0

glystats keeps deleting analyses it decided belong somewhere else.

◆ Current state

glystats provides the statistical tests behind glycoverse: differential analysis, clustering, dimensionality reduction, and until recently enrichment. The last four releases are mostly subtraction. WGCNA and consensus clustering were removed in 0.10.0 as too interactive for a pipeline package, the enrichment functions were deprecated in the same release and deleted in 0.11.0 in favor of glyfun, and 0.11.0 also removed every gly_*_() matrix and vector interface. What remains accepts SummarizedExperiment inputs.

◆ Where it's heading

The package is narrowing on purpose. The through-line across removals is a refusal to support two calling conventions or two homes for the same analysis: containers only, no bare matrices; one enrichment implementation, in glyfun. The additive work in the window went to statistical rigor rather than surface area, with effect sizes added to the four main tests, sign bugs fixed, and the log2 pseudo-count reduced.

◆ Prediction

With the interface pruning finished, the next releases are more likely to deepen the tests that remain than to add new analysis families.

Alternatives to duckspatial and glystats

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 duckspatial or glystats.

See all duckspatial alternatives → · See all glystats alternatives →

Recent activity from duckspatial and glystats

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1mo agoduckspatialCapture install and load output messages
  2. 1mo agoglystatsDocs recommend the new SE containers
  3. 1mo agoglystatsTests recognize both container types consistently
  4. 1mo agoglystatsMatrix interfaces and enrichment functions removed
  5. 1mo agoduckspatialVector-tile output, geometry parsers and precision control
  6. 1mo agoduckspatialShortest-line, azimuth, vertex and coordinate-extreme functions
  7. 2mo agoduckspatialNative spatial storage becomes the default connection format
  8. 2mo agoglystatsSmaller log2 pseudo-count across DEA and clustering
  9. 2mo agoduckspatialduckspatial macros usable inside dplyr verbs
  10. 3mo agoglystatsWGCNA and clustering dropped, enrichment deprecated
  11. 4mo agoglystatsEffect sizes added and test statistic signs fixed
  12. 4mo agoduckspatialduckspatial_df replaces sf as the default class

Frequently asked questions

What is the difference between duckspatial and glystats?

They serve adjacent needs but don't currently overlap on shipped themes. duckspatial and glystats 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 duckspatial better than glystats?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. duckspatial and glystats 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 duckspatial?

Top duckspatial alternatives in Analytics are ranked by recent ship velocity. Browse the "duckspatial alternatives" section above for the current picks, or visit /alternatives/duckspatial for the full list with editorial commentary on each.

What are the best alternatives to glystats?

Top glystats alternatives in Analytics are ranked by recent ship velocity. Browse the "glystats alternatives" section above for the current picks, or visit /alternatives/glystats for the full list with editorial commentary on each.