SARPROZ ©

Hello Daniele,

could you please let us know the relation between original image intensity (in the SLCs) and the values got in “refl. map”?

I need to compute sigma_0 and know how to do it from original SLC but these values are different.

Thank you very much, Ivana

Hi Daniele,

thank you very much for the explanation and also for the implementation.

Can you also please let me know how is the periodogram peak width defined? If e.g. the width of 90% of the peak coherence. Just to consider if really plus minus three sigma_vel are the “limits” of the velocity estimation as the values really look quite…[Read more]

Thank you Yuxiao,

but today (with the 06-Oct version) I get a similar/same error.

(will try the other stuff later. Before, I threw the images with only partial overlap away, but now I do not. The area of interest is covered, but I get these problems…)

Regards,
Ivana

Daniele,

could you please answer the questions from the previous one-week-old post in this thread?

Thank you, Ivana

sorry, http://www.insar.cz/example.zip

Hi Yuxiao,

I am attaching one image from the FITTED directory (they all look approximately the same) and one image from the INTERFEROGRAMS directory (they do not look the same as expected, but the half-zero pattern is the same in all the interferograms), and the logfiles (hope they are the right ones). Please let me know what else you need.

Ivana

Hello,

I have also experienced interferograms with zero part of the area (in azimuth). I think that it can be (in some cases) solved by cropping larger area (in the area selection) with the radius over cca 12 km. With the radius of 5 km, I experienced this problems (in two datasets). There is no error here except for the “azimuth stretch”…[Read more]

Hi Daniele,

thank you, it works. I would like to ask some more:

I would like to process only 11 points (would appreciate it especially for the sub-cell positioning) but I need to select them. I am afraid that the selecting criteria would be too complicated (various values of intensity etc., scatter plots support > and <, but not =), is it…[Read more]

OK, thank you.

this is the “error” I get many times, however not important (I was not sure if the list is for one error or for more). I considered other error which – apparently – does not do any log into the logfile and even to the lasterror. It is probably only displayed in the bottom part of the geocoding window. No problem.

Yes, I tried the…[Read more]

No, I am getting exactly the same results also in the newest compiled version… together with lots of

stima_freq: WARNING!!

NaNs detected in input matrix: forcing them to zero!!

I do know where the problem can be…

I am sorry, that was not the compiled version, but older matlab version, so that is probably the problem… trying it once more in the newer version.

I.

Hello again,

using the compiled version of Aug 31 (no newer), I was processing S1 data, and the interferograms and everything were nice using automatically-downloaded SRTM. Now, I used my own DEM, and the interferograms look weird (see the itf and the DEM visualization).

I admit I have a DEM with such a weird form (corner cut) and I used it,…[Read more]

No, there are not two points geolocated at the same position (according to CSV, as point 699 can be clicked on, point 700 gives this error and 701 is somewhere else).

Here is the output from disp_err (putting it all, but I am afraid that most of it is related to the other instance run in the compiled version (this instance is run under matlab,…[Read more]

Hello Ana,

(estimated) residual height value is the HEIGHT WRT DEM.

SIGMA HEIGHT is the estimated standard deviation of the HEIGHT (resp. HEIGHT WRT DEM, they are the same), for its background, see another discussion thread. If you are interested, ask more, as it was not yet finished but I do not have time and concentration for it now.

The…[Read more]