Include filepaths in raster_calculator mistmatched dimensions error#430
Merged
dcdenu4 merged 1 commit intonatcap:mainfrom Apr 14, 2025
Merged
Conversation
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.
Addresses #288
raster_calculatorissues an error if dimensions of the input rasters don't match. The error message only included the differing dimensions, however, without the associated filepaths. Including filepaths and dimensions will make it easier for a user to debug / fix the offending raster(s).I also noticed we could be making use of the
base_raster_path_band_list, which was already filtered on_is_raster_path_band_formatted, rather than re-running this check against thebase_raster_path_band_const_list.