Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

global extent calculation prioritizes weak_spatial_extent over spatial_extent #358

Closed
JeroenVerstraelen opened this issue Jan 30, 2025 · 0 comments · Fixed by #359
Closed
Assignees

Comments

@JeroenVerstraelen
Copy link
Contributor

JeroenVerstraelen commented Jan 30, 2025

extent = constraint["weak_spatial_extent"]

The order should be inverted, similar to how it is done when calculating the spatial_extent during the dry_run:

constraints["spatial_extent"] = constraints["weak_spatial_extent"]

@JeroenVerstraelen JeroenVerstraelen self-assigned this Jan 30, 2025
JeroenVerstraelen added a commit that referenced this issue Jan 30, 2025

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
JeroenVerstraelen added a commit that referenced this issue Feb 9, 2025

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
JeroenVerstraelen added a commit that referenced this issue Feb 25, 2025

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
JeroenVerstraelen added a commit that referenced this issue Feb 25, 2025

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
…ioritizes-weak_spatial_extent-over-spatial_extent

fix extent order when calculating global_extent #358
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant