Processing is cut at some latitude in snap 3.0

Dear colleagues,

I found the InSAR processing is automatically cut at some latitude. As a case, I tried the Japanese quake data acquired o March 22 and April 15 (the northernmost slice of S1A data in that area). The InSAR processing is wrongly cut at 35 deg N. Actually there are still some data in the land. Please check with the data or somewhere in the code for the issues.


Are you sure the DEM is covering the missing part? If the SRTM DEM tiles go missing for example something like you describe can happen.

Hi, Marcus, this issue occurs before differential step.

Yeah, the DEM is absolutely there. Actually, SNAP2 works fine. Cheers,