Image with a resolution of 20x20 m

s1tbx
#21

you can do this easier by coregistration of all images. If you select a master image, its resolution and extent is used for all salve images. You can define the resampling technique and what should be done with areas which aren’t covered by all images (minimum extent, master extent, maximum extent).

#22

Thanks for the help @ABraun
I have some more questions, please look at them:

  1. As you told me, I used co-registration and I put three images (1. backscatter, 2. coherence 3.phase) but I do not know why in the result, I do not have phase image?

You can see my steps in below:

  1. Productset reader; I put three images here but type, acquition, track and orbit are empty. I used these data before for classification and I had same issue ( I mean type, acquition, track and orbit were empty) but the classification worked and I thought it was not important, so I do not think so this is a problem.

    co1.png1920×1080 688 KB

  2. Creat stsack; I leave this box like below but I do not know what is the meaning with ‘output extent’ here.

    co2.png1920×1080 684 KB

  3. Cross-correlation; I leave this box like below but I do not know what is the meaning with its options here.

    co3.png1920×1080 706 KB

  4. Wrap; I leave this box like below but I do not know what is the meaning with its options here.

co4.png1920×1080 683 KB

Another important thing;
5. How can I see what is the resolution of my original data? As I mentioned that before when I went to re-sampling part, the resolution part was zero. Why?

#23

I have one question regarding this answer that you (@ABraun ) gave. Sorry if I misunderstand.
As I look at SNAP software, there are several ways for changing resolution;

  1. Using multi look option in SNAP
  2. using re-sampling option in SNAP
  3. using Range Doppler terrain correction option in SNAP
    So why you mentioned that we should use first, multi looking and then the RD Terrain Correction???!!

Cheers,

#24

if you already performed RD terrain correction the better method for offset estimation is “product geolocation” instead of “orbit”

#25

Each of these steps changes the resolution but they still perform different tasks:

  1. Multi-looking generates square pixels out of slant range geometries in the first place, no resampling technique applied.
  2. Re-sampling only changes the resolution to a given pixel-size.
  3. Terrain Correction adjusts the image to local topographic conditions, thereby using resampling as well.

It totally depends on what you want to do with your data. There is no “standard” way of perparing SAR data for analyses. Sometimes multi-looking simply helps to see the image undistorted.

#27

Hello all,

I know this topic is closed for over 2 years now, but I need to ask you this:

When I give the pixel size of 30 m in RD terrain correction for my SAR image, spatial resolution is set to 30 m. However, when I subset (Clip) my image in Arcmap according to the shapefile, if I want to make the same rows and columns as my Landsat image (Subset from same shapefile), pixel size changes to 30.5 and 30.9. Pixel size of Landsat is 30 m. Can someone please tell me why this happens and how can I prevent it?

Thank you for help!

#28

I’d say this depends on how ArcMap treats pixels which partly lie outside the shapefile. You can check in the processing environments if you find some setting which indicate that resampling is involved.

If you want to adjust Sentinel-1 and Landsat-8 to have the same pixel sizes and numbers, you can use the collocation tool with the one of smaller coverage as the master and the other as the slave.

#29

Hi!

Thank you for help!

Just letting you and everyone know that re-sampling twice worked.