Great! thanks a lot @marpet !
The code was the same but made me realized the home_dir retrieved via expanduser method was pointing to a folder that did not contain ‘AppData\Roaming\SNAP’. Perhaps would be helpful to add a warning/error message in such a case…
Thanks again
Thank you mengdahl, I solved the issue with the upgrad to SNAP v8.x 
1 Like
Sorry I’m a little late to the party but was there a fix for the headless option? I’m using snap as part of a pipeline in a docker container so I don’t have a gui to update.
I followed along and did the whole
snap --nosplash --nogui --modules --list --refresh
but it just hangs forever. I noticed someone above said that they killed it after a few min. and the update command worked after but I’ve tried many times between 30 seconds and 8 hours thinking maybe it needed more time and every time after I do that and run
snap --nosplash --nogui --modules --update-all
it still says that there are no updates.
To work around the “hanging”-issue you can use the little script provided here:
Update SNAP from the command line - SNAP - SNAP Wiki (atlassian.net)
It is in the note at the top.
Actually, you do not need to wait long.
The module list should be printed to the console within a few seconds, definitely less than a minute. Depends a bit on the internet connection.
Could it be that the reason that the update process shows that there are no updates, is that you are already up-to-date?
When the list of modules is printed, do you some s1tbx modules with version 8.0.3?
Like: org.esa.s1tbx.s1tbx.op.calibration 8.0.3 Enabled
Then you probably have already the latest version.
Yeah I think I might already have the latest version. It’s odd that I’m still getting the orbit file issue. My coworker was able to update snap on his local machine and it worked but for some reason it’s still not working for me.
Did you make some special configuration in the snap.auxdata.properties file? This might cause issues?
If not, can you post the error message from the log file. or even better the whole log file?
The file is located on Unix, at <user_home>/.snap/var/log/messages.log
Hello all, I have the same issue concerning Orbit file and then I cannot process my S1 images … I downloaded the latest snap version and when i’m also trying to update snap via the command line with : snap --nosplash --nogui --modules --update-all . It just doesn’t recognize the flags… Any idea ?
1 Like
Same here…
Good morning all,
I face similar problem as I am trying to run a chain of time-series sentinel-1 data via snappy and python.
As it is quite urgent has anyone solved the problem related to the connection time out in snappy?? I did try snappy with SNAP-7 and SNAP-8 (latest version).
If yes, please share your solution.
Thanks a million.
Best,
Thanassis
e.g. images have sensing date from 2019 to the end of 2020.
@mengdahl, is SNAP planning an update for orbits retrieval using Scihub (Copernicus Open Data Hub)?
In the STEP server last RESORB orbits are from 25th March… is not going to be updated? Or is it just temporally?
I had the same problem until I realized that /usr/bin/snap is not the snap we installed. For me I had to locate where I installed snap and then execute /home/user/snap/bin/snap (i.e. snap will use /usr/bin/snap, so you need full path-name)
Hi guys
After reading all posts in this thread, I am still really confused.
It would be great if one of the moderators (@ABraun @marpet @mengdahl) of the forum could take some time to summarize the current status, regarding both snap as gui, cli and snappy-api.
I get very inconsistent results comparing the snap gui and snappy.
I updated the software (SNAP gui) to 8.0.3 and orbit correction works now (for test data from 2018 and 2020).
I also checked the file snap.auxdata.properties and everything seems to be updated:
OrbitFiles.sentinel1POEOrbitPath = ${AuxDataPath}/Orbits/Sentinel-1/POEORB
OrbitFiles.sentinel1RESOrbitPath = ${AuxDataPath}/Orbits/Sentinel-1/RESORB
OrbitFiles.sentinel1POEOrbit_remotePath = http://step.esa.int/auxdata/orbits/Sentinel-1/POEORB/
OrbitFiles.sentinel1RESOrbit_remotePath = http://step.esa.int/auxdata/orbits/Sentinel-1/RESORB/
However, when I try snappy I get the following error:
RuntimeError: org.esa.snap.core.gpf.OperatorException: No valid orbit file found for 29-DEC-2020 16:58:40.620691
Orbit files may be downloaded from https://qc.sentinel1.eo.esa.int/ or http://aux.sentinel1.eo.esa.int/
and placed in C:\Users\florian.beyer\.snap\auxdata\Orbits\Sentinel-1\POEORB\S1B\2020\12
So, why snappy is not looking for the orbit files at the new location??? Is there a file in the snappy package, that I have to change manually to the right website?
Or do I have to apply snappy-conf.bat again, after updating SNAP?
Hi Florian,
The error message
Orbit files may be downloaded from https://qc.sentinel1.eo.esa.int/ or http://aux.sentinel1.eo.esa.int/" is outdated.
@lveci can you update this?
I think also with snappy the correct repository is used. Otherwise you would get a different error.
But looking at Index of /auxdata/orbits/Sentinel-1/RESORB/S1B/2020/12 (esa.int) I see that there is no orbit file close to the time you are searching for. There seem to be gap. I’m not familiar with the orbit files. maybe this is okay. maybe a orbit file is missing
I actually don’t see a gap (or missing files), when I look at:
http://step.esa.int/auxdata/orbits/Sentinel-1/POEORB/S1A/2020/12/
There are files for every day…
According to the error message, snappy is checking the wrong websites, right? No matter, which date I try…
---------------------------------------------------------------------------
RuntimeError Traceback (most recent call last)
<ipython-input-21-f5ec346988b3> in <module>()
4 parameters.put('Apply-Orbit-File', True)
5 # apply_orbit = snappy.GPF.createProduct('Apply-Orbit-File', parameters, subset)
----> 6 apply_orbit = snappy.GPF.createProduct('Apply-Orbit-File', parameters, s1_read)
7 print(colored('Orbit updated succesfully', 'green'))
8
RuntimeError: org.esa.snap.core.gpf.OperatorException: No valid orbit file found for 26-DEC-2020 05:23:47.499596
Orbit files may be downloaded from https://qc.sentinel1.eo.esa.int/ or http://aux.sentinel1.eo.esa.int/
and placed in C:\Users\florian.beyer\.snap\auxdata\Orbits\Sentinel-1\POEORB\S1B\2020\12The error message is just wrong. It does not consider which repository are actually used.
Yes, there are orbits for every day but I think the between 15 and 17 is to long. But this is just a guess. Maybe it is correct.
The same product works in the GUI?
yes, same product is working well in the gui…
Maybe you have an issue similar to the one @CorradoMotta had:
According to his reply it is now working with snappy.
Has someone else an idea?
I already checked that. Everything is fine with the code and the location of that SNAP folder.
I am facing the same problem Orbit file not available error . I am working in HPC where GUI is not an option it is either command line or snappy. I think there is a problem with the integration of snappy with latest sentinel toolbox (which is already upgraded to the latest version)
On my case I don’t think it’s related to my snap location but more in a connection problem with the orbits : i’m using snappy on a server and when it reach the “Apply orbit” processing i got this message :
Exception calling QC Rest API: Connect to qc.sentinel1.eo.esa.int:443 [qc.sentinel1.eo.esa.int/131.176.235.71] failed: Connection timed out (Connection timed out)
WARNING: org.esa.s1tbx.sar.gpf.orbits.ApplyOrbitFileOp: Connect to qc.sentinel1.eo.esa.int:443 [qc.sentinel1.eo.esa.int/131.176.235.71] failed: Connection timed out (Connection timed out)
Exception calling QC Rest API: Connect to qc.sentinel1.eo.esa.int:443 [qc.sentinel1.eo.esa.int/131.176.235.71] failed: Connection timed out (Connection timed out)
WARNING: org.esa.s1tbx.sar.gpf.orbits.ApplyOrbitFileOp: ApplyOrbit ignoring error and continuing: org.apache.http.conn.HttpHostConnectException: Connect to qc.sentinel1.eo.esa.int:443 [qc.sentinel1.eo.esa.int/131.176.235.71] failed: Connection timed out (Connection timed out)
Then it ignores it as set up in the parameters but when it reachs the “Terrain correction” processing it retrieve a Null object :
RuntimeError: org.esa.snap.core.gpf.OperatorException: org.esa.snap.core.gpf.OperatorException due to java.lang.NullPointerException
So I decided to try on the GUI on my laptop with latest version as on the server and when i’m trying to apply an orbit file it just doesn’t work so in my opinion it’s all related to the orbit files.
I know that it’s already things that were said in this thread so I don’t think that my comment is really helping…
But if any one has an option to help that would be great as my work is based on S1 products i’m totally stuck right now …
1 Like