rust-v0.4.0-geoparquet
This is the tag for the v0.4 release of the geoparquet
crate, which was delayed compared to the 0.4 release of the other crates.
0.4.0 (geoparquet
crate) - 2025-07-08
New standalone geoparquet
crate!
New Features 🪄
- GeoParquet reader refactor to avoid making duplicate wrappers of upstream structs #1089
-
Removes wrapper structs for builders. So we no longer have a
GeoParquetRecordBatchReaderBuilder
or aGeoParquetRecordBatchStreamBuilder
. Users will use upstreamparquet
sync/asyncBuilder
structs directly. Means a significantly lower maintenance overhead here, and we don't need to do anything to support new upstream functionality. -
Adds
GeoParquetReaderBuilder
trait that extends the upstreamArrowReaderBuilder
. This allows users to implement a spatialRowFilter
directly on an upstream builder instance. It also allows low-level access, so that if a user wanted a spatial filter plus something else, that would be doable. -
Allows user to choose when the WKB column should be parsed to a native GeoArrow type or not in the
geoarrow_schema
method. (theparse_to_native
parameter) -
Keeps wrapper structs for readers. So we still have a
GeoParquetRecordBatchReader
and aGeoParquetRecordBatchStream
, but these are very lightweight wrappers.The benefit of having these wrapper structs is that we can ensure GeoArrow metadata is always applied onto the emitted
RecordBatch
es.
-
- Refactor of GeoParquetReaderMetadata and GeoParquetDatasetMetadata #1172
- Remove
Option
for the geospatial metadata of eachGeoParquetReaderMetadata
andGeoParquetDatasetMetadata
. We assume that if the user is using thegeoparquet
crate, all files will have valid GeoParquet metadata.
- Remove
- Remove GeoParquet writer wrappers and just expose encoder #1214
- Add support for writing covering column to GeoParquet #1216
- Add support for generating the a bounding box covering column while writing data.
- Reconfigure writer properties generation. This takes inspiration from the upstream
parquet
properties generation, and has both column specific properties and default properties. So you can set the encoding for all columns but you can also override the encodings for specific columns.
- Allow passing primary column to parquet writer #1159
- Correctly set geometry types in GeoParquet metadata when writing #1218