Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Separate "native" GeoArrow trait and "serialized" GeoArrow trait #581

Open
kylebarron opened this issue Mar 26, 2024 · 0 comments
Open

Separate "native" GeoArrow trait and "serialized" GeoArrow trait #581

kylebarron opened this issue Mar 26, 2024 · 0 comments

Comments

@kylebarron
Copy link
Member

There's definitely some overlap that doesn't really make sense.

E.g. adding a to_coord_type method onto GeometryArrayTrait doesn't make sense for WKB or for coordinate arrays.

And then maybe we can name the traits NativeArray and SerializedArray, which frees up GeometryArray to be the name of MixedGeometryArray.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kylebarron