Fix classification output mismatch between preview and final raster #429
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
1 participant
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.
Hello,
I am currently working on my diploma thesis titled “Expansion of the Semi-Automatic Classification Plugin with the ability to remove outliers from the training input.” One of the tasks was to identify and fix a bug in the Semi-Automatic Classification Plugin.
During the classification process, the generated output raster was incorrect, while the Classification Preview tool provided by SCP produced correct results.
After analyzing the classification workflow in the source code, I found that in the raster generation method the bandset object had a different value compared to the one used during Classification Preview, which caused incorrect raster generation.
This pull request fixes the issue by correcting the way the bandset is copied and passed during raster generation, ensuring that the final classification raster matches the preview result.
This behavior appears to be the same issue described in issue #420 , where the classification preview works correctly but the final output raster differs from the preview.