Artefacts in S1TBX radiometric terrain flattening

The TF tool is renaming the Beta_Nought into Gamma_Nought, so I considered gamma_GRD_noTF and gamma_GRD_TF. Maybe one should compare beta_GRD_noTF and gamma_GRD_TF?

Yes, after TF, the output is terrain-flattened gamma nought, so that is correct. But as an input to TF, one should provide a radar geometry image in the backscatter convention beta nought, not gamma nought.

Hi @mengdahl, hi all,
I am trying to correct for terrain using the Terrain Flattening operator and Range Doppler Terrain Correction. However results after Terrain Flattening are highly unsatisfactory (s. Screeshots). I wonder if this is (still) a issue of the algorithm or if there is a way to improve the output.
I´m working on Win10 64bit, Snap 6.0 Beta, Example dataset: S1B_IW_GRDH_1SDV_20170110T095447_20170110T095512_003784_00681B_B4AB.SAFE (Chilean Andes)
I use a gap filled TanDEM-X DEM (doesnt cover the whole radar scene) so I doubt that the issue is within the DEM (Projection UTM 19S, resampled to 10m with bilinear; also tried WGS84 Lat/long).
I applied (and varied) the following pre-processing steps: Thermal Noise Removal >Apply Orbit File > Calibrate to beta > (Subset) > Speckle Filter >Terrain Flattening > Terrain Correction


– Calibrated Image –

– DEM (same extent as TC&TF below) –

– Terrain Flattened and Terrain Corrected (without additional normalization) –

– Terrain Corrected –
Range Doppler with radiometric normalization set performs well in referencing the image to the source DEM but correction for terrain is weak and shadows largely persist (as well as bright areas)
Similar posts:

Best
Chris

Could you fix the orientation of the images - it’s very difficult to compare the results for the moment. The terrain flattened scene looks good IMO, I don’t know what is going on with the terrain corrected version.

Hi @mengdahl,
I edited the screenshots, hope its now easier to compare. I´m not sure with the TF image, the blurriness and the NaN holes (in the TF&TC image) are much different from what I know of corrected images from MapReady (which of course uses a different algorithm and doesnt support S1). Let me know if I can provide you with any additional info