-
Notifications
You must be signed in to change notification settings - Fork 154
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
[FEA] Use cudf List types for polygon and polyline geometry #261
Comments
This issue has been marked rotten due to no recent activity in the past 90d. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. |
This issue has been marked stale due to no recent activity in the past 30d. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be marked rotten if there is no activity in the next 60d. |
This should be possible now that we have list and struct types in cuDF. |
This issue has been labeled |
This issue has been labeled |
…on` (#862) This PR adds column/python API for `pairwise_linestring_intersection`. Closes #648 This PR is also the first attempt of #261 , establishing `geometry_column_view` that inherits `cudf::column` and adds additional information to identify the underlying nested levels. Note that it cannot directly inherit from `cudf::lists::list_column_view`, because a point array isn't a `List<T>` array. Also note that the type codes defined in libcuspatial and cuspatial-python may be different, so there is a type code mapping after computing the result from libcuspaital. Finally, since `List<Union>` is currently unsupported in libcudf, the python API returns the geometries in two parts: `offset + GeoColumn`. Authors: - Michael Wang (https://github.com/isVoid) Approvers: - H. Thomson Comer (https://github.com/thomcom) - Mark Harris (https://github.com/harrism) URL: #862
Is your feature request related to a problem? Please describe.
With the addition of List and Struct types in cuDF, we can update cuSpatial's polygon and polyline geometry representations to use nested "list of lists of point structures".
Describe the solution you'd like
The logical structure of a list of polygons looks like this:
We can represent these data in the same 4 buffers we use today (
poly_offsets
,ring_offsets
,points_x
,points_y
) with the following Arrow types:Additional context
geoarrow/geoarrow#3
geoarrow/geoarrow#4
The text was updated successfully, but these errors were encountered: