silx
silx settles into maintenance a release after its PySide6 migration
Comparison · Analytics
duckspatial vs TimescaleDB
A side-by-side editorial comparison of duckspatial and TimescaleDB — release velocity, themes, recent moves, and the top alternatives to consider.
duckspatial vs TimescaleDB: at a glance
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.
What is TimescaleDB?
TimescaleDB is paying down correctness debt in its columnstore query paths.
The 2.29 line is in patch mode after 2.29.0 landed chunk exclusion for DML in late July. 2.29.1 carried three security advisories alongside compression fixes, and 2.29.2 is bug fixes only - most of them wrong-results bugs in the columnar execution paths rather than crashes. Every release note in this window recommends upgrading at the next opportunity.
duckspatial vs TimescaleDB: editorial side-by-side
duckspatial
0.0ANALYTICS
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.
TimescaleDB
5.0ANALYTICS
TimescaleDB is paying down correctness debt in its columnstore query paths.
◆ Current state
The 2.29 line is in patch mode after 2.29.0 landed chunk exclusion for DML in late July. 2.29.1 carried three security advisories alongside compression fixes, and 2.29.2 is bug fixes only - most of them wrong-results bugs in the columnar execution paths rather than crashes. Every release note in this window recommends upgrading at the next opportunity.
◆ Where it's heading
The feature work of 2.27 and 2.28 - vectorized filter evaluation, first/last derived straight from columnstore batch metadata, sparse indexes, SkipScan on compressed data - has been followed by a steady stream of fixes to those same code paths. 2.29.2 alone repairs SkipScan dropping uncompressed rows, sparse-index pushdown returning wrong results for IS NULL, and gapfill over window aggregates. That is the normal cost of pushing query optimizations into a compressed columnar store, and the project is working through it release by release rather than pausing.
◆ Prediction
With three consecutive patch releases on the 2.29 line and no new highlighted features since 2.29.0, the next minor is likely to resume the columnstore performance work - though the density of wrong-results fixes suggests more patches first.
Alternatives to duckspatial and TimescaleDB
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 TimescaleDB.
Plotly
Plotly is turning its cloud into a metered compute platform with an enterprise on-ramp.
aniread
aniread stops asking you to know which tracker wrote the file
Rho
Rho's release machinery finally produced a stable build — and it shipped no new product.
Usermaven
Usermaven closed the loop: data comes in from anywhere, and now it goes back out.
OpenCTI
OpenCTI spends a release unblocking queues and hardening upserts
See all duckspatial alternatives → · See all TimescaleDB alternatives →
Recent activity from duckspatial and TimescaleDB
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoTimescaleDB2.29.2: SkipScan and sparse-index correctness fixes
- 15d agoTimescaleDB2.29.1: security fixes plus compression bugfixes
- 19d agoTimescaleDB2.29.0: chunk exclusion speeds up UPDATE and DELETE
- 1mo agoduckspatialCapture install and load output messages
- 1mo agoTimescaleDB2.28.3: columnar pipeline correctness fixes
- 1mo agoduckspatialVector-tile output, geometry parsers and precision control
- 1mo agoTimescaleDB2.28.2: upgrade-path fixes for 2.28.1
- 1mo agoTimescaleDB2.28.1: compressed-table crash and constraint fixes
- 1mo agoduckspatialShortest-line, azimuth, vertex and coordinate-extreme functions
- 2mo agoduckspatialNative spatial storage becomes the default connection format
- 3mo agoduckspatialduckspatial macros usable inside dplyr verbs
- 4mo agoduckspatialduckspatial_df replaces sf as the default class ⚡
Frequently asked questions
What is the difference between duckspatial and TimescaleDB?
They serve adjacent needs but don't currently overlap on shipped themes. TimescaleDB is currently shipping more aggressively (velocity 5.0 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 duckspatial better than TimescaleDB?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. TimescaleDB is currently shipping more aggressively (velocity 5.0 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 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 TimescaleDB?
Top TimescaleDB alternatives in Analytics are ranked by recent ship velocity. Browse the "TimescaleDB alternatives" section above for the current picks, or visit /alternatives/timescaledb for the full list with editorial commentary on each.