search

geoarrow / geoarrow-python

Python implementation of the GeoArrow specification
http://geoarrow.org/geoarrow-python/
Apache License 2.0
59 stars 3 forks source link

Question about a new release #42

Closed RaczeQ closed 4 months ago

RaczeQ commented 9 months ago

Hello,

I was wondering if you could publish a new release of the library in the near future. I'd love to use new functions (especially io from and to geoparquet format) in my python library, but putting a git development url in dependencies isn't really sustainable in the long run 😄

paleolimbot commented 9 months ago

I'm happy to tag + release later this week or next, although be aware that there are still large structural changes that are being discussed (#38) that might require you to do some conditional things based on the version. That said, I don't think that io.read_geoparquet_table() is one of the things that will move or whose behaviour for the wide variety of cases is likely to undergo much evolution.

RaczeQ commented 9 months ago

Yes, I'm aware of this discussion and I'll be following the development of those changes in the future. Thank you for the heads up.

RaczeQ commented 7 months ago

Just as information - since it's not possible to release a library on PyPI with a link to the repository library, I had to lock it to the current newest release and I copied some code with the io module with annotation where it comes from: https://github.com/kraina-ai/quackosm/blob/482e3090dfbefd7fae4374267ad045be0f12465e/quackosm/_geo_arrow_io.py

I'll remove it after the new release of geoarrow-python (or maybe I'll switch to geoarrow-rust-core when it'll have the same IO capabilities regarding GeoParquet files).

kylebarron commented 7 months ago

read_parquet exists, but right now it only accepts local files and is likely to be less stable than the pyarrow version. Cloud file support is planned "soon"

paleolimbot commented 7 months ago

Yes, sorry, I forgot about tagging + pushing another release 😬