I have a mosaic dataset that stores two regional single-band (grayscale) images.
In one of the images, there are areas where the pixel value is zero. I don't want to display these pixels, so I have tried both 1) setting the NoData value of the Mosaic Dataset to 0 (and displaying NoData as transparent), and 2) selecting "Display background value [0] as [transparent]". Both methods properly set the pixels to transparent, but unfortunately, these transparent areas overlap my second image, obscuring it.
I have enabled time on the mosaic dataset, set the default mosaic operator to "FIRST" and configured it to sort in descending order of the time field (i.e., more recent images have higher priority). So, whenever the first regional image (with the transparent areas) is the newest image, it is mosaicked over the second image, which obscures the second image's pixels, even when the higher-priority image's pixels are NoData/transparent.
Does anyone have a suggestion as to how to resolve this? I realize I could clip the first image, but would prefer to avoid that. Is my only other option to configure my mosaic operator/sort order to always prefer the second image, or is there a way to avoid mosaicking transparent pixels?
Thanks,
Jason