90d578fa5d
contrib/PyCuAmpcor/cuDenseOffsets.py: + expose --raw-over-samp-factor option to change the raw data oversampling factor with default of 2 + expose --corr-win-size option, which by default, is calculated automatically based on the search window size and raw oversampling factor + change the namespace key for the oversampling factor of correlation surface from 'oversample' to 'corr_oversample' to avoid ambiguity, the cmd option name is still the same, thus no different in the user side. + use vrt file for master / slave slc data loading folllowing https://github.com/isce-framework/isce2/pull/78 + re-organize createParse() for readability + add example to argparse help stripmapStack/MaskAndFilter.py: + fix a bug introduced in #https://github.com/isce-framework/isce2/pull/112 + add example usage to help message + mask pixels with SNR == 0, for plotting only without touching data files + show input parameter in the figure title + show percentage after SNR thresholding + add interpolation for matplotlib while plotting topsStack/grossOffsets: move obsolete basemap import from the top to the related commented code block |
||
|---|---|---|
| .. | ||
| stripmapStack | ||
| topsStack | ||
| README.md | ||
README.md
Stack Processors
Read the document for each stack processor for details.
Installation
To use the TOPS or Stripmap stack processors you need to:
-
Install ISCE as usual
-
Depending on which stack processor you need to try, add the path of the folder containing the python scripts to your
$PATHenvironment variable as follows:- add the full path of your contrib/stack/topsStack to
$PATHto use the topsStack for processing a stack of Sentinel-1 TOPS data - add the full path of your contrib/stack/stripmapStack to
$PATHto use the stripmapStack for processing a stack of StripMap data
- add the full path of your contrib/stack/topsStack to
Note: The stack processors do not show up in the install directory of your isce software. They can be found in the isce source directory.
Important Note:
There might be conflicts between topsStack and stripmapStack scripts (due to comman names of different scripts). Therefore users MUST only have the path of one stack processor in their $PATH environment at a time, to avoid conflicts between the two stack processors.
References
Users who use the stack processors may refer to the following literatures:
For StripMap stack processor and ionospheric phase estimation:
- H. Fattahi, M. Simons, and P. Agram, "InSAR Time-Series Estimation of the Ionospheric Phase Delay: An Extension of the Split Range-Spectrum Technique", IEEE Trans. Geosci. Remote Sens., vol. 55, no. 10, 5984-5996, 2017. (https://ieeexplore.ieee.org/abstract/document/7987747/)
For TOPS stack processing:
- H. Fattahi, P. Agram, and M. Simons, “A network-based enhanced spectral diversity approach for TOPS time-series analysis,” IEEE Trans. Geosci. Remote Sens., vol. 55, no. 2, pp. 777–786, Feb. 2017. (https://ieeexplore.ieee.org/abstract/document/7637021/)