'ASTER 1sec GDEM' and DEM from TanDEM-X

[marjanmarbouti]

Dear all

I downloaded some data for ‘ASTER 1sec GDEM’ dem from below link:

https://search.earthdata.nasa.gov/search/granules?p=C197265171-LPDAAC_ECS&q=aster%20gdem&ok=aster%20gdem

I also have a DEM that I made by using SNAP from TanDEM-X product .

STEPS for making DEM for TanDEM-X:

• Making interferogram
• Multilooking
• Unwrapping
• Phase to height
• Geocoding (map projection: UTM zone, parameter projection:4north)

Then, I applied projection over one product from ‘ASTER 1sec GDEM’.

I want to compare (one of the product of 'ASTER 1sec GDEM) with (DEM from TanDEM-X). they are in same geolocation (figure 1 and 2) but pixels are different (figure 3 and 4).

Figure 1. Aster DEM product

Figure 2. TanDEM-X DEM product

Figure 3. Aster DEM pixels

Figure 4. TanDEM-X DEM pixels

What can I do to make pixels same?
I want to compare one pixel in ‘DEM by TanDEM-X’ with one pixel in ‘ASTER DEM’. Is it possible by this way?

[ABraun]

you can use the collocation tool to include both rasters into one product. The first product you select is considered the master and defines the pixel size and the extent of the product. The slave image will be resampled accordingly.

[marjanmarbouti]

(map projection: UTM zone, parameter projection:4north)

Thanks but how about coregistration (creat stack). Can I use it? What is difference between them?

[ABraun]

Classical coregistration is more effective for images with certain patterns, for example SAR images in slant geometry. It searches for statistically similar points in both images and creates a model to translate the geometry of the first image into the second.

If your data is already geocoded, “collocation” or “create stack” are the more suitable tools according to my opinion. The first is to match two images and gives you more flexibility to handle output file names while the second one takes multiple inputs. Both are fine for your case.

[marjanmarbouti]

Thank you so much