-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GeoTable.from_arrow doesn't recognize geometry column from PointArray #589
Comments
Thanks for trying it out! I agree having better geometry constructors will be necessary for usability. GeoArrow defines extension metadata that needs to be on an array to declare it a geometry. Your issue is that when you call One way to fix this is to do use the The other way is to register the pyarrow extension types provided in For now, I've put more effort into the IO readers and writers and into the GeoPandas and Shapely interoperability. So a simple way to get a GeoTable is to first create a |
I'm trying to quit doing that ;)
That's what I really needed.
Now, with my
I see that it says my geometry is a Struct but I thought it'd be a |
Yes of course, but baby steps!
GeoArrow allows either FixedSizeList or Struct for coordinate buffers. #578 will allow you more control over interleaved vs separated layout when constructing arrays from raw buffers. We should also add a helper to go back and forth between them when you already have your arrays. |
I started from something like
then tried
but got
I also tried a few things around
ChunkedPointArray.from_arrow_arrays([my_point_array])
but none of it worked.The text was updated successfully, but these errors were encountered: