Fix rasterMetrics bugs #267
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
twelch
added a commit
that referenced
this pull request
Jun 25, 2024
* fix rasterMetrics individual sketch bug * update lockfiles * bug: support case where geoblaze throws if no valid overlapping pixels found
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.
Solves for a use case where Geoblaze throws if no valid pixels found overlapping with a polygon. Solution: initialize array of default values, one for each expected band in the raster.
Resolves a bug for sketch collection use case where individual sketch stats were overlaying the entire collection every time, not calculating stats for it's individual sketch. The result was every individual sketch had a metric value matching the collection level.