Just a heads up that the main parquet specification has moved from https://github.com/geopandas/geo-arrow-spec/ to https://github.com/opengeospatial/geoparquet, and that we officially released it as v0.1.0 (https://github.com/opengeospatial/geoparquet/releases/tag/v0.1.0).
In practice, however, this package should already be compliant to this spec (if it followed the metadata spec as in https://github.com/geopandas/geo-arrow-spec/). We only added an additional "edges" field, but since this is optional, not having it is not violating the spec (and the default is probably correct in most cases).
The new version in https://github.com/opengeospatial/geoparquet also doesn't include the top-level "creator" field with library name and version. But since additional fields are allowed, this is strictly speaking also not violating the spec.
So you might not need to change much in practice (but could certainly update the readme to include a link to https://github.com/opengeospatial/geoparquet).
We are still keeping the https://github.com/geopandas/geo-arrow-spec/ repo for Arrow-specific standards (extension types, other ways to store the geometries than WKB, ..), while the main GeoParquet metadata spec is now covered in https://github.com/opengeospatial/geoparquet,
Just a heads up that the main parquet specification has moved from https://github.com/geopandas/geo-arrow-spec/ to https://github.com/opengeospatial/geoparquet, and that we officially released it as v0.1.0 (https://github.com/opengeospatial/geoparquet/releases/tag/v0.1.0).
In practice, however, this package should already be compliant to this spec (if it followed the metadata spec as in https://github.com/geopandas/geo-arrow-spec/). We only added an additional "edges" field, but since this is optional, not having it is not violating the spec (and the default is probably correct in most cases).
The new version in https://github.com/opengeospatial/geoparquet also doesn't include the top-level "creator" field with library name and version. But since additional fields are allowed, this is strictly speaking also not violating the spec.
So you might not need to change much in practice (but could certainly update the readme to include a link to https://github.com/opengeospatial/geoparquet).
We are still keeping the https://github.com/geopandas/geo-arrow-spec/ repo for Arrow-specific standards (extension types, other ways to store the geometries than WKB, ..), while the main GeoParquet metadata spec is now covered in https://github.com/opengeospatial/geoparquet,