spsurvey
spsurvey has spent four years consolidating after its 5.0.0 rewrite rather than adding to it
A side-by-side editorial comparison of duckspatial and tibblify — release velocity, themes, recent moves, and the top alternatives to consider.
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.
tibblify learned to derive its own specs from OpenAPI, removing the step users disliked most
tibblify converts nested lists and JSON into rectangular tibbles using an explicit specification of the expected structure. Its 0.2.0 rewrite moved the engine to C and reset the API; 0.3.1 then added a path to generate specifications from an OpenAPI document rather than hand-writing them. 0.4.0 in May 2026 is the first release in over two years, and it is a breaking cleanup.
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.
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.
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.
tibblify converts nested lists and JSON into rectangular tibbles using an explicit specification of the expected structure. Its 0.2.0 rewrite moved the engine to C and reset the API; 0.3.1 then added a path to generate specifications from an OpenAPI document rather than hand-writing them. 0.4.0 in May 2026 is the first release in over two years, and it is a breaking cleanup.
The arc runs from 'write a spec by hand' toward 'the spec comes from somewhere else'. Alongside the OpenAPI importer, guess_tspec() gained exported variants so users can override its dispatch, and untibblify() now picks up the tib_spec attribute automatically. 0.4.0's breaking change prefixes all arguments of dot-accepting functions with a period to avoid collisions with column names, softened by a once-per-session deprecation warning, and refactors the entire codebase.
The un-dotted argument forms are explicitly slated for removal, so the next release most likely completes that deprecation. Whether the 0.4.0 refactor introduced corner-case regressions is the open question the release notes themselves raise.
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 tibblify.
spsurvey has spent four years consolidating after its 5.0.0 rewrite rather than adding to it
StreamCatTools is quietly moving off web services and onto cloud-native GeoParquet
reproducible added a windowed read path so remote GeoTiffs never fully download
qcTAF is building an automated checklist for reproducible fisheries assessments, one criterion at a time
After three dormant years, rpymat returned to fix the OpenMP crash that breaks R and conda together
ieegio's first release lands electrode trajectory burning and a WebGL-free surface plot
See all duckspatial alternatives → · See all tibblify alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r — within Analytics. duckspatial and tibblify 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. duckspatial and tibblify 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 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.
Top tibblify alternatives in Analytics are ranked by recent ship velocity. Browse the "tibblify alternatives" section above for the current picks, or visit /alternatives/tibblify for the full list with editorial commentary on each.