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.

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

Merged

Conversation

thomcom
Copy link
Contributor

@thomcom thomcom commented Feb 3, 2023

Description

Upstream changes in 23.04 require that columns have valid_count and has_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

  • I am familiar with the Contributing Guidelines.
  • New or existing tests cover these changes.
  • The documentation is up to date with these changes.

@thomcom thomcom added bug Something isn't working 3 - Ready for Review Ready for review by team non-breaking Non-breaking change labels Feb 3, 2023
@thomcom thomcom requested a review from a team as a code owner February 3, 2023 17:47
@thomcom thomcom self-assigned this Feb 3, 2023
@thomcom thomcom requested a review from vyasr February 3, 2023 17:47
@github-actions github-actions bot added the Python Related to Python code label Feb 3, 2023
@thomcom thomcom requested review from isVoid and removed request for vyasr February 3, 2023 17:47
@thomcom thomcom changed the title Add Add valid_count and has_nulls to GeoColumn Feb 3, 2023
Copy link
Member

@harrism harrism left a 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.

python/cuspatial/cuspatial/core/_column/geocolumn.py Outdated Show resolved Hide resolved
Comment on lines 186 to 187
Null support is implemented in GeoSeries and this is not expected
to ever return less than the length of the GeoColumn. This is
Copy link
Member

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.

Copy link
Contributor Author

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?

@thomcom
Copy link
Contributor Author

thomcom commented Feb 10, 2023

/merge

@rapids-bot rapids-bot bot merged commit 7d18ae0 into rapidsai:branch-23.04 Feb 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3 - Ready for Review Ready for review by team bug Something isn't working non-breaking Non-breaking change Python Related to Python code
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

[BUG]: Printing GeoDataFrame throws errors due to missing null count
3 participants