feat(duckdb): set wkb metadata #636
Merged
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
gadomski
force-pushed
the
duckdb-wkb-metadata
branch
from
9cf09cf to
e4fe26b
Compare
gadomski
force-pushed
the
duckdb-wkb-metadata
branch
from
e4fe26b to
63c6be8
Compare
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.
I think we'll want to set the
geoarrow.wkbfield extension as shown here so we can later load our produced record batches into GeoPandas, etc. GeoPandas doesn't understandgeoarrow.geometryyet, which is what our wkb-parsing workflow produces.Not sending b/c I can't test w/ GeoPandas downstream in stacrs yet because <gestures in Rust+Python> that I haven't been able to unpick yet.