Fix _recombine_columns when either geocolumn or non-geocolumn was empty #1438
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
closes #1437
When
GeoDataFrame._split_out_geometry_columns
is called, there may be no geometry columns to split out into 2 DataFrames; therefore, onceGeoDataFrame._recombine_columns
, it assumed the 2 DataFrames were always non-empty. Added a check to bypass this validation if either was empty.I ran the
ZipCodes_Stops_PiP_cuSpatial
notebook locally and the (non-commented) cells no longer raise an exception.Checklist