From 569b341c69c7039384c4f628dcce2eb5d9ac0ca1 Mon Sep 17 00:00:00 2001 From: Chris Holmes Date: Wed, 19 Jun 2024 11:30:03 -0700 Subject: [PATCH] Updates for the 1.1.0 release (#230) * Updates for the 1.1.0 release * Bump version number in example_metadata_point.json file * readme updates for 1.1.0 * Develop on 1.2.0-dev --------- Co-authored-by: Tim Schaub --- README.md | 11 ++--------- examples/example.parquet | Bin 29838 -> 29838 bytes examples/example_metadata.json | 2 +- examples/example_metadata_point.json | 2 +- format-specs/geoparquet.md | 2 +- format-specs/schema.json | 2 +- 6 files changed, 6 insertions(+), 13 deletions(-) diff --git a/README.md b/README.md index dd310ce..5c4aa6b 100644 --- a/README.md +++ b/README.md @@ -10,13 +10,13 @@ Initial work started in the [geo-arrow-spec](https://github.com/geoarrow/geoarro Arrow work in a compatible way, with this specification focused solely on Parquet. We are in the process of becoming an [OGC](https://ogc.org) official [Standards Working Group](https://portal.ogc.org/files/103450) and are on the path to be a full OGC standard. -**The latest [stable specification](https://geoparquet.org/releases/v1.0.0/) and [JSON schema](https://geoparquet.org/releases/v1.0.0/schema.json) are published at [geoparquet.org/releases/](https://geoparquet.org/releases/).** +**The latest [stable specification](https://geoparquet.org/releases/v1.1.0/) and [JSON schema](https://geoparquet.org/releases/v1.1.0/schema.json) are published at [geoparquet.org/releases/](https://geoparquet.org/releases/).** **The community has agreed on this release, but it is still pending OGC approval.** We are currently working on the process to get it officially OGC approved as soon as possible. The OGC candidate Standard is at [https://docs.ogc.org/DRAFTS/24-013.html](https://docs.ogc.org/DRAFTS/24-013.html). The candidate Standard remains in draft form until it is approved as a Standard by the OGC Membership. Released versions of GeoParquet will not be changed, so if changes are needed for OGC approval, it will be released with a new version number. The 'dev' versions of the spec are available in this repo: -- [**Specification**](format-specs/geoparquet.md) (dev version - not stable, go to the [stable specification](https://geoparquet.org/releases/v1.0.0/) instead) +- [**Specification**](format-specs/geoparquet.md) (dev version - not stable, go to the [stable specification](https://geoparquet.org/releases/v1.1.0/) instead) - [JSON Schema](format-specs/schema.json) - [Examples](examples/) @@ -62,13 +62,6 @@ A quick overview of what GeoParquet supports (or at least plans to support). It should be noted what GeoParquet is less good for. The biggest one is that it is not a good choice for write-heavy interactions. A row-based format will work much better if it is backing a system that is constantly updating the data and adding new data. -## Roadmap - -The goal of 1.0.0 was to establish a baseline of interoperability for geospatial information in Parquet. For 1.0.0 -the only geometry encoding option is Well Known Binary, but there is an option to allow other encodings. The main goal of 1.1.0 will be to incorporate a more columnar-oriented -geometry format, which is currently being worked on as part of the [GeoArrow spec](https://github.com/geoarrow/geoarrow). Once that gets finalized we will add the option to -GeoParquet. In general 1.1.0 will further explore spatial optimization, spatial indices and spatial partitioning to improve performance reading spatial subsets. - ## Versioning As of version 1.0 the specification follows [Semantic Versioning](https://semver.org/), so at that point any breaking change will require the spec to go to 2.0.0. diff --git a/examples/example.parquet b/examples/example.parquet index 7c653bb259012832e65eea60506a4c1984117239..33e4cdcdd6dea981b17ac5a54fa90899e79738ef 100644 GIT binary patch delta 268 zcmeBs$=LUjaY7F>1Dn9a{$n6&a(A@zq%+Wk*FD^03i1J99f~-3b!otL()^!&s!UYzY92g!m**cyRtko(ahDUAP6NKdY zc!+Cxqhcl(CulGlZJv`*%g$K2St`SghuuuiP|rYe&E$d-(aH5CY&q%+Wk*FD^03i1J99f~-3b!otL()^!&s!UYzY92g!m**cyRtko(ahDUAP6NKdY zc!+Cxqhcl(CulGlZl04+%g$J_St`SghuuieK+iyO&E$d-(aH5CY&