Skip to contents

duckspatial 0.9.0

MAJOR CHANGES

  • conn argument defaults now to NULL. This parameter is not mandatory anymore in spatial operations, and it will be handled internally. The argument has been moved after x, y, and function-mandatory arguments (#9).

  • ddbs_write_vector() allows to create a temporary view with the argument temp = TRUE, which is much faster than creating a table (#14).

  • ddbs_read_vector() uses internal optimizations with geoarrow making it much faster (#15).

  • The spatial functions allow now to have either an sf or a DuckDB table as input (x) and/or output (name = NULL or name != NULL) (#19).

  • The crs and crs_column arguments are deprecated and will be removed in duckspatial v1.0.0. This change aligns with planned native CRS support in DuckDB, scheduled for v1.5.0 (expected February 2025) (#7).

NEW FEATURES

MINOR CHANGES

  • All functions now have a parameter quiet that allows users to suppress messages (#3).

  • Spatial operations now don’t fail when a column has a dot (#33).

  • Added some vignettes (#42).

  • ddbs_filter(): uses intersects for ST_Intersects instead of intersection.

  • ddbs_filter(): doesn’t return duplicated observations when the same geometry fulfills the spatial predicate in more than one geometries of y (#50).

duckspatial 0.2.0

CRAN release: 2025-04-29

NEW FEATURES

  • ddbs_read_vector(): gains a new argument clauses to modify the query from the table (e.g. “WHERE …”, “ORDER BY…”)

NEW FUNCTIONS

IMPROVEMENTS

  • ddbs_intersection(): overwrite argument defaults to FALSE instead of NULL

  • Better schemas management. Added support for all functions.

duckspatial 0.1.0

CRAN release: 2025-04-19

  • Initial CRAN submission.