SNAP + MintPy workflow

[yunjunz]

Originally posted by @andretheronsa in https://github.com/insarlab/MintPy/wiki/SNAP-input-data

SNAP is a popular application to process SAR data. It allows for the creation of all the required input data for Mintpy. Therefore if MintPy can read this data it becomes possible to apply Multi-temporal InSAR and atmospheric correction to SNAP outputs. SNAP processing can be done manually, in the command line, or using the SNAP python API allowing for automated scripts.

An effort has been made in MintPy to integrate the outputs of SNAP directly for ease of processing. Unlike the SNAP extensional export for PSI with StaMPS, MintPy reads the native SNAP .dim files directly. This makes it possible to generate input files in SNAP and ingest them directly into MintPy. The recipe below should work as long as the correct workflow is followed. The aim is to make the world of open-source multi-temporal InSAR more user-friendly.

Notes

• Only limited testing has been done on prep_snap.py. It is possible that different SNAP workflows would not create a .dim file that is not expected by the script. This is because prep_snap.py tries to extract attribute files from the .dim XML file using simple parsing which might be sensitive to different workflows. The script was developed on data prepared by the workflow detailed earlier using Python / SNAP / snappy.
• Only geocoded (SNAP terrain correction step) data are supported so far. However, support for datasets in radar geometry should be easy to add.
• Only tested on Sentinel-1.
• No formal comparison/assessment has been done yet. Use it at your own risk.
• We want your help! This page is by no means comprehensive. Contributions in terms of notes, explanations, screenshots, tips, etc., are highly desired. ANYONE could edit this page.

SNAP Workflow

This workflow makes it possible to work with an area of interest covered by any combination of Sentinel-1 bursts / swaths / slices. It should be done for the entire redundant interferogram network of reference and secondary scenes.

1. Read reference and secondary data
2. Reference and secondary slice assembly (if required for sentinel-1)
3. Reference and secondary Apply orbit file
4. Reference and secondary Split product (extract relevant polarisation and subswaths)
5. The following is done per subswath [IW1, IW2, IW3]
   • Back-geocoding co-registration (write baseline attributes)
   • Enhanced spectral diversity (if more than one burst is present for Sentinel-1)
   • Interferogram generation
   • TOPSAR Deburst
   • Topo-phase removal
   • Goldstein phase filtering
6. Merge subswaths of flattened and filtered interferogram products (if more than one swath was done)
7. Subset by band and extract interferogram (This is the first MintPy input product - optional)
8. Add elevation band to co-registered product (must be done here to capture baseline attribute data)
9. Subset by band and extract only the elevation band (This is the second MintPy input product)
10. Generate Coherence
11. Subset by band and extract coherence (This is the third MintPy input product)
12. Snaphu export interferogram
13. SNAPHU phase unwrapping (external program)
14. Snaphu import and save unwrapped product (This is the fourth MintPy input product)
15. Terrain correct all four Mintpy products
16. Subset all four MintPy products by region - this must be done after terrain correction to ensure identical extents.

The resulting directory should have a structure similar to the example here, which also includes an example template file. Each .dim file should only have one band. The rest (running smallbaselineApp.py) is the same as shown in the example dataset.