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

Strange Uplift results in SBAS #255

Closed
soroushyasini opened this issue Jun 12, 2023 · 8 comments
Closed

Strange Uplift results in SBAS #255

soroushyasini opened this issue Jun 12, 2023 · 8 comments

Comments

@soroushyasini
Copy link

soroushyasini commented Jun 12, 2023

Hi Mr. Morishita. I implemented 439 interfrograms and corrected them by 121 GACOS data of frame 174A_05598_131313 from 2020 until 2022. After removing DEM and orbital ramp error, the shown subsidence patterns seems alright but there are significant uplifts in the area which we do not expect them according to local and field data. is there any idea to improving the results ?
I upload some of the results here. I also attached a Profile of the area which has shown uplift significantly.
vel filt

network13
coh_avg
vstd
1

@yumorishita
Copy link
Owner

Where is the unexpected uplift area you mean? Also please show mask_ts.png.

@Sakina-A
Copy link

Sakina-A commented Jul 7, 2023

Hi Morishita

I would like to ask about the upward velocity. According to the results, the upward velocity corresponds very well to buildings (urbanization) in my study area but because the velocity is in mm/year it cant be explained by an increase in the buildings heights (and its too good to be a coincidence that a surface rebound due to subsurface recharge is happening in the exact location of urban areas) so:

1- Is the velocity calculated based on a reference area/points? meaning that if this reference area/points experienced subsidence will this lead to an uplift in areas with the no movement?

2- If the velocity is not calculated based on No.1 above, then how the upward velocity can be explained in terms of how LiCSBAS works?

Study area

mask_ts

@yumorishita
Copy link
Owner

No. 1 is correct.

@Sakina-A
Copy link

Sakina-A commented Jul 9, 2023

Got it. Am just a little confused about somethings, so please correct me if I'm wrong:

1- The reference point (chosen by LiCSBAS) is the point selected with the least amount of error for the SB network inversion to calculate the velocity. So, is the reference area (black dashed rectangle) also selected in the same way?

2- According to your reply #249 (comment), the reference point is forced to be zero. Hence, how can I find the amount of displacement at this point so that it can be subtracted/added to the rest of the cells to explain the upward velocity? Do I compare it to the actual displacement at the exact point and time?

@yumorishita
Copy link
Owner

yumorishita commented Jul 9, 2023

  1. No, the reference point is selected again in step16. Please read this.
  2. The displacement of the reference point is already subtracted from the rest of the points (that is why the displacement is zero). You can manually set the reference area or point. Please see Reference Point #102.

@Sakina-A
Copy link

Thank you for clarifying No.1
Regarding No2., what I mean is there a way to know the amount of subtraction before it is applied (the amount of displacement at the reference point before it was set to zero)?

@yumorishita
Copy link
Owner

All the displacement is a relative value and the displacement value with no reference has no meaning. Therefore, there is no absolute displacement value at the selected point before selecting the reference point. If you set the reference at another point, you will find the non-zero displacement at the previous reference point.

@Sakina-A
Copy link

I understand now, thank you. I chose a new reference area based on your explanation and checked its indices and got reasonable results.

_Cumulative_Displacement

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

3 participants