Add WCS config w/ correct scaling for NDVI, and fix legends #454
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
ericboucher
reviewed
Apr 18, 2022
| "opacity": 0.7, | ||
| "legend_text": "LEGEND", | ||
| "legend_text": "Normalized Difference Vegetation Index (NDVI) derived from MODIS TERRA/AQUA", | ||
| "legend": [ |
There was a problem hiding this comment.
Should we add an issue to create "standardized/shared" legends and wcs configs?
There was a problem hiding this comment.
@ericboucher - yes! #358
ericboucher
approved these changes
Apr 18, 2022
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.
This PR addresses an error in NDVI configurations where the scale factor was missing which then leads to incorrect analysis results. The screenshots below show the incorrect result without the WCS config, followed by the correct results. The legend labels and legend text have also been corrected in this PR. This applies to all PRISM deployments.