SARPROZ ©

correct.
if you are using matlab, you can type “fast” at the command prompt, this will load all important variables and file names. the you can use “leggi” to read the data, with Type=1. here the help:
Data=leggi(FileName,S,L)
Data=leggi(FileName,S,L,[Svet,Lvet])
Data=leggi(FileName,S,L,[Sin,Sfin,Lin,Lfin])…[Read more]

sorry, no idea. since it’s the most recent version of Matlab, then the suggestion is to write to Mathworks reporting the error.
to temporarily solve the problem, you can use the Sarproz compiled version. you just need to launch the co-registration in the compiled version, then you can switch back to Matlab for doing the rest. The Sarproz license…[Read more]

Sorry, it seems we overlooked your post…
It sounded a system/permissions problem anyway…
But, never mind, now it works…

does this file C:Program FilesMATLABR2018atoolboximagesimagesprivateresampsep.mexw64 exist?

what is the output of “license(‘test’,’Image_Toolbox’)” at the matlab command prompt?

you need to include a lasterror.mat file

open a terminal (command prompt), cd to the folder where main.exe is, launch the application from the terminal by typing “main.exe” and pressing enter, then tell us what messages you get

this means that the installation of the mcr was not successful
try again
and check if the directory where you installed it is in the system path. if not, add it manually to the system path

Hi Rajabun,
this is indeed a visualization bug. What is visualized is the content of the jpeg images which is written in a 0-255 scale. While we work to fix it, you can circumvent the bug by temporarily change the Max Matrix Size value in the advanced parameters https://sarproz.com/manual/adv_param.html In your case, you should write a value equal…[Read more]

we are now uploading a fix.
to temporarily solve the issue, you could switch back to a previous sw version.
The APIDelay was first introduced on March 24 and then modified on April 19

hi
the error you report is in fact a small bug, an updated version will soon be uploaded online.
however, in normal conditions you should not get such error. it is not clear to me what you are trying to do.
check well please the instructions in the tutorial. make sure data are in the proper folders and try again.
best

Hi Carolina,
you should reduce the size of your attachments (pictures), the maximum allowed should be 2MB.
There are many ways to export results to google, you do not say how you did it.
In your case, you should use the “GeoOut” function in the “filter/matrix visualization” frame in the “scatter plots” module:…[Read more]

You don’t need to re-coregister the dataset. What you can do is looking at the interferograms to see if there are fringes or other problems. In case of problems you may try to remove those images from the dataset (delete the corresponding lines in the dataset.txt file) and re-coregister them, if you think it is a coregistration problem.

As discussed in many places in the forum, this could be caused by an inaccurate GCP.
However, you can still apply a post-processing correction, using geographic correction operations.
You can find them in the time series module (that correction is applied on a single time series object).
Or you can apply them at you whole site, via this module:…[Read more]

* numbers are always relative to the particular case. E.g. .85 with 35 images is different than .85 with 90 images. With 90 images, you can take this threshold lower. to get an idea, plot the histograms of these parameters in your area of interest
* the bad looking APS you plotted above deserves some closer look. probably you got some…[Read more]

Hi Uros,
before discussing about possible processing solutions, one has to observe well the data: how many images do you have and their temporal/geometric distribution, what sensor and acquisition mode, how do reflectivity map and amplitude stability index look like. Then, when the case is complex, better to generate also MST interferograms. When…[Read more]

Hi Steffan,
sorry for the late answer. We need to find some time to check your data. We need to see things from the beginning.
For the moment, I can suggest you to check this simple exercise https://www.sarproz.com/yuxiaos-tutorials/
(the last tutorial). It gives you an idea of the results you should see step by step
best

Yes, there is surely something wrong.
We should check the APS results

In all geocoding functions you have a menu and you can choose among kml, geotiff RGB, geotiff 32
The last option exports the actual values and you can load them into a GIS software
Here more infos: https://sarproz.com/manual/geo_sito.html
And here a similar answer with more options:…[Read more]

the displacement you detect from InSAR is along the LOS.
To get displacement along track, you may use pixel tracking.
We do not have yet a proper specific module for pixel tracking, but you can still perform it.
Here an exercise showing how to apply pixel tracking (the third tutorial):
https://www.sarproz.com/yuxiaos-tutorials/
best