SARPROZ ©

Yes, the .off file is present and looks reasonably.

And slave image is also in the EXT folder, except for the fact that it is not VV, but HH, and the corresponding jpg looks reasonably, similar to the master.

By the way (the processing is not important, I am doing it just to check and see), I could not open the site processing (did you see it…[Read more]

Hi Ivana,

by looking at the log files, I would suggest the following:

Checking in /EXT folder the file 20150123_20150324_init.off and check if there is anything written inside.

It would also be helpful to check the intensity of both the master image and slave image. the master will be in FITTED folder as the name 20150213.jpg. The slave image…[Read more]

Hi Ivana,

I can’t see your log in the forum… Can you find another way to pass the log file?

thanks,

yuxiao

type “fast” in Matlab
and then use the following expression
[Rg,Az]=geo2SAR(lat,lon,h,el,Master,handles.SiteParam.DirSite);
el=1 corresponds to WGS84
otherwise input a string like GRS80 or the ellipsoid you need

to extract phase/amp values the easiest way is to use the small area.
when you load a small area, complex numbers are accessible in the…[Read more]

Hello Yuxiao,

just for sure, I am reporting failed coregistration (for 1 image) on different scene set. I cannot find any reason (error) for this. And the error does not let me go further.

Thank you, Ivana

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