SARPROZ ©

We are seeing the same error message. Data is set up following the same procedure that we usually use, although we are on a new machine.

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]

Dear prof. Perissin,

Thank you for your answer and willingness to help me.
Answer to your questions are following:
1. I have 47 images, Sentinel 1A sensor, IW Beam mode, subswath 2, descending aq. mode
2. Temporal and spatial distribution you can see on attached images and dataset plots & graphs that I believe can be useful to you
3. I am also…[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.

So for APS estimation with 130+ images I can reduce amp. stab. thresh to much lower levels? I will try something like .75 and see what happens.

The only coregistration errors I got were S1 Stitching erros, which I inquired in another thread and was told to ignore. I will try coregistering the dataset again and see if there are any errors on those…[Read more]

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]

Hello friends,

I followed the tutorial by Mr. Yuxiao very closely. Results seem much better than before, but there are still a couple of anomalies.

First, the resulting points from 0.85 thresh amp. stab:

Coherence Before:

Graph Coherence;

Parameters Plot…

Heights:

Displacement:

Coherence after weighting (0.8; 0.95)

Coherence…[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

After reprocessing the point of interest with 135 images, the results are the same (extremes of displacement).

Here are examples:

Here are APS parameters:

Maybe this time series can provide some insight:

Thank you!

Thank you Yuxiao

Yes you can ignore.

The warning message there should be quite self-explanatory.

yuxiao

Dear periz,

I am reprocessing the dataset with 135 images (from 60 previous), I will post the results soon.

Thank you

This bug is solved.

Hello,

I have downloaded the newest version of Sarproz, and I am working on 48 images of Sentinel 1a data.
Frist, I would like to say that in previous version of SarPROZ I didn’t have this issue and everything worked perfectly (same datasets).

During Slaves extraction, I receive this error “Image N does not cover your AOI! Check footprints of N…[Read more]