v0.1.0

Initial Release of GeoParquet

This is our first release of the GeoParquet specification. It should provide a clear target for implementations interested in providing support for geospatial vector data with Parquet, as we iterate to a stable 1.0.0 spec.

Initial work started in the geo-arrow-spec GeoPandas repository, and that will continue on Arrow work in a compatible way, with this specification focused solely on Parquet.

What's Changed

• Update geoparquet spec by @TomAugspurger in #2
• Attempt to align with geoarrow spec by @cholmes in #4
• Align "geo" key in metadata and example by @jorisvandenbossche in #5
• Clarify the Parquet FileMetadata value formatting (UTF8 string, JSON-encoded) by @jorisvandenbossche in #6
• Clarify that WKB means "standard" WKB enconding by @TomAugspurger in #16
• More explicitly mention the metadata is stored in the parquet FileMetaData by @jorisvandenbossche in #20
• Readme enhancements by @cholmes in #19
• Optional column metadata field to store bounding box information by @jorisvandenbossche in #21
• Clarify that additional top-level fields in the JSON metadata are allowed by @jorisvandenbossche in #28
• CRS spec definition for version 0.1 by @alasarr in #25
• Update example parquet file by @TomAugspurger in #24
• Clean up TODOs in geoparquet.md by @TomAugspurger in #31
• "edges" field spec definition for version 0.1 by @Jesus89 in #27
• Add known libraries that support GeoParquet to README by @jorisvandenbossche in #29
• Updated warning in readme by @cholmes in #33

New Contributors

• @TomAugspurger made their first contribution in #2
• @cholmes made their first contribution in #4
• @jorisvandenbossche made their first contribution in #5
• @alasarr made their first contribution in #25
• @Jesus89 made their first contribution in #27

Full Changelog: https://github.com/opengeospatial/geoparquet/commits/v0.1.0