OPERA_L3_DIST-ANN-HLS_Color_Index draws VEG-DIST-STATUS 9 and 10, but its colormap omits them

[dschuck]

The GIBS colormap for the OPERA_L3_DIST-ANN-HLS_Color_Index layer (https://gibs.earthdata.nasa.gov/colormaps/v1.3/OPERA_Vegetation_Disturbance_Annual.xml) lists VEG-DIST-STATUS values 0, 3, 6, 7, 8, and 255.

Table 4-2 of the OPERA DIST HLS Product Specification V1 (https://lpdaac.usgs.gov/documents/1766/OPERA_DIST_HLS_Product_Specification_V1.pdf) also defines values 9 ("confirmed previous year <50%") and 10 ("confirmed previous year >=50%") for DIST-ANN, and the layer's tiles draw them. The tiles are palette PNGs whose index is the class value, and their embedded palette maps index 9 to #333333 and index 10 to #444444, for example in https://gibs.earthdata.nasa.gov/wmts/epsg3857/best/OPERA_L3_DIST-ANN-HLS_Color_Index/default/2025-01-01/GoogleMapsCompatible_Level12/12/1581/655.png. Comparing tiles with the source data over a San Francisco Bay Area region confirms that pixels of value 9 and 10 are drawn in those colors.

Neither color appears in the colormap or legend, so a client building its legend from the colormap cannot identify those pixels, and they are hard to distinguish from value 0 (#121212).

Could values 9 and 10 be added to the colormap and legend, with the colors the tiles already use?

[LP DAAC - dgolon]

Hello @dschuck Thanks for posting. We are looking into this. We will follow up when we have an answer. -- Danielle

[dschuck]

Hello @dschuck Thanks for posting. We are looking into this. We will follow up when we have an answer. -- Danielle

Hi Danielle. Just checking in to see if you've uncovered anything regarding the missing values.

[LP DAAC - dgolon]

@dschuck Apologies for the delay. We are still waiting for a response, the contact was on vacation, but we should have it here shortly in the next day or two. We'll post as soon as we know more. Thanks -- Danielle