SARPROZ ©

My apologies. Here are the files.

Best

Dear friends,

I have good news and bad news…

Good news – Using “orbits only” coregistration parameter not only made coregistration much faster but also corrected the failed interferograms from before, excelent!

Bad news: There is still ramping, mostly in azimuth, and strange results.

A – First the ramping pairs:

B – Now the…[Read more]

Dear Yuxiao,

I have sent you the site log file to the provided email address.

In the meantime I will check out “orbits only” coregistration.

Thanks!

So I re-cogistered the dataset (I know I didn’t have to, oh well) and increased the number of reference points to 500K. Didn’t notice any errors except S1_Stitching like before. Using Max Area for AOI selection.

Then I changed to MST graph I processed Interferograms. There still seems to be a lot of problems…

Ramping in numerous images, here…[Read more]

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]

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]

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

Dear periz,

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

Thank you

Thank you!

For anyone having the same problem, selecting an appropriate manual GCP seems to fix the problem. Roads and other landscape features are properly aligned now. I used a floodlight from a football field and it seems to do the job just fine.

The all zero error seems to be due to ocean, as the satellite data does cover some coastal area.

Thanks for the help.

I am now getting an SRTM error:

sel_par: neither file D:SNAPBejaBeja_SARSLC2017RESULTSDemSynt nor D:SNAPBejaBeja_SARSLC2017RESULTSDemSynt.mat found

files D:SNAPBejaBeja_SARSLC2017RESULTSDemSynt and D:SNAPBejaBeja_SARSLC2017RESULTSDemSynt.mat not found

leggi_srtm: Warning! file D:SNAPBejaBeja_SARSLC2017..SRTMN05W033.hgt is all zeros!!…[Read more]

I will try to select a different GCP than the auto GCP option. What are the best practices for GCP selection at Sentinel 1 resolution? I am aware posts are good for higher res. sensors, but what about ST1? A building?