Only use the elevation generated by InSAR as the input (as you did)
Using the ASTER here is totally fine. Make sure you check “DEM” in the terrain correction step. This writes the ASTER DEM in UTM coordinates into your target product so you can compare later.
If you do this with the InSAR elevations of both dates, the results will be of the same size and coordinate system and then you can select “Radar > Coregistration > Stack Tools > Stack” to bring them into one final product.
I made elevation result and the ASTER DEM in UTM coordinates (figure1) but it seems a little strange although I did not work with DEMs but why the ASTER DEM has DEM over some area of ice and does not have DEM over other parts?
Another idea, I made a mosaic and I think the resolution was changed after making mosaic.
Yes. Now I got the point, making mosaic reduces resolution.
Any idea about it?
that’s possoble. You can use the measure tool to see how large the single pixels are.
I see that you have just updated your post. Strangely, the DEM was resampled for mosaicing.
If you remember, I tried to make DEM for 18 and 29 May (for example HH). Result of 29th May was fine but I think something goes wrong with unwrapping 18th May (figure1, 2,3).
I think because we have water in our interferogram (figure1). I do not know how SNAP does unwrapping and from where it starts to do.
How can I find unwrapping code or method that SNAP uses it for unwrapping? Do you have any idea about it? How this error would be solved?
you can mask out low coherence areas in the image using a valid pixel expression as described here: Subsidence map in 3d view) but this unfortunately doesn’t affect the uwnrapping process.
Is it possible that I use ‘special subset from view’ over interferogram and subset my area of interest OR should I do this over intensity before making interferogram?
To your second question: this is possible for must sensors besides Sentinel-1 because of the bursts. Subsetting the interferogram for TSX/TDX is no problem!
