I ingested a number of BYOC tiles (several thousand files) into a user collection on CODE-DE. Most of them are working perfectly, meaning I can request them through WMS for visualization purposes. Yet, for some of them, I face visualization issues. For instance, It appears to happen that on a tile at a certain sensing date, data from the underlying file is not shown although there is one available in my collection.
The status for all files in my collection is shown as ‘INGESTED’. For test purposes, I re-ingested one file (certain sensing date) I was having issues with manually, which did the trick in the end.
Is that perhaps a known issue? Or is there a way to find out automatically which of the many files don’t work properly?
I think I found the potential issue but don’t know exactly how to solve it.
Neighbouring BYOC tiles have some degree of overlap in my collection due to prior reprojection to EPSG:3857 (original EPSG was 25832). In these overlapping areas, it can happen that actual values from one tile are blocked out from masked values (datamask) located on the neighbouring tile (I guess).
Is there a way to account for such overlaps in the eval. script perhaps? I read something about the ‘mosaicking’ parameter set to ‘tile’. But I don’t know how to implement that in the script in order to select the right tile with actual data.