Do not set the collections transform#59
Merged
andrewdnolan merged 1 commit intoE3SM-Project:mainfrom Apr 14, 2026
Merged
Conversation
Collaborator
Author
Testing:
|
Collaborator
Author
Testing:
|
Collaborator
Author
TestingUsing |
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
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.
Not setting the collection transform, for GeoAxes instances, results in ~50% (or more) speed up in rendering. I reached out to the cartopy dev's about whether this was really needed, but have not heard. If we were making an obvious mistake here, I think they would have said something.
Native mesh contouring (#52) also produces matplotlib collections on map projected figures. We do not set the transform there and have not had any issues. So, I'm feeling comfortable moving forward with this (for now at least).
If we get a response or issues arise, we can always revert these changes.
Closes #33.