The problem
We are trying to compare multiple InSAR DEMs (derived from TerraSAR-X images) to identify topographic changes and measure volumetric change.
Before subtracting 2 InSAR DEMs they must be calibrated so that they represent the same absolute elevation on areas that did not change. We’re struggling with this calibration step; e.g., we are having issues with tall buildings that have very different height in each InSAR DEM even after calibration (sometimes, positive height Vs negative height).
The data
We have computed InSAR DEMs from coherentT TSX image pairs for an urban area in the middle east. We then subtracted 2 InSAR DEMs to see where topography has changed and be able to measure volumetric change.
We selected the images with the smallest temporal baseline and largest perpendicular baseline. The DEMs were created using ESA’s SNAP toolbox following these steps:
NB: the same analysis was done with Iceye data as well. We observed similar calibration issues.
Tested methods
Before comparing 2 InSAR DEMs we aligned them, and calibrated them using SRTM DEM as ground truth. We tried different methods for the calibration:
Both methods gave similar results.
Results
After calibration we differentiated the 2 InSAR DEMs. To assess the quality of the calibration we computed the RMSE of this difference. We basically expect the values of the difference to be close to 0 in most parts of the image except where terrain have changed (e.g., construction site).
The attached 'InSAR_difference.png" is a InSAR DEM difference before (left) and after (right) calibration.
NB:
Conclusion and remaining challenge
With the calibration applied we were able to bring down the RMSE of InSAR DEM difference from ~10m to ~6m.
However, we keep having issues with tall buildings, as well as and roads (maybe due to moving cars that corrupt the phase).
In the images below we have a tall building where the InSAR DEM difference remains above 15m (even after calibration).
See image "DEM_difference_tall building"
These are zooms of the same images presented in the 'result' section
Possible cause
Anyone has any ideas what we could try next to solve this issue?
Few ideas we haven't tried yet: