Hello, we recently started having issues with this link format and tried to find some information as to why it may not be working suddenly but so far have not been able to find anything that would suggest the sudden break.
the problem is that the requested image is too big. If I try the same request with a smaller bbox (or with coarser resolution as you did it), it works, e.g.: https://services.sentinel-hub.com/ogc/wms/?service=WMS&request=GetMap&layers=TRUE_COLOR_PREVIEW&version=1.1.1&name=Sentinel-2%20L1C&=&maxcc=100&time=2020-10-01/2020-10-11&bbox=2139372,5246857,2149372,5256857&crs=EPSG:3857&resX=10m&resy=10m
(I also removed repeated dates.)
The error message you are getting is not helpful at all. We do have validations for requesting too big image size and would usually return a nice error message for such examples. We will check why/how your request manages to get around these validations. Thank you for reporting.
@avrecko - Thankyou for the quick reply and the tidy up of the request.
I could not find anything regarding size vs res in the docs? I am new to satellite imagery so still feeling my way around how it works.
I did some testing with various sizes and res and was able to get an error message at time but wondering if their is some best practise or size limit cut off for each res?
in Sentinel Hub you can request images up to 2500 x 2500 pixels (the limitation applies to each dimension separately).
You can control the size of the image you are requesting by specifying:
WIDTH and HEIGHT parameters in your request. Until you keep both values under or equal to 2500 the request should work. Using this option, you do not have control over the requested spatial resolution.
RESX and RESY parameters in your request. Using this option you directly control the spatial resolution of the image but the image size is calculated automatically by dividing the requested bbox with RESX and RESY (each bbox’s dimension respectivly). It is sometimes not straight forward to “see” what the requested image size would be looking only at BBOX and RESX/Y. One approach for such cases is to try to request coarser spatial resolution (if your application/usage of the satellite data alows this) or a smaller bbox.