Changes to prepare release 0.2.0 (#71)

Co-authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com>

README.md

@@ -8,8 +8,7 @@ lines, polygons) in [Apache Parquet](https://parquet.apache.org/), a popular col
 geospatial data is represented in Parquet to further geospatial interoperability among tools using Parquet today, and hopefully 
 help push forward what's possible with 'cloud-native geospatial' workflows. 
 
-**Warning:** This is not (yet) a stable specification that can be relied upon. The initial 0.1 release was made to gather
-wider feedback, and we anticipate that some things may change. For now we reserve the right to make changes in backwards incompatible 
+**Warning:** This is not (yet) a stable specification that can be relied upon. All 0.X releases are made to gather wider feedback, and we anticipate that some things may change. For now we reserve the right to make changes in backwards incompatible 
 ways (though will try not to), see the [versioning](#versioning) section below for more info. If you are excited about the potential 
 please collaborate with us by building implementations, sounding in on the issues and contributing PR's!
 
@@ -61,7 +60,8 @@ will work much better if it is backing a system that is constantly updating the
 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 - Feedback from implementations, add spatial index and potentially 3D coordinates.
+* 0.2 - Feedback from implementations, 3D coordinates support.
+* 0.3 - Feedback from implementations, add spatial index.
 * 0.x - Several iterations based on feedback from implementations.
 * 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

examples/example.py

@@ -1,5 +1,12 @@
 """
 Generates `example.parquet` using pyarrow by running `python example.py`.
+
+You can print the metadata with:
+
+.. code-block:: python
+
+   >>> import json, pprint, pyarrow.parquet as pq
+   >>> pprint.pprint(json.loads(pq.read_schema("example.parquet").metadata[b"geo"]))
 """
 import json
 import pathlib
@@ -17,7 +24,7 @@
 
 
 metadata = {
-    "version": "0.1.0",
+    "version": "0.2.0",
     "primary_column": "geometry",
     "columns": {
         "geometry": {

examples/example_metadata.json

@@ -18,6 +18,6 @@
       }
     },
     "primary_column": "geometry",
-    "version": "0.1.0"
+    "version": "0.2.0"
   }
 }

format-specs/geoparquet.md

@@ -7,7 +7,7 @@ should be stored in parquet format, including the representation of geometries a
 
 ## Version
 
-This is version 0.1.0 of the geoparquet specification.
+This is version 0.2.0 of the geoparquet specification.
 
 ## Geometry columns
 
@@ -44,7 +44,7 @@ but have a default geometry used for geospatial operations.
 
 #### version
 
-Version of the geoparquet spec used, currently 0.1.0
+Version of the geoparquet spec used, currently 0.2.0
 
 ### Column metadata
 

validator/python/geoparquet_validator/schema.json

@@ -6,7 +6,7 @@
   "properties": {
     "version": {
       "type": "string",
-      "pattern": "^0\\.1\\.[0-9]+$",
+      "pattern": "^0\\.2\\.[0-9]+$",
       "description": "The version of the geoparquet metadata standard used when writing."
     },
     "primary_column": {