Adding InSAR processors to isce image

[grallewellyn]

Options would be:

1. Figure out how to manually create the InSAR processors for the isce3 image (if possible) and document this process for users (ideal approach)
2. Correct the isce2 image and manually create the InSAR processors. Related to this ticket: https://github.com/MAAP-Project/Community/issues/1022

We are all still unclear about the process manually creating the InSAR processors after the MAAP MSFC-JPL teams meeting 7/15

• The ISCE2 package in conda-forge channel is missing stack processors https://github.com/conda-forge/isce2-feedstock/issues/48
• Narayanarao chose to build ISCE2 from the source using scons, which will provide all the functionalities "InSAR stack processors."

From Narayanarao:

If I understood it correctly, InSAR processing functionalities in ISCE3 are more focused on NISAR data format.

1. Therefore, one has to convert all other sensor data (For instance, I am using Senitnel-1 and ALOS-2 data ) into NISAR RSLC format.
2. With converted RSLC, we have to create a configuration file for each InSAR pair. The second step looks like it can be registered to a DPS algorithm with a little effort, though one has to build their own stack. However, the first step of converting all the input SLC data into NISAR HDF5 format is a little concerning to me (given the diversity in the sensor data formats and mode of acquisition) and has unnecessary computational overhead. Therefore, I am not sure which would be an effective solution. Getting an ISCE2 image or converting the input data every time into NISAR HDF5 format. Given the situation, I think preparing an ISCE2 image would be ideal.

Sam Niomoeller is the UWG POC for this ticket

cc @wildintellect

[grallewellyn]

Gustavo confirmed we will probably need to use isce2

You are right, the if the inputs are not formatted in the NISAR format, you'd need to convert/repackage them to that format first. As Sam pointed out, ISCE3 includes a script to repackage ALOS-2 SLCs (L1.1) in stripmap mode to the NISAR format. We also have another script to repackage ALOS-1 Raw data (L1.0) to the NISAR format. Some UAVSAR datasets distributed through the UAVSAR website are also provided in the NISAR format. Unfortunately, the scripts to convert/repackage UAVSAR and Sentinel-1 data to the NISAR format are part of a library called SimulationTools, that is not publicly available. So, if you need to generate a stack of Sentinel-1 interferograms, you'll probably need to use ISCE2.