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
Writing (to_parquet): optionally compute and add this column to written file (behind some option, eg write_bbox_covering=True/False?)
Reading (read_parquet):
Allow the user to specify a bbox to filter (similarly as read_file), and automatically translate this to a pyarrow filter predicate.
By default drop the bbox struct column when reading and converting to pandas? I would say yes (converting a struct column to pandas is expensive), but would there be a use case for providing an option to keep it?
The text was updated successfully, but these errors were encountered:
GeoParquet 1.1 is adding a new feature to the spec: bbox columns ("bbox covering encoding", https://github.com/opengeospatial/geoparquet/blob/main/format-specs/geoparquet.md#covering)
We should add support for that to geopandas:
to_parquet
): optionally compute and add this column to written file (behind some option, egwrite_bbox_covering=True/False
?)read_parquet
):bbox
to filter (similarly asread_file
), and automatically translate this to a pyarrowfilter
predicate.The text was updated successfully, but these errors were encountered: