Orbit file timeout (March 2021)

You are purposefully using a time-window of zero length?

It is not a timewindow of zero length, unless I misunderstood something. It is selecting orbit data with a start datetime that is less than or equal, and an end datetime that is greater than or equal then searched datetime. That should give me the orbit file(s) that have a valid datetime range (between ContentDate/Start and ContentDate/End) for this datetime, not? Or is there a better way to select the orbit files that are valid for a certain scene datetime?

Hi @lveci - @marpet,

Updating SNAP solved the problem with the timeout connection on SNAP toolbox. However python snappy continues to give the same exception. I guess it is still using the original source. Is there something i need to do to reflect the SNAP update changes into snappy package?

thanks

Hello to everyone,

Is there a way to solve this issue with an older version of SNAP? I’m currently using SNAP v6, via gpt. I tried to update via command line, as suggested by Marpet, but it didn’t work.

Having a look at snap/etc/snap.auxdata.properties the remote path for POE and RES is http://step.esa.int/auxdata/orbits, that is reachable, but SNAP keeps in trying to download them from qc.sentinel1.eo.esa.int, failing.

Is there a way to force SNAP v6.0 in downloading orbit files from the proper repository and avoiding qc.sentinel1.eo.esa.int? Or shall I update SNAP to v8.0?

Thank you!

You should update - a large number of bugfixes and improvements have taken place since 6.

1 Like

Actually, snappy should use the same modules updates as SNAP does.

There was an issue with loading module updates, but this has been resolved:
[SNAP-929] Modules not loaded when snappy is not started from the system drive - JIRA (atlassian.net)

Maybe you have some old snappy code?
You could check and compare the code shown in the following post with yours:


You find the __init__.py in the snappy folder. Where it is located, depends on your installation settings.

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 :slight_smile:

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

@marpet

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\12