yumorishita / LiCSBAS

LiCSBAS: InSAR time series analysis package using LiCSAR products
https://doi.org/10.3390/RS12030424
GNU General Public License v3.0
231 stars 110 forks source link

LOS decomposition to EW and vertical direction #163

Closed DaisyUoE closed 1 year ago

DaisyUoE commented 2 years ago

Hi Morishita, I am looking for a user friendly code/software to decomposition the LOS result from the LiCSBAS output. Do you have any suggestions?

Many thanks, Daisy

DaisyUoE commented 2 years ago

Hi, please see attached, thanks! Screenshot 2022-09-05 144003

yumorishita commented 2 years ago

n_loop_err is the cause of the mask. You should check 12loop/bad_loop_cand_png/*.png and 12no_loop_ifg_ras/*.png, manually identify the unw data with unwrapping errors, remove them from GEOCml*, and rerun from step11.

DaisyUoE commented 2 years ago

I have done the suggested step, and removed 20161020-20161107, 20161101-20161107, 20161107-20161201, 20161020-20161113, 20161113-20161201 from both /GEOCml1 clip and /GEOCml1 folder. However, the result ends up only has bit data in the middle, please see attached mask_ts.png Screenshot 2022-09-06 170927

yumorishita commented 2 years ago

You are showing the unclipped result in TS_GEOCml1. Run LiCSBAS again using the clipped data GEOCml1clip.

DaisyUoE commented 2 years ago

Thanks, I got a good result by rerunning it from step 03, instead of step 11. Now trying to apply GACOS.

DaisyUoE commented 2 years ago

Could I define the reference point when run batch_LiCSBAS.sh? I am trying to use the same reference point for both ascending and descending processing, then compare their time-series at the same location. Thanks! -Daisy

yumorishita commented 2 years ago

Please see this: https://github.com/yumorishita/LiCSBAS/issues/102.

DaisyUoE commented 2 years ago

Could you please advise on which command to define E.geo (N.geo)'s reference point. Because I am trying to define the descending results reference point match with ascending, then run LiCSBAS_decomposeLOS.py, thanks! -Daisy

yumorishita commented 2 years ago

E.geo is a LOS unit vector component and should have no reference point.

zhouhuayun commented 2 years ago

Hi, When I use LiCSBAS_decomposeLOS.py to obtain the deformation information of the vertical ground, I keep getting the following error (Figure 1). What is the reason? image

Figure 2 shows the txt document content required by-f of LiCSBAS_decomposeLOS.py. image

yumorishita commented 2 years ago

Both ascending and descending velocities are required.

DaisyUoE commented 2 years ago

Hi Morishita, Is it possible to regenerate the network figure? I found automatic generated network*.png at TS*/network folder. However, I would like to remove the notation of time at each SAR image dot. I have tried LiCSBAS_plot_network.py, did not find the input files 'ifg_list' and 'bperp_list'. Thanks, Daisy

yumorishita commented 2 years ago

'ifg_list' can be easily created, e.g., by

cd GEOCml1
ls -d 20*_20* > ifg_list

'bperp_list' is, e.g., GEOCml1/baselines.

DaisyUoE commented 2 years ago

Thanks Morishita, another question. Is there any way to find out the equation for the fitted sinusoidal curve of the time-series points (please see attached figure)? Picture1

yumorishita commented 2 years ago

The equation is coded here. If you want to get the coefficients of the model, please modify the LiCSBAS_plot_ts.py to print the coefficients.

DaisyUoE commented 2 years ago

I ran LiCSBAS_plot_ts.py, got a time-series text file output, in the file, it has linear model coefficients. However, no sinusoidal model coefficients. Please see attached picture. Picture2

yumorishita commented 2 years ago

I think you used LiCSBAS_cum2tstxt.py. Yes, it does not compute the coefficients of the sinusoidal model. You need to modify the source code of LiCSBAS_plot_ts.py.

DaisyUoE commented 2 years ago

baselines.

I managed to run the 'LiCSBAS_plot_network.py' successfully, however, the time notation of each SAR image automatically plotted. Is there any parameter I could use to remove the month/year notation at each plotted dots please? please see attached screen capture below. Screenshot 2022-10-18 104707

yumorishita commented 2 years ago

Comment out the followoing two lines. https://github.com/yumorishita/LiCSBAS/blob/dfdb8fadf323c821f386ed60eb0e871288961a72/LiCSBAS_lib/LiCSBAS_plot_lib.py#L264 https://github.com/yumorishita/LiCSBAS/blob/dfdb8fadf323c821f386ed60eb0e871288961a72/LiCSBAS_lib/LiCSBAS_plot_lib.py#L265

DaisyUoE commented 2 years ago

Thank you so much, I got it working based on your advice. -Daisy

DaisyUoE commented 2 years ago

Hi Morishita, I noticed there is a big gap in my descending network figure (please see attached). Is it ok to have a one year gap in network for SBAS-InSAR processing? The result seems still good, just worried about the reviewer are going to be picky about it. I am trying to figure out why there is a gap. First, I check COMET-LiCS website, the network has no gap there (please see attached). Then I run 'batch_LiCSBAS.sh' to process the data, the network has a gap in the result. I also checked my processing back in May, somehow, with the same workflow, no gap in the LiCSBAS result network. I am so confused. Daisy

1 2

yumorishita commented 2 years ago

It is quite strange. You should use all the available interferograms for the paper. Can you upload the log file?

DaisyUoE commented 2 years ago

Attached is the log file, thanks. -Daisy

202210202130batch_LiCSBAS_01_16.log

yumorishita commented 2 years ago

The reason of the missing dates is that you have the GAOCS data for the dates are missing. Please see the log in step03. You need to prepare them yourself or turn off the GACOS correction in step03.

DaisyUoE commented 2 years ago

Thanks for explaining the cause of the issue. If GAOCS data is missing from the server, how could I prepare them myself? In this case, do not apply GACOS correction in descending processing, a better choice? Or with GACOS correction, however with a GAP in network, a better choice? -Daisy

yumorishita commented 2 years ago

You can submit the GACOS request here. See this as well. GACOS correction to all interferograms would be required for the peer-reviewed paper.

DaisyUoE commented 2 years ago

I requested some GACOS to try to make it work. First, for the 'location' parameter, I put the latitude and longitude value that covers entire descending footprint. Second, for the 'time of day' parameter, I kept default 0:00 (any advice? please see Fig.4) Then the server back to me really fast, and I downloaded the data, rename it with the same name style as in GACOS folder, and add those files in the GACOS folder (Fig.2 and 3). After that, I rerun the workflow from step03, however, the result did not pick up the GACOS file that I added in (covers beginning of 2019), the gap still there (Fig 1 and log file). Please advise! 1 2 3 4

202210242138batch_LiCSBAS_03_16.log

yumorishita commented 2 years ago

The 'time of day' should not be 0:00, but be center_time written in metadata.txt or slc.mli.par (e.g., 0:19 for 019D_06217_131313).

What is the file name of the downloaded data? If it is .ztd or .ztd.tif, you should not rename it to .sltd.geo.tif because they are different. The .ztd or *.ztd.tif files can be used in step03 (see here).

Please see GEOCml*GACOS/yyyymmdd_yyyymmdd/yyyymmdd_yyyymmdd.gacos.png to check how the correction worked.

DaisyUoE commented 2 years ago

I requested the GACOS data again with time at 0:19, and did not change *.ztd.tif files name, kept as it was. However, still the GACOS did not apply through the newly added GACOS files. For example, the 20190102_20190207 correction is empty (please see attached figure). I also attached one sample GACOS file that already exists in the GACOS folder, another one is newly requested, maybe you could have a look at them to help find out what is wrong? Thanks! -Daisy 11

GACOS file1.zip GACOS file2.zip

yumorishita commented 2 years ago

The attached 20190102.ztd.tif seems to be normal. If you retried without removing existing GEOCml*GACOS/sltd/yyyymmdd.sltd.geo, please retry again after removing them because they are not overwritten if exist.

If the problem still exist, please attach GEOCml1GACOS/sltd/20190102.sltd.geo, 20181221.sltd.geo and EQA.dem_par.

DaisyUoE commented 2 years ago

After removing existing GEOCml*GACOS/sltd/yyyymmdd.sltd.geo, and it works. The gap caused by GACOS is gone. Please see Figure 3, and log file. There are two small gaps in the current network, please see figure 2. The cause of the gap are 'bad' pairs got removed, please see figure 1. Since it is caused by bad pairs, I do not think there are anyway to 'fill' the gap. Is it OK to have couple small gaps in the network for SBAS-InSAR result for the peer-reviewed paper? Thanks! -Daisy 3 2 1 202210291105batch_LiCSBAS_03_16.log

yumorishita commented 2 years ago

In my opinion, the gap is not a significant problem in this case because the deformation velocity looks constant before and after the gap. Of course, you need to clearly explain it in the paper.

irmayolii commented 1 year ago

Dear Prof. Yumorishita After we get EN/UD.geotif from processing LiCSBAS_decomposeLOS.py, can I generate specified point timeseries from EN/UD.geotif timeseries?

yumorishita commented 1 year ago

No, currently LiCSBAS has no function to do that.

irmayolii commented 1 year ago

so how do we know how big the shift is of EN/UD.tif in numerically, can we get file in txt about cumulative displacement or anything to exctract value from that?

araditiya commented 1 year ago

Please see this #39 It looks no clear the flow command for me, in order to get E/W, U/D. Could you help me to guide this issue. I success to execute the first command cum2vel and it generates 20151122_20221227.vel file. Then, I face an error in further step as follows,

saka@xps8930:~/work$ LiCSBAS_flt2geotiff.py -i 20151122_20221227.vel -p EQA.dem_par

LiCSBAS_flt2geotiff.py ver1.5.1 20210209 Y. Morishita LiCSBAS_flt2geotiff.py -i 20151122_20221227.vel -p EQA.dem_par Use gdal module Traceback (most recent call last): File "/home/saka/LiCSBAS/bin/LiCSBAS_flt2geotiff.py", line 213, in sys.exit(main()) File "/home/saka/LiCSBAS/bin/LiCSBAS_flt2geotiff.py", line 190, in main data = io_lib.read_img(infile, length, width, endian=endian) File "/home/saka/LiCSBAS/LiCSBAS_lib/LiCSBAS_io_lib.py", line 199, in read_img data = np.fromfile(file, dtype=dtype).reshape((length, width)) ValueError: cannot reshape array of size 63001 into shape (2515,2676)

saka@xps8930:~/work$

yumorishita commented 1 year ago

so how do we know how big the shift is of EN/UD.tif in numerically, can we get file in txt about cumulative displacement or anything to exctract value from that?

You can extract value from geotiff, e.g., by gdal2xyz.py.

yumorishita commented 1 year ago

@araditiya The size of the vel file seems to be inconsistent with what it should be. I cannot identify the cause from this limited information.

araditiya commented 1 year ago

@araditiya The size of the vel file seems to be inconsistent with what it should be. I cannot identify the cause from this limited information.

Thank you. It has solved due to file E,N come from different folder.

ditafaith commented 1 year ago

Hi, does it possible to decompose only from short period, says for each asc and desc 2 images (e.g. before and after EQ) ? Is there any minimum stack of images ?

yumorishita commented 1 year ago

I think it is possible.

ditafaith commented 1 year ago

I think it is possible.

It sounds good opportunity. Then, is it possible the licsbas read the output from snap software ?

yumorishita commented 1 year ago

Yes, if you convert the output to the proper format (see here).

ditafaith commented 2 months ago

@as1234554321 it looks difficult without additional information such as log file/ files.txt. You may check the input files, I guess.

ditafaith commented 2 months ago

@as1234554321 All geotiffs should be gathered into same directory where files.txt located in, then you might run the command.

as1234554321 commented 1 month ago

hello @ditafaith sorry for out of topic Are you Indonesian? If yes, I would like to contact you personally to discuss. thankyou