You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for all of your work on this package. We are really stoked to start using it! I was wondering if the package currently has the ability to read/write GeoParquet format. I have been able to read/write parquet files with a geometry from arrow/geoarrow, but on read it seems to ignore the geoparquet metadata, and it doesn't write it when passed to arrow::write_parquet(). Is this the expected behavior and will the GeoParquet spec expected to be supported at some point? This is a feature we are very interested in, and I am very happy to help contribute in any way I can. Please reach out if I can help in anyway. Thanks again for making this package - It is something we've been hoping for for a while!
Cheers,
Brayden
The text was updated successfully, but these errors were encountered:
Thanks so much for your hard work here! Has there been any progress on this? Our data stack requires specifically GeoParquet, and would love to use your package, but at the moment the files geoarrow produces seem to be parquet-storing-geography-as-a-record.
Hi Dewey,
Thanks for all of your work on this package. We are really stoked to start using it! I was wondering if the package currently has the ability to read/write GeoParquet format. I have been able to read/write parquet files with a geometry from arrow/geoarrow, but on read it seems to ignore the geoparquet metadata, and it doesn't write it when passed to arrow::write_parquet(). Is this the expected behavior and will the GeoParquet spec expected to be supported at some point? This is a feature we are very interested in, and I am very happy to help contribute in any way I can. Please reach out if I can help in anyway. Thanks again for making this package - It is something we've been hoping for for a while!
Cheers,
Brayden
The text was updated successfully, but these errors were encountered: