CHANGELOG: clarify polygonize transform auto-detection covers all return types#2550
Merged
Conversation
The PR description for #2541 notes that the auto-detected transform is applied inside `_scan`, so every return_type (numpy, awkward, geopandas, spatialpandas, geojson) benefits. The CHANGELOG entry only mentioned return_type='geopandas', which understates the fix scope.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Follow-up to PR #2541 (closes #2536). The CHANGELOG entry only mentioned
polygonize(return_type='geopandas'), but the PR description and the implementation are broader: the auto-detected transform is applied inside_scan, so everyreturn_typeoption (numpy,awkward,geopandas,spatialpandas,geojson) benefits.This PR rewords the entry to match the PR description and the code, without changing any behaviour.
Test plan