v1.0.0-beta.1
Pre-releaseWe're getting close to the first stable GeoParquet release! We may have one or two more beta releases after gathering feedback from implementors, but we don't have any other planned breaking changes before 1.0.0. Please give it a try and create issues with your feedback.
The 1.0.0-beta.1 release includes a number of metadata changes since the previous 0.4.0 release. One breaking change is that the previous geometry_type
metadata property is now named geometry_types
. The value is always an array of string geometry types (instead of sometimes a single string and sometimes an array). In addition, we've clarified a number of things in the specification and tightened up the JSON schema to improve validation. See below for a complete list of changes.
What's Changed
- Add GeoParquet.jl, an implementation in Julia by @evetion in #109
- add R examples and geoarrow by @yeelauren in #108
- fix lint error by @kylebarron in #125
- Include suggestion about feature identifiers by @tschaub in #121
- Consistent spelling of GeoParquet by @tschaub in #142
- Add link to gpq by @tschaub in #139
- Correct the 'bbox' description for 3D geometries by @jorisvandenbossche in #88
- Clarify nesting and repetition of geometry columns by @tschaub in #138
- Clarify that bbox follows column's CRS by @jorisvandenbossche in #143
- Clarify geographic vs non-geographic bbox values by @tschaub in #145
- Array of geometry types by @tschaub in #140
- More consistent spelling and punctuation for JSON types by @tschaub in #149
- Add Apache Sedona to known libraries by @jiayuasu in #150
- schema.json: update reference to projjson schema to v0.5 by @rouault in #151
- Require minimum length of 1 for primary_geometry #129 by @m-mohr in #153
- Clean-up spec and JSON Schema by @m-mohr in #131
- Clean-up README by @m-mohr in #156
- The default value of the crs field is required #152 by @m-mohr in #154
- Require at least one column by @m-mohr in #158
- Add basic valid and invalid tests for the json schema by @jorisvandenbossche in #141
- Refer to RFC 2119 for definition of requirement levels by @tschaub in #160
- Read version number from the schema by @tschaub in #159
New Contributors
- @evetion made their first contribution in #109
- @yeelauren made their first contribution in #108
- @tschaub made their first contribution in #121
- @jiayuasu made their first contribution in #150
- @m-mohr made their first contribution in #153
Full Changelog: v0.4.0...v1.0.0-beta.1