Avoid GeoAttrsError by using more robust target extent calculation#3572
Merged
pomadchin merged 2 commits intolocationtech:masterfrom Apr 17, 2025
Merged
Avoid GeoAttrsError by using more robust target extent calculation#3572pomadchin merged 2 commits intolocationtech:masterfrom
pomadchin merged 2 commits intolocationtech:masterfrom
Conversation
pomadchin
changed the title
… case a LayoutDefinition is available locationtech#3559
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
2 participants
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.
A cleaned up version of #3560
Closes #3559
Closes #3560
All credits to @jdries!