Support duckspatial native GeoArrow streams - #19
Merged
Merged
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
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.
Summary
Adds direct support for
duckspatial_dfobjects.When
addSource()receives aduckspatial_df, it requests DuckSpatial's native GeoArrow representation. This lets users pass lazy DuckDB spatial query results directly to a Deck.gl layer without first collecting ansfobject or manually converting WKB geometries.This depends on Cidree/duckspatial#150, which fixes
native = TRUEto produce native GeoArrow Point, LineString, and Polygon layouts.Example
Users do not need to set
native = TRUE;deckglgeoarrowselects that conversion automatically.The included test checks that
duckspatial_dfinputs use the native GeoArrow path without adding DuckSpatial as a package dependency.