Am using the Python API to download some S1 (ID: BANDS-S1-IW) and S2 (ID: BANDS-S2-L1C) images. Everything works fine with the S2 download but not the S1 download especially once ortho-rectification is turned on. The following error was reported initially:
This XML file does not appear to have any style information associated with it. The document tree is shown below.
java.util.concurrent.ExecutionException: java.lang.RuntimeException: Could not load necessary digital elevation model for orthorectification! Please try again later or without orthorectification.
Is there a way of going around this problem? If not, is it possible to also download the original metadata (the .dim file from ESA) for each downloaded non-rectified image from the EOCloud in order to perform the ortho-rectification locally using SNAP?
can you send one of the requests failing with this code so that we can look into it?
Not sure if related, but I noticed that you are exceeding daily limit for trial account (10.000 requests per day, see rate limiting section)
To use SNAP you will have to download original data, orthorectify it and then make the data available within your python workflow.
(2) When ortho-rectification is disabled in the configuration, am able to download the images. When I enable the ortho-rectification right after that and re-run the script, am able to down the images without any exception being thrown. The limiting factor here is the number of requests per day, which you say is 10000. Would an upgrade to individual commercial use be of help here?
(3) To use SNAP to ortho-rectify the clipped images downloaded from the EO Browser, I will need to metadata info per ach image. Is there a way of getting this as well from the EO Browser per each download?
Hi once again, so we got a commercial license now and am still having difficulties with the download of the ortho-rectified S1 images. I have been running the script since yesterday. The script is still running but there is NO download or I have not received an error message from the API. Can you please check what is happening? Thanks a lot.
…after further investigation I found a workaround for the issue: my geometry is quite small (below 10x10 m). If I inflate the geometry a bit (greater ~10x10 m) the above exception does not occur.
we found an issue and pushed the fix to the production so there should hopefully not be any more of these types of errors (orthorectification is hard and DEM is not as homogenous as one would hope for, so there might be some other border cases…)