Snap2stamps error

then the changes were not applied or in the wrong file.
Are you using the latest version of SNAP?

I’m using latest version SNAP8.0.3

Please check it once.

and the snap2stamps scripts make use of the xmls in this folder or is there another instance of the folder elsewhere?

While running this Snap2stamps python script in Ubuntu, I just copied graphs and bin folder to my working directory. Then i processed

  1. python2 slaves_prep.py project.conf
  2. python2 splitting_slaves.py project.conf
    the above two ran successfully,
    but while running the below step is is creating error,
    3.python coreg_ifg_topsar.py project.conf

Is there any path I have to set or no need?

Sorry i forwarded wrong image, below one is the correct one.

This is my project.conf file in bin folder

please also modify this line in the coreg_ifg_computation_subset.xml file

2 Likes

Thank you so much ABraun, You are excellent in problem solving.
I think it was running fine.
#####################################################################

Coregistration and Interferogram computation started:

#####################################################################

/mnt/f/Ahmedabad_zip/split/20171121/20171121_IW3.dim
[1] Processing slave file :20171121_IW3.dim

SNAP STDOUT:INFO: org.esa.snap.core.gpf.operators.tooladapter.ToolAdapterIO: Initializing external tool adapters
INFO: org.esa.s2tbx.dataio.gdal.GDALVersion: GDAL not found on system. Internal GDAL 3.0.0 from distribution will be used. (f1)
INFO: org.esa.s2tbx.dataio.gdal.GDALVersion: Internal GDAL 3.0.0 set to be used by SNAP.
INFO: org.esa.snap.core.util.EngineVersionCheckActivator: Please check regularly for new updates for the best SNAP experience.
INFO: org.esa.s2tbx.dataio.gdal.GDALVersion: Internal GDAL 3.0.0 set to be used by SNAP.
Executing processing graph
INFO: org.hsqldb.persist.Logger: dataFileCache open start
.INFO: org.esa.snap.core.dataop.dem.ElevationFile: http retrieving http://step.esa.int/auxdata/dem/SRTMGL1/N23E072.SRTMGL1.hgt.zip
SEVERE: org.esa.snap.core.dataop.dem.ElevationFile: error in opening zip file
INFO: org.esa.snap.core.dataop.dem.ElevationFile: http retrieving http://step.esa.int/auxdata/dem/SRTMGL1/N23E072.SRTMGL1.hgt.zip
INFO: org.esa.snap.engine_utilities.download.DownloadableContentImpl: http retrieving http://step.esa.int/auxdata/dem/egm96/ww15mgh_b.zip
INFO: org.esa.snap.core.dataop.dem.ElevationFile: http retrieving http://step.esa.int/auxdata/dem/SRTMGL1/N22E072.SRTMGL1.hgt.zip
INFO: org.esa.snap.core.dataop.dem.ElevationFile: http retrieving http://step.esa.int/auxdata/dem/SRTMGL1/N22E072.SRTMGL1.hgt.zip
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: Shifts written to file: /root/.snap/var/log/IW3_range_shifts.json
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: Estimating azimuth offset for blocks in overlap: 1/4
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: Estimating azimuth offset for blocks in overlap: 2/4
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: Estimating azimuth offset for blocks in overlap: 3/4
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: Estimating azimuth offset for blocks in overlap: 4/4
INFO: org.esa.snap.core.dataop.dem.ElevationFile: http retrieving http://step.esa.int/auxdata/dem/SRTMGL1/N22E071.SRTMGL1.hgt.zip
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: Shifts written to file: /root/.snap/var/log/IW3_azimuth_shifts.json
…10%…20%…30%.INFO: org.esa.snap.core.dataop.dem.ElevationFile: http retrieving http://step.esa.int/auxdata/dem/SRTMGL1/N23E071.SRTMGL1.hgt.zip
…40%…50%…60%…70%…80%…90% done.
– org.jblas INFO Deleting /tmp/jblas3912217123297068240/libjblas_arch_flavor.so
– org.jblas INFO Deleting /tmp/jblas3912217123297068240/libjblas.so
– org.jblas INFO Deleting /tmp/jblas3912217123297068240/libgfortran-4.so
– org.jblas INFO Deleting /tmp/jblas3912217123297068240/libquadmath-0.so
– org.jblas INFO Deleting /tmp/jblas3912217123297068240

[1] Finished process in 456.325519085 seconds.
Coregistration and Interferogram computation for data 20171121_IW3.dim successfully completed.

very good.

It’s working thank you Abdel.

#####################################################################

TOPSAR Splitting and Apply Orbit

#####################################################################

[1] Folder: 20190108
/mnt/e/Jamnagar/slaves/20190108
[’/mnt/e/Jamnagar/slaves/20190108/S1A_IW_SLC__1SDV_20190108T011020_20190108T011047_025379_02CF66_A6BE.zip’]
FILE(s) : /mnt/e/Jamnagar/slaves/20190108/S1A_IW_SLC__1SDV_20190108T011020_20190108T011047_025379_02CF66_A6BE.zip
[’/usr/local/snap/bin/gpt’, ‘/mnt/e/Jamnagar/graphs/splitgraph2run.xml’, ‘-c’, ‘110G’, ‘-q’, ‘40’]
SNAP STDOUT:INFO: org.esa.snap.core.gpf.operators.tooladapter.ToolAdapterIO: Initializing external tool adapters
INFO: org.esa.s2tbx.dataio.gdal.GDALVersion: GDAL 2.2.3 found on system. JNI driver will be used.
INFO: org.esa.s2tbx.dataio.gdal.GDALVersion: Installed GDAL 2.2.3 set to be used by SNAP.
INFO: org.esa.snap.core.util.EngineVersionCheckActivator: Please check regularly for new updates for the best SNAP experience.
INFO: org.esa.s2tbx.dataio.gdal.GDALVersion: Installed GDAL 2.2.3 set to be used by SNAP.
Executing processing graph
INFO: org.hsqldb.persist.Logger: dataFileCache open start
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)
Connect to qc.sentinel1.eo.esa.int:443 [qc.sentinel1.eo.esa.int/131.176.235.71] failed: Connection timed out (Connection timed out) due to Connection timed out (Connection timed out)
done.

Error: [NodeId: Apply-Orbit-File] Connect to qc.sentinel1.eo.esa.int:443 [qc.sentinel1.eo.esa.int/131.176.235.71] failed: Connection timed out (Connection timed out) due to Connection timed out (Connection timed out)

[1] Finished process in 71.100687027 seconds.

#####################################################################

Please give me solution for the above error?

Hi @suribabu,
as you can read on the forum and post by @ABraun, since Monday there is a problem with “apply Orbit File” and we are all waiting for
an update from the developers.

Regards,
S Savastano

1 Like

Thank you so much.

root@DESKTOP-4HUO8B9:/mnt/e/Jamnagar/bin# python2 coreg_ifg_topsar.py project.conf
/mnt/e/Jamnagar
/mnt/e/Jamnagar/graphs
IW3
/mnt/e/Jamnagar/master/S1A_IW_SLC__1SDV_20190426T011020_20190426T011047_026954_030885_3E4D_split_Orb.dim
/usr/local/snap/bin/gpt
/mnt/e/Jamnagar/graphs/coreg_ifg_computation.xml

#####################################################################

Coregistration and Interferogram computation started:

#####################################################################

/mnt/e/Jamnagar/split/20190108/20190108_IW3.dim
[1] Processing slave file :20190108_IW3.dim

From last one hour onward it is showing like this. with coreg_ifg_computation_subset.xml also same issue. Please check it once

I have around 29 SAR images, From last one hour onward above posted command is running but still there is no output is created for single image ( coregister folder and interferogram folder) .

maybe related to the DEM used in the BackGeocoding? A process related to digital elevation models is taking forever to finish

Thank you so much ABraun it’s working now.

Dear ABraun
S1-TOPS split is not running. please check it once. I installed all the updates now it is SNAP8.0.3.

I can’t see an error.
Maybe your disk is full? Restatting SNAP could also help.

No still 2TB free space is present, it took around 10 minutes to complete this step.