SARPROZ ©

yes, it’s a measure of the accuracy of the height estimation
it is calculated based on the distribution of the dataset parameters (normal and temporal baselines) and on the options you selected to estimate the time series parameters (as velocity and height)

Yes, velocity and deformation trends are the same.
The cumulative displacement is saved when you do a non-linear processing.
You do a non-linear processing if you input a value in the “smart” box in the time series processing options.
That value corresponds to the length of a temporal filter. So, the outcome is a non-parametric estimation of the…[Read more]

3. if the cumulative displacement CumDisp.mat file is not there, it means it was not saved. Is the velocity there? If the velocity is there and the cumulative displacement not, it means you estimated a linear model, so, the cumulative displacement was not produced. To know to cumulative displacement, just multiply the velocity by the observation…[Read more]

1. select a set of points via load mask using e.g. the temporal coherence or the amplitude stability index. it does not make any sense to select points based on cumulative displacement

2. then check your results via histogram and scatter plots modules. you can check the histogram of the cumulative displacement to understand what is wrong. then…[Read more]

Use this module: http://sarproz.com/manual/xplot.html
1. load points via load mask in site processing
2. open the scatter plots module
3. choose latitude as y axis, longitude as x axis, velocity or any other parameter of interest as color
4. press “go” in filter/matrix visualization to check what you are doing
5. press “geoout” in the same frame…[Read more]

zip not rar

the license was sent to your email address

Plz inform so that i can send you the results.

Looks like we overlooked your post…
Did you solve the issue?
You don’t need to increase the search pixel: the initial cross-correlation is used to estimate and remove the big shifts. Increase the search pixel only if you think that shifts change significantly within the image (e.g. because of a huge stretch).
We cannot debug your lasterror…[Read more]

sorry, first 2 lines 123:134 and 139:148 is original position of center lat and lon

What has worked for me was adding last four lines to alos_psr_meta.m

mid_lat = str2double(facility(3065:3084));
mid_lon = str2double(facility(3085:3104));
if isnan(mid_lat) || isnan(mid_lon)
mid_lat = str2double(summary(123:134));
mid_lon = str2double(summary(139:148));
end

However, I’ve lost the M-file, probably Daniele…[Read more]

Dear prof. Perissin and Matus,

have you managed to resolve this issue? I’m probably encountering the same one.

There is prior error concerning the coordinates (of scene centre), since srprz tries to download SRTM for NaN latitude and NaN longitude (please see the log attached).

Many thanks
Richard