Passing a geopandas.GeoDataFrame directly to memtable will yield a bunch of
errors because our various to_arrow and other proxy methods don't know how to
handle the bundled geo data.
As an intermediate bit of functionality until things like geoarrow are more
widely supported, this PR adds an extra dispatch to the memtable constructor
to 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.
Description of changes
Passing a
geopandas.GeoDataFrame
directly tomemtable
will yield a bunch of errors because our variousto_arrow
and other proxy methods don't know how to handle the bundled geo data.As an intermediate bit of functionality until things like
geoarrow
are more widely supported, this PR adds an extra dispatch to thememtable
constructor to 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 togeometry
columns in backends that support that.Issues closed
Resolves #10453