BUG: explode() fails if 'level_1' is in columns #1445
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
martinfleis
commented
May 24, 2020
Comment on lines
+679
to
+680
| if not PANDAS_GE_024: | ||
| expected_df = expected_df[["level_1", "geometry"]] |
There was a problem hiding this comment.
There's some strange behaviour for old pandas, switching the order of columns, so I am switching it back.
jorisvandenbossche
approved these changes
May 27, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #1393
If there is a column
'level_1'present in GeoDataFrame, it will fail withNotImplementedError. We are using automatically createdlevel_1column within explode, so I am renaming potentially conflicting column to'__level_1'and then back.