SARPROZ ©

Dear Yuxiao,

For testing my results: what method can you introduce? how you can help me in this check?
Nader

if you pick up manually a GCP,
you should not get significant problems

however, just make sure not to have NaNs in the DEM in SAR coordinates
in case, place them to zero
d

Hi Yuxiao,

can you please send me the compiled version for windows 64 bits with it?

Thank you for your help,
Dora

Hi Daniele and Yuxiao,

thank you, the problem was solved by deleting the one image,

it is S1A_IW_SLC__1SDV_20151004T045254_20151004T045321_007998_00B312_5C90.SAFE (IW3),

however now, the process of slaves extraction gets stuck on a different image,

S1A_IW_SLC__1SDV_20151109T045242_20151109T045309_008523_00C10E_3329.SAFE
(with no…[Read more]

Hi Dear Dora,

The warning inside your logs is fixed and your master image should extract just fine. I’ve already tested out the sample data you’ve uploaded and the extraction works well.

To eliminate the warnings you can just download the file I’ve uploaded, extract them and overwrite with the exist ones in your pcodes folder.

Yuxiao

Hi Santiago,

In the current version of code we didn’t implement the importing of s1a dual polarization. We will fix this issue in a couple of days the most. We will let you know on that.

Meanwhile, for downloading s1a data, due to the heavy burden of ESA’s server, it is either recommended to use the API…[Read more]

Hi Ivana,
we are adding an option for visualizing which image has the problem.
I’ll send you the pcodes by email, there are also some other changes going on, keep it as a temporary version.
You’ll have to use the “debug” option in advanced parameters.
In that way, you can post here which is the image with problems, Yuxiao needs to look into it.
bye
d

Ciao Dan,

Here the names of two of the images:

S1A_IW_SLC__1SDV_20160104T052642_20160104T052709_009340_00D80F_1E18
S1A_IW_SLC__1SDV_20151223T052642_20151223T052709_009165_00D311_E59E

I know this is not the propper place to ask this, but have you experienced recently problems to download Sentinel-1 data?

Thanks,
Santiago

Hi Santiago,
send us the file name of a VV/VH image so that we can download and check it
dan

Hi Matus,

Sorry for the late reply..

Since the coregistration will rely on the area and quality of overlapping parts between bursts, it is always generally a good idea to extract a bigger area (especially on range direction) so to ensure there are enough overlapping parts for fine-coregistration.

Then, since the fine-coregistration will rely…[Read more]

Hi Dora,

The link is fine. I am going to run you data in a while and then let you know!

Yuxiao

Hi Yuxiao,

I’m sorry for the delay, I’m having trouble with the ftp. Please let me know if you can access the image through this link instead: https://www.dropbox.com/sh/u8gekioz09t9ynf/AABb2ecF1XYTu7sutZqEQflya?dl=0

Thanks,
Dora

Hi Sg,
– here http://sarproz.com/manual/slc_data_module.html you can read that you can update your dataset, trying to coregister again the failed images (be careful, when you press buttons always read carefully the messages given by the sw. in particular, if you do not check the “update” option you may overwrite your work if you press randomly…[Read more]

Hi Dear Nader,

Yes first we should at least see the fringes.

In the second place, as said in the previous topic, It would be great for you to send me you master image’s file name (or date, but file name preferred), the image pairs (same as master image) that has ramps, and the range (coordinates, samples and lines) you set for your area so t…[Read more]

Hi Ivana,

Thanks for the info! I will take a look into the data and let you know!

Yours,
Yuxiao

hi Nader,

as mentioned by Yuxiao in a previous topic, there could be several reasons for having a ramp on an interferogram.
E.g. orbital inaccuracies, coregistration problems, atmospheric artifacts and so on.
Yuxiao is checking it because the Sentinel processing still deserves some extra care.
Generally speaking, forgetting for a moment that you…[Read more]