feat(geospatial): accept geopandas GDFs in memtable
#10485
Merged
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.
Description of changes
Passing a
geopandas.GeoDataFrame
directly tomemtable
will yield a bunch oferrors because our various
to_arrow
and other proxy methods don't know how tohandle the bundled geo data.
As an intermediate bit of functionality until things like
geoarrow
are morewidely supported, this PR adds an extra dispatch to the
memtable
constructorto cast geometry columns to WKB, which allows most backends to ingest the
resulting data with the geo columns as binary, which can then be cast to
geometry
columns in backends that support that.Issues closed
Resolves #10453