Update to new DuckDB, use new core GEOMETRY type, rework GDAL integration.
#713
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
It returns a bounding polygon expanded by a specified amount. A common use case is doing a "near" search on a point. This is a postgis function, not found by me in OGC MM. See https://postgis.net/docs/ST_Expand.html
No functional changes.
…gth segments in polygon rings
Setup CI for v1.4 branch, fix bug in st_distance when processing zero-length segments in polygon rings
… ogc.wkb and not geoarrow
…into gdal-arrow
Changes GEOS_PREC_NO_TOPO to GEOS_PREC_VALID_OUTPUT in get_gridded() to ensure topological validity during grid snapping operations.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context: duckdb/duckdb#19136
This PR adapts spatial to use the new core
GEOMETRYtype that will be part of DuckDB v1.5. It also introduces some other changes that are planned for v1.5GEOMETRYnow defaults to GeoArrow when converting to/from arrow, no need to callregister_geoarrow_extensions()ST_Read()has been cleaned up a lot.spatial_filterandspatial_filter_boxoptions has been removed, DuckDB will now automatically push down bounding-box filters.sequential_layer_scanoption has been removed (its applied automatically for OSM imports internally now)ST_Readwill now emit statistics for geometry columns if available, that could potentially help with query planning in the future.ST_Readnow emits the specialOGC_FIDcolumn if available.COPY (...) TO ... (FORMAT GDAL)now uses arrow to pass data to GDAL, which makes it significantly faster to export data out through the different GDAL drivers. More column data types are also supported.