Right now it appears that the geocoded outputs match the resolution of the input dem (30x30 m). We will want to customize the output pixel resolution for each multilook combination like this:
Multilook
Geocoded Resolution (m)
20x4
80
10x2
40
5x1
20
This will likely need to be accomplished by creating a DEM with the target resolution specifically for geocoding.
Explored this a bit and found there are two issues at play.
ISCE2 uses the resolution of the DEM we specify as the geocoding DEM to set the resolution of the output products, we'll need something like this DockerizedTopsApp implementation, but using gdal instead of rasterio
Fixing the first issue will fix the majority of the problem, but we will need to think carefully about how we set the resolution for the geocoding DEM. ISCE2 requires the geocoding DEM to be in EPSG:4326 (lat/lon), but the same EPSG:4326 resolution will translate into different UTM (meters) resolutions depending on where the data is located on the earth. This effect can make the resolution vary by at least 4 meters. To fix this, we will need to calculate a unique lat/lon geocoding resolution for each InSAR job based on its location.
Right now it appears that the geocoded outputs match the resolution of the input dem (30x30 m). We will want to customize the output pixel resolution for each multilook combination like this:
This will likely need to be accomplished by creating a DEM with the target resolution specifically for geocoding.