ALOS-2 derived decibel values seem too low - have I missed a processing step?

I’ve been processing a stack of ALOS-2 25m resolution georeferenced level 1.5 data (format - WBDR1.5RUD) using the steps listed below, however my final images converted to decibels have a range of high negative values, e.g. -61.4 to -206.1 db. I think they should be more in a range which has a maximum of 0 to 1 db. Visually, the spatial pattern of the final images look good, but just with the wrong decibel range. Could you please suggest where I might have gone wrong in the following workflow?

  1. conversion to beam-dim format for further processing within SNAP.
  2. multi-temporal coregistration of the scenes - ‘product geolocation’ specified as the initial offset method, and a nearest neighbour resampling method was used.
  3. Speckle filtering - the improved Lee Sigma filter, with a 5x5 averaging window, was applied to each image within the co-registered stack.
  4. Geocoding using the single SAR image mosaic option for each image within the co-registered stack. The output data has a resolution of 100 m.
  5. I then calculated sigma naught in decibels as: 10*log10(DN^2) - 83 (I applied this step within python)

The terrain is relatively flat, so I’ve not applied terrain correction (also this isn’t possible within SNAP for L1.5 imagery).

I’ve taken the calibration factor of -83db from the ALOS documentation. It does seem like the calibration factor might be off, and should be closer to -20db in this case.

Here are examples of the amplitude (resulting from geocoding using SAR mosaic option) and sigma naught (db) histograms.

HH_amplitude
HH_db

ALOS-2 documentation:

I’ve realised that after the processing steps applied, the amplitude_HH is no longer in units of DN. The original DN range is 461 to 11927, which converts to a more reasonable sigma naught decibel range of -1.469 to -29.717 db. I found that the SAR mosaic geocoding option changes the values from DN to a smaller range centered around 0. To solve for this, I tried converting to decibels before using the SAR mosaic option, but the decibel range is then shifted to a smaller range centred around 0.

Histogram of HH amplitude converted to decibels before using SAR mosaic:
HH_db_before_SAR_mosaic

Histogram following geocoding of this band using Radar → Geometric → SAR mosaic:
HH_db_after_SAR_mosaic

Can anyone please advise as to why this happens, and is there a way to convert these data back to their normal decibel range after using the SAR mosaic option?

I’ve realised my mistake - I had left the default options in SAR-Mosaic, including a ticked box called ‘Normalize’. Unticking this option results in the outputs being in the original DN range, which can then be converted to decibels correctly.

1 Like