Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Does this code have splicing function #147

Closed
ThreeIcug opened this issue Apr 28, 2022 · 6 comments
Closed

Does this code have splicing function #147

ThreeIcug opened this issue Apr 28, 2022 · 6 comments

Comments

@ThreeIcug
Copy link

Dear author,
LiCSBAS have provided a very convenient and fast method to get the time series of InSAR. Because the earthquake happened at the junction of the two images. A single image can't show all of the influence region. Does this code have a splicing function. I read the wiki ,but i can't find it.

@yumorishita
Copy link
Owner

The input GeoTIFF files can be merged by gdal_marge.py.

@ThreeIcug
Copy link
Author

Thank you for your timely help.

@ThreeIcug
Copy link
Author

I think the script can merge the cc , unw and the other .tif file. The cc and unw can named as same as the old, but what names should I give to the geo , mli and hgt file. In addition, how to deal with the baselines and metadata.txt file.

@yumorishita
Copy link
Owner

I think either name should be OK for mli etc. though I have never tried merging. I also realized that there could be phase biases between unw files and they should be removed using overlapping areas.

@ThreeIcug
Copy link
Author

Yes, I merge the data, the problem that you realized is happened.
Screenshot from 2022-05-07 22-55-47
How can I remove the phase biases.

@yumorishita
Copy link
Owner

Compute the phase difference in the overlapping area and its average (e.g., by gdal_calc.py), then subtract the average from the one data. I am not sure if this works well.
Otherwise, you could produce the interferograms covering the area of interest from the SLC yourself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants