WCS TRANSPARENT+GEOMETRY parameters stopped working?

We use WCS requests to download images using the GEOMETRY parameter to cut out invalid pixels from our AOIs and TRANSPARENT=true. By doing this, we get images with an Alpha channel with values 0 outside the GEOMETRY and 1 inside it.

Don’t know exactly when it began, but trying to request images today, we got black backgrounds outside the GEOMETRY and after analyzing the images, they had no Alpha channel, this occurred for every layer we tried (TRUE_COLOR, NDVI [GREYSCALE], NDVI, EVI, etc).

Nothing has changed in our layers configuration nor ir the requests we made, except for date, but even trying with old images we already downloaded and were ok this issue ocurred.

Ex: (request bellow image)

http://services.sentinel-hub.com/v1/wms/INSTANCE_ID?service=WMS&geometry=POLYGON+((-53.307853+-24.572338%2C+-53.305578+-24.574095%2C+-53.306522+-24.575422%2C+-53.307509+-24.578427%2C+-53.308368+-24.578856%2C+-53.312402+-24.577022%2C+-53.307853+-24.572338))&time=2020-04-16T00%3A00%3A00&request=GetMap&quality=100&priority=mostRecent&height=1000&TRANSPARENT=true&styles=GRAYSCALE&srs=epsg%3A4326&width=1046&showLogo=false&maxcc=20.0&version=1.1.1&format=image%2Fpng&crs=epsg%3A4326&layers=EVI

Can you provide first few blocks of the INSTANCE_ID, so that we can replicate the request in our environment?
There were some updates done on the “data mask” side, but I believe they should be backwards compatible. Still, do take a look in this examples if it helps somehow:
https://docs.sentinel-hub.com/api/latest/#/API/data_access?id=example-2-use-values-in-datamask-as-the-transparency-band

Hi @lucianoalberti,

we have identified the issue. It is indeed related to the data mask implementation as stated in the document I mentioned before.

The workaround is pretty simple - to adjust evalscript to handle transparency. I have now changed this on your account.

I apologise for inconvenience.

Best,
Grega

Hello @gmilcinski,

sorry but how we used one of the pre-configured layer schemas, we don’t really know much about the evalscripts, so thanks for changing it in my account! :grinning:

Best, Luciano

@gmilcinski sorry but I just realized that using any of the Base Products is keeping the black borders, in the case only EVI has been corrected, the only way to solve this is by editing the scritps for the rest of the layers I use with the data mask implementation?

If you let me know, which layers you are using (and which style), we can do this conversion for you.

Alternatively you can find the “simple version” version of the Custom script in our repository and do it yourself:

Since I don’t feel very comfortable on editing the the Scripts, I would really appreciate if you could do that

The Layers/Styles are:

  • TRUE_COLOR (default style)
  • NDVI (default style, greyscale)
  • MOISTURE_INDEX (default)
  • SAVI (greyscale)
  • LAI_SAVI (default)
  • EVI (greyscale)
  • CHL_RED_EDGE (dafault)

I believe we have configured all these layers.
Could you please double check if it works as expected?

As a side note - can you perhaps replace your API calls from
http://services.sentinel-hub.com/v1/wms
to
https://services.sentinel-hub.com/ogc/wms

The end-point you are using is deprecated for more than 3 years. It’s still working, as we are trying hard to remain backward compatible, but we would appreciate if you could update.
There should be no changes on your side.

Yes, they are all working, thanks for the help!

Sure, we will be updating it as soon as we can