Open EternalDeiwos opened 6 months ago
Good catch! I haven't opened up the pandas integration project for a while and it may be that some of my assumptions when I wrote the initial version are no longer valid! Other than general time constraints, one of the reasons I haven't put much effort into this part of the repo is that GeoPandas is considering allowing a GeoArrow storage type along these lines, and if that's the case, I'd want geoarrow-pyarrow to just return GeoPandas objects.
(In the meantime I should definitely fix though!)
Thanks. As I said I am just playing with it so no pressure from my side if this is going to change substantially in the future.
From my first impression, it is a lot easier to understand at a glance what geoarrow.pandas
is doing under the hood than the equivalent GeoPandas. I hope wherever this lands, that it will be just as easy to directly access the underlying buffers.
I am playing around with the
geoarrow.pandas
integration and found something odd; if I load a data frame containing a geometry column it will successfully load and display the geometry correctly but I am unable able to do anything with it. Anything I try (e.g.df.geometry.geoarrow.*
) produces the following error:I created the file like this:
and I load the file like this