Strange NaN area in Back-Geocoding result

[constantinevi]

Hello everyone,

Here is a problem I found in my result, some area become nodata in slave image, while the dem I input is correct. There is some figure:

The master image 20180416, east coast of Taiwan:

The slave image 20150619, there are several triangle look nodata area:

DEM data I input in same area, elevation seems no problem:

It seems Back-Geocoding operator have some bug like that?
I also mention about another similar problem in this thread:

Problem with "mask out area with no elevation" in S-1 TOPS Coreg

Hello, I try to do coregistration with Sentinel-1 image use S-1 TOPS back-geocoding operator. After update to SNAP 7.0, I found that when the option “mask out area with no elevation” is selected, some area will be mask even if it is part of land rather than sea. Here is an example: Master image intensity in coreg stack: [Honeyview_20171008_IW1_Stack1_ESD_Deburst_Intensity_IW1_VV_mst_08Oct2017] Slave image intensity in coreg stack: [Honeyview_20171008_IW1_Stack1_ESD_Deburst_Intensity_IW1_VV…

Does anyone encounter to this problem with your own external DEM?

[ABraun]

So you used your own DEM?
Please try once with SRTM 1Sec (Auto Download) to check if the error persists. It should not affect the coregistration quality to use it.