You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should ensure we can both read and write files with such encoding for the geometry column(s).
For writing, we can have an encoding keyword which still defaults to "WKB", but where can specify one of the new encodings as well ("point", "linestring" etc).
We could maybe also accept an additional value of "geoarrow" that will then infer the actual geometry-specific encoding from the data?
The text was updated successfully, but these errors were encountered:
Closely related to #3219, but focused on GeoParquet.
GeoParquet 1.1 added a bunch of encodings: https://github.com/opengeospatial/geoparquet/blob/main/format-specs/geoparquet.md#native-encodings-based-on-geoarrow
We should ensure we can both read and write files with such encoding for the geometry column(s).
For writing, we can have an
encoding
keyword which still defaults to"WKB"
, but where can specify one of the new encodings as well ("point"
,"linestring"
etc).We could maybe also accept an additional value of
"geoarrow"
that will then infer the actual geometry-specific encoding from the data?The text was updated successfully, but these errors were encountered: