Vertical and Horizontal Displacement
oguzhannysr opened this issue · 9 comments
@Alex-Lewandowski @khogenso @piyushrpt Hello, first of all, thank you for the work done. Within the scope of Opensciencelab, I processed my human data with h3py + mintpy notebooks and created displacement maps in the LOS direction. However, using my results from ascending and descending orbits, I want to separate the LOS direction into vertical and horizontal components. Can you help, if there is any solution for this I may have missed it.
You should check out MintPy's asc_desc2horz_vert utility. I believe it will do what you need.
@oguzhannysr I second Forrest's recommendation. Additionally, we have recently replaced the MintPy notebooks in this repository with the opensarlab_MintPy_Recipe_Book, which is also available in OpenSARLab.
We have plans to eventually add a notebook to the "Extras" chapter to demonstrate use of asc_desc2horz_vert script, as it has been a frequent request.
@forrestfwilliams @Alex-Lewandowski Thanks for your help. I couldn't figure out how to use the asc_desc2horz_vert.py file. I ran opensarlab_MintPy_Recipe_Book on both orbits and got all my results. I want to perform vertical and horizontal separation for each displacement produced (result files in the geotiff file). In addition, I read in another discussion that this py file is compatible with ISCE, but not with GAMA.
@forrestfwilliams @Alex-Lewandowski usage: asc_desc2horz_vert.py [-h] [-d DS_NAME] [-g GEOM_FILE GEOM_FILE]
[--max-ref-yx-diff MAX_REF_YX_DIFF]
[--az HORZ_AZ_ANGLE] [-o HZ_FILE UP_FILE]
[--oo ONE_OUTFILE]
file file
For example, which result files (opensarlab_MintPy_Recipe_Book outputs) should I use for the input data here?
@forrestfwilliams @Alex-Lewandowski I am waiting for your help, thank you very much.
Hi @oguzhannysr,
OpenSARLab has seen a recent increase in questions regarding asc_desc2horz_vert.py, so I will take some time to look into it more next week. It is possible that we will need to do a little work to get it running on GAMMA InSAR data.
Forrest linked to the python module in his comment, however there is also a CLI (https://github.com/insarlab/MintPy/blob/main/src/mintpy/cli/asc_desc2horz_vert.py) that contains some example workflows for using the tool in the comments. It suggests that you could call it with something like: asc_desc2horz_vert.py hyp3_gamma_sbas_ascending/MintPy/velocity.h5 hyp3_gamma_sbas_descending/MintPy/velocity.h5
@Alex-Lewandowski Thank you very much for your efforts. I will be waiting with curiosity. My goal will be to parse each displacement map in the Geotiff result folder in vertical and horizontal directions. I would like to do it for Velocity as well, but what I really want is for displacement maps.
@Alex-Lewandowski Hello, any news? Thank you.
Hi @oguzhannysr,
I was able to use asc_desc2horz_vert.py on HyP3 INSAR_ISCE_BURST data. It should work on HYP3_INSAR_GAMMA as well. Once the dataset is loaded by MintPy and a time series is produced, the script should be able to use it.
To run the script, you should first prepare two time series meeting the following requirements:
- They have overlapping spatial extents
- They have the same spatial resolution
- They have close to the same reference point (within 3 pixels)
- The 3 pixel maximum allowance can be adjusted with the
--max-ref-yx-diffargument
- The 3 pixel maximum allowance can be adjusted with the
- One dataset should be in the ascending orbit direction
- One dataset should be in the descending orbit direction
- They share a temporal range
- Warning: the script will run on time series whose temporal ranges do not intersect at all, and provide (probably meaningless) results. This makes me think that it does not account for datetimes, and it may not be safe to pass 2 time series whose temporal ranges differ by much but still overlap. This requires further investigation.
Another warning: the script will handle different but intersecting spatial extents, however it will leave non-decomposed, LOS velocities around the edges as seen below:
