-
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
Add valid_count
and has_nulls
to GeoColumn
#894
Add valid_count
and has_nulls
to GeoColumn
#894
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wondering if you are overdocumenting.
Null support is implemented in GeoSeries and this is not expected | ||
to ever return less than the length of the GeoColumn. This is |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we really want to document this expectation in this way? Might cause a user to make assumptions or rely on this expectation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I modified the docs, take another look?
/merge |
Description
Upstream changes in 23.04 require that columns have
valid_count
andhas_nulls
. cuSpatial doesn't explicitly support nulls yet, but this PR handles the missing methods so that cudf does not produce messy error messages when one attempts to print a dataframe.Closes #886
As there are no tests for geocolumn and it does not support nulls, tests have not been added for these interface methods at this time.
Checklist