2025 - Orbit files missing

Hello everyone,

I am using the GPT command-line tool in SNAP (version 11.0.1) with the Microwave Toolbox (version 11.0.0) to preprocess Sentinel-1 data from the this year. However, during the Apply Orbit File step, I receive the following error since 1st Jan 2025:

No valid orbit file found …

I also noticed that there is no corresponding 2025 folder under: Index of /auxdata/orbits/Sentinel-1/RESORB/S1A/.

Any help would be greatly appreciated.

Thank you in advance for your help!

2 Likes

I have also experienced the problem. I tried both SNAP 9.0 with updates and SNAP 11.0 with updates.

It happens for both:
-PorbitType "Sentinel Restituted (Auto Download)"
and
-PorbitType "Sentinel Precise (Auto Download)"

The issue is a blocker for me for processing fresh S1 imagery.

I noticed that files from 2025 seem to be ending up in the 2024/12 directory (https ://step.esa.int/auxdata/orbits/Sentinel-1/POEORB/S1A/2024/12/), so it might be a problem with the script that synchronizes the orbit files to SNAP site.

Below SNAP traceback

WARNING: eu.esa.sar.orbits.io.sentinel1.OrbitFileScraper: Unable to connect to http://step.esa.int/auxdata/orbits/Sentinel-1/RESORB/S1A/2025/01/: HTTP error fetching URL. Status=404, URL=[http://step.esa.int/auxdata/orbits/Sentinel-1/RESORB/S1A/2025/01/]
WARNING: eu.esa.sar.orbits.gpf.ApplyOrbitFileOp: RESORB files are no longer available from Copernicus Dataspaces
WARNING: eu.esa.sar.orbits.io.sentinel1.OrbitFileScraper: Unable to connect to http://step.esa.int/auxdata/orbits/Sentinel-1/POEORB/S1A/2025/01/: HTTP error fetching URL. Status=404, URL=[http://step.esa.int/auxdata/orbits/Sentinel-1/POEORB/S1A/2025/01/]
RESORB files are no longer available from Copernicus Dataspaces
org.esa.snap.core.gpf.OperatorException: RESORB files are no longer available from Copernicus Dataspaces
        at org.esa.snap.engine_utilities.gpf.OperatorUtils.catchOperatorException(OperatorUtils.java:434)
        at eu.esa.sar.orbits.gpf.ApplyOrbitFileOp.initialize(ApplyOrbitFileOp.java:215)
        at org.esa.snap.core.gpf.internal.OperatorContext.initializeOperator(OperatorContext.java:528)
        at org.esa.snap.core.gpf.internal.OperatorContext.getTargetProduct(OperatorContext.java:298)
        at org.esa.snap.core.gpf.Operator.getTargetProduct(Operator.java:359)
        at org.esa.snap.core.gpf.main.CommandLineTool.runOperator(CommandLineTool.java:306)
        at org.esa.snap.core.gpf.main.CommandLineTool.runGraphOrOperator(CommandLineTool.java:284)
        at org.esa.snap.core.gpf.main.CommandLineTool.run(CommandLineTool.java:188)
        at org.esa.snap.core.gpf.main.CommandLineTool.run(CommandLineTool.java:121)
        at org.esa.snap.core.gpf.main.GPT.run(GPT.java:60)
        at org.esa.snap.core.gpf.main.GPT.main(GPT.java:37)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:566)
        at org.esa.snap.runtime.Launcher.lambda$run$0(Launcher.java:55)
        at org.esa.snap.runtime.Engine.runClientCode(Engine.java:189)
        at org.esa.snap.runtime.Launcher.run(Launcher.java:51)
        at org.esa.snap.runtime.Launcher.main(Launcher.java:31)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:566)
        at com.exe4j.runtime.LauncherEngine.launch(LauncherEngine.java:84)
        at com.install4j.runtime.launcher.UnixLauncher.start(UnixLauncher.java:71)
        at install4j.org.esa.snap.runtime.Launcher_gpt.main(Unknown Source)
Caused by: java.io.IOException: RESORB files are no longer available from Copernicus Dataspaces
        at eu.esa.sar.orbits.io.sentinel1.SentinelPODOrbitFile.retrieveOrbitFile(SentinelPODOrbitFile.java:106)
        at eu.esa.sar.orbits.gpf.ApplyOrbitFileOp.updateOrbits(ApplyOrbitFileOp.java:269)
        at eu.esa.sar.orbits.gpf.ApplyOrbitFileOp.initialize(ApplyOrbitFileOp.java:203)
        ... 24 more

Error: RESORB files are no longer available from Copernicus Dataspaces
org.esa.snap.core.gpf.OperatorException: RESORB files are no longer available from Copernicus Dataspaces
        at org.esa.snap.engine_utilities.gpf.OperatorUtils.catchOperatorException(OperatorUtils.java:434)
        at eu.esa.sar.orbits.gpf.ApplyOrbitFileOp.initialize(ApplyOrbitFileOp.java:215)
        at org.esa.snap.core.gpf.internal.OperatorContext.initializeOperator(OperatorContext.java:528)
        at org.esa.snap.core.gpf.internal.OperatorContext.getTargetProduct(OperatorContext.java:298)
        at org.esa.snap.core.gpf.Operator.getTargetProduct(Operator.java:359)
        at org.esa.snap.core.gpf.main.CommandLineTool.runOperator(CommandLineTool.java:306)
        at org.esa.snap.core.gpf.main.CommandLineTool.runGraphOrOperator(CommandLineTool.java:284)
        at org.esa.snap.core.gpf.main.CommandLineTool.run(CommandLineTool.java:188)
        at org.esa.snap.core.gpf.main.CommandLineTool.run(CommandLineTool.java:121)
        at org.esa.snap.core.gpf.main.GPT.run(GPT.java:60)
        at org.esa.snap.core.gpf.main.GPT.main(GPT.java:37)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:566)
        at org.esa.snap.runtime.Launcher.lambda$run$0(Launcher.java:55)
        at org.esa.snap.runtime.Engine.runClientCode(Engine.java:189)
        at org.esa.snap.runtime.Launcher.run(Launcher.java:51)
        at org.esa.snap.runtime.Launcher.main(Launcher.java:31)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:566)
        at com.exe4j.runtime.LauncherEngine.launch(LauncherEngine.java:84)
        at com.install4j.runtime.launcher.UnixLauncher.start(UnixLauncher.java:71)
        at install4j.org.esa.snap.runtime.Launcher_gpt.main(Unknown Source)
Caused by: java.io.IOException: RESORB files are no longer available from Copernicus Dataspaces
        at eu.esa.sar.orbits.io.sentinel1.SentinelPODOrbitFile.retrieveOrbitFile(SentinelPODOrbitFile.java:106)
        at eu.esa.sar.orbits.gpf.ApplyOrbitFileOp.updateOrbits(ApplyOrbitFileOp.java:269)
        at eu.esa.sar.orbits.gpf.ApplyOrbitFileOp.initialize(ApplyOrbitFileOp.java:203)
        ... 24 more
2 Likes

I had the same problem today. what i did to fix it was to go to the processing parameters and check the “do not fail if orbit file is not found” and it worked just fine

1 Like

I guess you just skip applying the orbit file in this case which is not an option for us.

Agreed, the workaround suggests just to skip the orbit application. That should not be needed, since it seems that the orbit files are available but in the wrong place.
Looking at https ://step.esa.int/auxdata/orbits/Sentinel-1/POEORB/S1A/2024/12/ I can see that the new orbit files keep getting uploaded to 2024/12 folder instead of 2025/01:


so I’m increasingly convinced that the issue lies in syncing those files to SNAP site.

1 Like

Thank you for bringing this issue to our attention. The SNAP team is actively working to resolve it.

2 Likes

Issue fixed. The orbit files are now be available for download.

2 Likes

Thank you! I can confirm that SNAP now picks up the orbit files.

1 Like

For reference - this seems to happen every year. Orbit files are missing until about 2 weeks after the new year. I do not know why. Some automatic products that use sentinel observations get delayed because of this, which is unfortunate.