Skip to content

Commit

Permalink
Updates for 0.4.0 release (#105)
Browse files Browse the repository at this point in the history
  • Loading branch information
cholmes authored May 25, 2022
1 parent 2615675 commit 69eec8f
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 6 deletions.
6 changes: 2 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -49,8 +49,7 @@ A quick overview of what geoparquet supports (or at least plans to support).
* **Great at read-heavy analytic workflows** - Columnar formats enable cheap reading of a subset of columns, and Parquet in particular enables efficient filtering
of chunks based on column statistics, so the format will perform well in a variety of modern analytic workflows.
* **Support for data partitioning** - Parquet has a nice ability to partition data into different files for efficiency, and we aim to enable geospatial partitions.
* **Enable spatial indices** - To enable top performance a spatial index is essential. This will be the focus of the
[0.4](https://github.com/opengeospatial/geoparquet/milestone/5) release.
* **Enable spatial indices** - To enable top performance a spatial index is essential. This will be the focus of a future release.

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.
Expand All @@ -61,8 +60,7 @@ Our aim is to get to a 1.0.0 within 'months', not years. The rough plan is:

* 0.1 - Get the basics established, provide a target for implementations to start building against.
* 0.2 / 0.3 - Feedback from implementations, 3D coordinates support, geometry types, crs optional.
* 0.4 - Feedback from implementations, add spatial index.
* 0.x - Several iterations based on feedback from implementations.
* 0.x - Several iterations based on feedback from implementations, spatial index best practices.
* 1.0.0-RC.1 - Aim for this when there are at least 6 implementations that all work interoperably and all feel good about the spec.
* 1.0.0 - Once there are 12(?) implementations in diverse languages we will lock in for 1.0

Expand Down
4 changes: 2 additions & 2 deletions format-specs/geoparquet.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ should be stored in parquet format, including the representation of geometries a

## Version

This is version 0.3.0 of the geoparquet specification.
This is version 0.4.0 of the geoparquet specification.

## Geometry columns

Expand Down Expand Up @@ -44,7 +44,7 @@ but have a default geometry used for geospatial operations.

#### version

Version of the geoparquet spec used, currently 0.3.0
Version of the geoparquet spec used, currently 0.4.0

### Column metadata

Expand Down

0 comments on commit 69eec8f

Please sign in to comment.