geoarrow 0.4.0 release missing on crates.io

[wichert]

All the new crates such as geoarrow-array, geoarrow-schema are available on crates.io with their v0.4.0 release, but the geoarrow crate itself only has v0.3.0 and a couple of beta release for 0.4.0. Can you please upload the 0.4.0 release for geoarray itself as well? That will help use of geoarrow on current Rust releases; v0.3.0 is missing the fix for #716.

[kylebarron]

As explained in the README, the geoarrow crate is deprecated. There won't be a v0.4 release in the same form as the v0.3 release.

There will some time be a new release of geoarrow that serves as an "amalgam" crate, which literally just re-exports items from the underlying constituent crates (geoarrow-array, geoarrow-schema, etc).

This is exactly the same as how the upstream arrow-* crates are laid out, and how arrow just re-exports data from all the arrow-* crates.

I agree the churn is unfortunate, but the current state of the geoarrow-rs repo is orders of magnitude more stable and ready to build on going forward than geoarrow v0.3. But yes, you'll need to rewrite your code to use the new APIs exported from the geoarrow-* crates.

[wichert]

Hi @kylebarron . Thanks for the quick response. I was looking for the replacement of geoarrow::io::parquet. I missed geoparquet since it has a different prefix. I do see however that that is also missing a v0.4.0 release on crates.io. Would it be possible to get a non-beta release of geoparquet?

[kylebarron]

Yes, I hadn't published geoparquet v0.4 yet because I was planning to refactor the writer API still. I'll take a look at it this afternoon and decide whether to publish a v0.4 as-is or whether the refactor would be small enough.

In essence we're trying to reduce the amount of duplication that we have in our own code, preferring to only have "add-in" APIs that work directly with the upstream parquet APIs. We already do that on the read side #1089, #1172, but haven't edited it for the write side yet.

[kylebarron]

I think geoparquet 0.4 should get published on Monday, after merging #1216 and potentially fixing #1217