KJ135
/
ISCE_INSAR
mirror of http://172.16.0.12:5000/WBJY/ISCE_INSAR.git
4
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
ISCE_INSAR/contrib/stack
History
Zhang Yunjun 31bb73ba95
various bugfix for topsStack (#500) 
* stackSentinel: add compute arg group and simplify main()

+ createParser(): add compute sub group for more organized print out msg

+ main():
   - remove the unsed inps.workflow value checking, as it's covered in the argparse
   - move the update stack date list checking insidie selectNeighborPairs()

* topsStack/mergeBursts: bugfix for float outY/XSize and gdal

+ mergeBursts.py: bugfix for the gdal call when outY/XSize is not integer by
   - set width/height to integer
   - add srcWin argument

+ mergeBursts.py: repeat gdal.Translate call as a workaround solution to the following gdal issue:
   - ERROR 1: Input and output dataset sizes or band counts do not match in GDALDatasetCopyWholeRaster()
   - the issue happens to version 3.3.3 and 3.4, but not in 2.3

+ unwrap: bugfix for intendation inconsistency

+ invertIon: print out num of pairs/dates

+ stackSentinel:
   - sort orbit date for downloading
   - add missing stackReferenceDate arg to selectNeighborPairs() for update mode

+ README: add link to stack processor readme for quick navigation.

* bugfix by removing existing *.hdr files

+ remove existing *.hdr files, to avoid gdal error, instead of repeat the gdal func call

+ replace the gdal_translate cmd call with gdal.Translate() in python.

+ add progress_cb() from stack overflow to printout progress bar in gdal.Translate() call
 		2022-06-17 11:00:13 -07:00
..
alosStack Replaced logger.warn to logger.warning, changed *.hgt* to *.hgt and updated RelaxIV download link (#332) 2021-09-09 11:05:12 -07:00
stripmapStack fixImageXml: support multiple files w/ wildcards (#439) 2022-06-10 13:19:50 -07:00
topsStack various bugfix for topsStack (#500) 2022-06-17 11:00:13 -07:00
README.md new alosStack application 2020-11-07 16:06:02 -08:00

README.md

Stack Processors

Read the document for each stack processor for details.

Installation

To use a stack processor you need to:

  1. Install ISCE as usual

  2. Depending on which stack processor you need to try, add the path of the folder containing the python scripts to your $PATH environment variable as follows:

    • add the full path of your contrib/stack/topsStack to $PATH to use the topsStack for processing a stack of Sentinel-1 TOPS data
    • add the full path of your contrib/stack/stripmapStack to $PATH to use the stripmapStack for processing a stack of StripMap data
    • set environment variable $PATH_ALOSSTACK by doing: export PATH_ALOSSTACK=CODE_DIR/contrib/stack/alosStack to use the alosStack for processing a stack of ALOS-2 data

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: