GITC-8325: Properly handle data values outside of colormap range #56
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
jtroberts
approved these changes
Dec 3, 2025
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.
Description
The behavior of the quantization step for palettized PNGs has been modified to properly handle values that lie above or below the defined colormap steps in the color palette. For example, if a colormap defines its lowest color level as 0, negative numbers would be treated as nodata. Now they are treated as the lowest color level, which is the intended behavior. This change also fixes a bug with the way that nodata values were handled during quantization.
Jira Issue ID
GITC-8325
Local Test Steps
Tested with unit tests and running a script to run against a real TEMPO L2 product. Testing against the regression tests is still pending.
PR Acceptance Checklist
CHANGELOG.mdupdated to include high level summary of PR changes.docker/service_version.txtupdated if publishing a release.