This seems like a persistent problem that I keep seeing on this forum and I can’t seem to figure it out either.
In order for the preprocessing to be successful, I have to manually download the Elevation File myself - I’m even using GPT now - I would greatly appreciate if there was a solution for this that you could share or if there is something that I should be trying out.
I have followed the RUS Copernicus Tutorials for GPT, but I still get this same issue pop up!
Unfortunately, we rely on the external server which provides the SRTM data.
We know that it is sometimes slow or not responding but this is out of our control.
The best work around this issue is to download it manually and modify the snap.auxdata.properties file in <INSTALL_DIR>\etc according to the download location.
Thanks for the clarification @marpet
The download location looks correct (same as stated in our earlier conversations).
I am still confused however about the external server. The SRTM data seems to always download when using the SNAP GUI, and whenever using snappy/GPT I’ve had to download manually which defeats the point of any automating - would you have any advice on next steps in an aim to automate S1 preprocessing?
I have updated to SNAP v.8 and all the associated updates, but somehow the problem is not fixed and the reason is that, using GPT, it is pointed towards a directory that does not exist.
Therefore the file cannot be downloaded, and this is independently of the file I am processing it seems (in bod characters - if you copy/paste it in a browser, it goes nowhere):
INFO: org.esa.snap.core.dataop.dem.ElevationFile: http retrieving **http://srtm.csi.cgiar.org/wp-content/uploads/files/srtm_5x5/TIFF/**srtm_59_17.zip
I am using UNIX.
However, if I process the same file using the same graph via the GUI (both on my Windows machine with SNAP v.7 or UNIX with SNAP v.8 GUI), it works.
(It does not make sense to me either, I agree).
Is there something that has changed with GPT?