SARPROZ ©

once again the attachment

Hello Yuxiao,

OK, trying to attach the logfile (long).

the image with the phase jump is 20141223.

and the images with wrong coherence (at the North) are 20150820-20150901, 20150703-20150715, 20150808-20150901, 20150727-20150808, 20150715-20150727.

regarding the area: the center is now (if I remember well, is it possible to get the values…[Read more]

Hi Ivana,

Recent days I am working on killing the bugs that are possibly occurred because of partial overlap images. In the next few days a new version should be released and it should work better with those partial overlapped images.

Can you provide the log file of geocoding all interferograms and what the error is? So we can look into detail…[Read more]

Hi Matus,

I am still looking into your results and logs, but I reply here what I’ve finished looking and I will keep on investigating and reply you the rest.

1. Co-registration-error: Sorry, this error was due to a bug in the code that deleted the SLC file so that the file for coregistration refinement is missing. I will kill this bug for the…[Read more]

sorry, the file was also too large 🙂

http://www.insar.cz/itfs.zip

Ivana

Hello,

sorry for my long pause, I was out.

Now I am trying the processing again, with the compiled version of Aug 31st (as the update function does not work for me in the matlab version).

I decided to delete those problematic images, as they were problematic due to only partial overlap with the others in the AOI. The process of selecting the…[Read more]

sorry, the file was too big to be included in attachement

https://www.dropbox.com/s/m30bbbhcoarrreh/tests.zip?dl=0

finally, i get some promisingly looking set of images and interferograms, but also:

1) corregistration refinement error (applied experimentally),
2) interferograms plotted through Small Area Processing differs when “View SLC” and “Read and Plot Interfs” functions are used,
and can be seen in attached zip (second folder with time-ordered print…[Read more]

We are working at stitching subsequent images together. Up to now Sarproz never did it, we always worked with single footprints.
The reason for renaming images acquired on the same day was a quick and dirty solution for managing TanDEM-x bistatic pairs without changing the naming convention.
What you can do at this moment is working on them…[Read more]

hi there, apparently there’s a problem with renaming the Sentinel-1 images with the same dates.

when the duplicates are deleted from SLC directory, it is possible to continue with proccesing.

lasterror.mat and log files attached

cheers

Thanks for your suggestion. I am trying, ‘Height’ here mean the accumulative height, doesn’t it?

the “smart” function implements a non-linear analysis, so, it is clear that the linear velocity will not be estimated
use the Cumulative displacement instead.
consider anyway that here the key point is the estimation of the height.
after the smart, you could repeat the analysis reading the height previously estimated and estimating a new linear…[Read more]

Dear Prof.Daniele

Please, Find attach error file below

Best Regards,

Ana

1. that is no “software error”. it’s a message about terms called “master error” and “reference error”. if the software returns an error you get the usual messages “an error occurred … lasterror.mat was saved …”
2. probably you clicked on a pixel which is not a PS. but as I can see from that attachment, a PS IS selected and its parameters ARE…[Read more]

Dear Prof.Daniele

From the problem above, It is SOLVE and OK.

But, After I re-processing my data, Any problem occur.
I used 20 ENVISAT ASAR image and using STAR-graph (before I used MST-graph).
In Site Processing toolbox, I have done and have very good result based on coherence graph (See image).
I want to generate Geocoding, it’s mean I must…[Read more]

I think I made a mistake, it was the logical cores…

I am afraid this is an overfitting case.
I suppose you do not have many images, so, in such case I do not suggest you to estimate the thermal expansion.
Also, keep height and velocity ranges small in the APS estimation.
Better you remove high points when estimating the APS.
The APS estimation process should be kept as simple as possible. Later in…[Read more]

I am tempted to answer in the following way:
whatever the initial PSC you select, there is no better way to identify the good targets as with the temporal coherence. That is, the best way to state if a point is reliable or not is to look at the phase dispersion after analyzing the connections. With “analyzing the connections” I mean processing the…[Read more]