Snap2stamps error

hi i got the same problem but in version 8 updated today.

I saw that the file had to be modified:

but mine was updated today and I sensed that nothing had to be modified, because it was not the same as the indications previously offered.

So, some solution @ryeramirez @ABraun

if you have processed the interferograms with SRTM 1Sec, there should be no problem at all, because the download only affected SRTM 3Sec.

So the export still stops with SRTM 1Sec?

How do I know with which of the options the images were processed?

I did not modify any files, nor instructions.

In my ignorance, I think it used SRTM 1Sec, since if there are self-discharge problems, it is logical to think that it directly downloads SRTM 1Sec

In that case I would say yes, despite using SRTM 1Sec, snap2stamps stopped.

In this case SRTM 1Sec was used (line 69 of this file)

Very strange indeed, your screenshot also indicates that SRTM 1Sec was used. So the problem with the export is not related to the changed availabiltiy of SRTM 3Sec. You did nothing wrong, don’t worry - we just haven’t found the reason for the error in general.

Can you try with the SNAP GUI exporting a single pair using the StaMPS export operator?
Can you tell us if this works?

Hi, @nachin6789!

I did solve the problem following the work around solution proposed by @ABraun.

You can find it here at the last message: SRTM ZIP-files are corrupted or not found

Thank you @ABraun as always.

1 Like

thank you for reporting. May I ask which of the two solutions worked for you? And what version of SNAP did you use?

I used this solution.

Change it from
DEM.srtm3GeoTiffDEM_HTTP =
DEM.srtm3GeoTiffDEM_HTTP =

I am using SNAP 7.

thank you for reporting - good to know.
Did you re-compute the interferograms based on the new SRTM 3Sec source or has changing the source already solve the export from being stuck?

I think it works halfway, I generate 4 exports to test, it seems that everything is going well but the dem folder, I think it needs to generate the projected_dem.rslc file

In any case, if snap2tamps is executed, only 1 of all images is generated (that is, it seems that it is only capable of creating 1 image and then stops iterating with the rest of the images)

Hi, @ABraun!

Since I am doing the processing per batch (i.e. per 10-20 images), which is in my experience a lot faster compared to processing the whole dataset in one run given the current resources I have, I didn’t do any interferogram re-computation for the batches I have processed before experiencing the problem.

And to trace any source of error when doing StaMPS analysis after processing all batches, I have separated the diff0 and rslc folders created thereafter (after doing the solution proposed). I will merge all all soon.

I hope this won’t create another issue during the StaMPS analysis.

Thank you.

1 Like

This surely helps us, thank you!

Hi, @ABraun

Just an update.

After combining all preprocessed data before and after implementing the solution proposed, the StaMPS processing was successful.

Thank you.

1 Like

Sounds good, thank you!

Dear Sir,
I recently updated SNAP Latest version for SNAP2StaMPS processing. My server having these below specifications. Processing 52 interferograms creation it took around 3 days time. Please suggest what setup i wanna change in my Windows 10 server.


in case you are using SRTM 3 Sec for the integrated topographic phase removal: SRTM ZIP-files are corrupted or not found

In my Study I’m using SRTM 1sec for interferogram generation.

you can try to optimize the memory consumption as described here: I’m getting the error “Cannot construct DataBuffer”, "“GC overhead limit exceeded” or “Java Heap Space”. What can I do?
If you have 128 GB RAM you can set Xmx to 96G

1 Like

Thank you ABraun.

I have the following error message in snap version 8.

I knew that for version 7 of SNAP I had to modify the file if only 1 burst is used.

My question is, should I change the names of the parameters in the chart “coreg_ifg_computation_subset.xml” (exactly the same as in version 7 of this post)?: