I tried to use the DEMAssistedCoregistraetion graph to coregister two GRD Sentinel-1 in ground range geometry and it works pretty well (seams to reach the same accuracy as S1-TOPS-coregistration for SLC and better than the automatic coregistration).
Why is this function “hidden” as internal graph? Could it be used as S1-TOPS-GRD-coregistration or I miss some important parts?
That is great! I try the operator and it seems to work well (at least with SRTM DEM). Are there any limitation using this function with the current implementation? Will it be available within the next realise?
I tried it out and the results are way much better than the automatic corregistration. The level of accuracy is comparable with the TOPS coregistration. The configuration was as follows:
GRDH image with precise orbits applied. SRTM bicubic interpolation for both DEM and image resemplig. I used SRTM 1sec. Area of application are Alps.
If it implements an algorithm that use the DEM and the (precise) orbits this I expect a better accuracy than an amplitude coregistration based on a first guess on the orbits.
May I miss something but to me it seems a good algorithm
Well there is not so much to measure: if I use automatic coregistration I obtain all NaN. If I use the stack tool with precise orbits I get ~5pixel shift between master and slave. If I use DEMAssistedCoregistraetion I obtain a subpixel accuracy (Visually it is impossible to see any shifts).
I used the following configuration:
GRDH image with precise orbits applied.
STACK: Initial offset method orbits for the stack. bicubic interpolation.
DEM assisted cor: SRTM 1sec for DEM. bicubic interpolation for both DEM and image resemplig
Area of application are Alp with the following images
The standard way to process would be to skip co-registration and directly terrain-correct, and then generate a stack from the terrain-corrected images. I tried this out with your images and they align perfectly.