Use DuckDB's filesystem for GDAL by default, Handle GDAL errors, Add ST_Union_Agg(), ST_Intersection_Agg().
#126
Conversation
This file contains 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
… status). Throw proper exceptions on GDAL errors
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We now use DuckDB's filesystem abstractions in all GDAL I/O operations by default. This is pretty huge as
ST_Readwill now be able to work in WASM as well as in combination with DuckDB'shttpfsextension. We still expose GDAL's virtual filesystems though so you can still do e.g. /vsicurl/ ifhttpfsis not installed.We now also capture GDAL errors and throw DuckDB exceptions instead, no more double-errors being printed in the CLI.
We now initialize GDAL once globally regardless of how many attached databases loads the spatial extension. We also just enable the bundled drivers and don't go looking in external directories for loadable plugins.
Add
ST_Union_Agg/ST_Intersection_Aggaggregate functions based on GEOS. These are not as performant as I would like but should still be useful.