TopSAR Processing

according to @mengdahl 's post here, this should be no problem. The only thing to watch out fro is the selection of bursts in the Split operator.

1 Like

Yes, I agree with you and that what, I said, but in case the burst cover the AOI, are match each other in both frames,

hi team,
I’m trying to do land displacement analysis, by following the steps as discussed above while doing the topographic phase removal the output is having the some NaN values like below images

is it correct or not? please help me.
I’m just surprising by getting NaN values like that sequence, please help me.
thank you in advance.

Which DEM did you select?

Be sure that the autodownload selected DEM is covered your study area,

I did select the appropriate bursts from each frame and it worked fine actually for now.

I just want to another another question.

When doing Phase to Displacement (in SNAP), is the displacement already in the vertical direction or is it in the LOS of the satellite?

Thank you.

The displacement is in LOS, but it is possible to get the vertical displacement, it is well explained in this post,

Source of the post

And in this post as well,

Source of the post

1 Like

Thank you! I did use the formula given as shown in the two posts. I just want to confirm if vertical measurements are always larger than LOS measurements?

Also, can I use some kind of scripting in SNAP to get the pixel information instead of using some drawing tools?

Thank you.

In general the equation is used to convert LOS to Vertical, showing that the vertical disp. depends on the cos of the incidence angle,

Source

But according to the Zhong Lu Daniel Dzurisin, 2014 LOS, is more sensitive to vertical dis. uplift and subsidence, which is your case,

image

But according to my experience and the other discussions from earlier posts in here Source of the post

The atmospheric effects has the large pack of the increasing the amount of real disp.

I didn’t quit understand what do you mean scripting in here, but in general you use pixel info and get the information of any pixel by pointing on it,

1 Like

So, it is normal to get somewhat larger vertical measurements (VD) than the LOS measurements. In my case (using the given equation), I have a maximum difference of about 1cm (VD > LOS). I thought before that LOS measurements will always be larger than VD measurements.

I am measuring a longitudinal surface displacement of a road. I have used the cursor to move around the area to get the pixel information as well as using the line drawing tool. I did it several times for a number of pairs (14). I have the results already. They looked okay actually. But my supervisor, asked me if instead of doing this several times, if I can use a written script (say in Python) to get the pixel information along the line of pixels (road line) I am interested in. For example, in QGIS, I can call Python to do some tasks for me as long as I have a script.

Actually I’m new learner of python, but you could use the pins and then export the values of each one corresponding of all your products,

Since SAR sensors are side-looking, it is the vector sum of both the vertical and horizontal components along the line of sight (LOS) that can be measured, creating some ambiguity in separating the two elements.

A displacement in the vertical direction will induce a displacement SMALLER when projected in the LOS direction. However a LOS displacement cannot guaranty that the displacement in indeed vertical.

I can take a example. In glaciology, when studying ice-sheet displacement, the ice-flow mostly follows the topography, which is very flat in some regions. You can observe by DInSAR a displacement. however, you know that this displacement in the LOS direction is due to horizontal movement instead of vertical.

I hope it helps.

Yes, using pins is another option. I didn’t answer my supervisor yet, but I think he will push me using script to extract the pixel information even if I am used to the drawings tools already.

One more thing, which do you recommend to report?

  1. the pixel information taken from exporting the mask pixels, or
  2. the pixel information taken from ‘Analysis --> Profile Plot’. I copied and pasted in excel the ‘mean’ values from the tabulated results.

I do get different values of displacements from the two extractions. But not that much.

Thank you.

Different approach of extracting the values shouldn’t change the original value,

I was expecting that before but I was surprised when I plotted the results for comparison.

Here are screenshots from the ‘Analysis --> Profile Plot’.

I think the blue region shows the upper and lower limits (computed by sigma method?) and the dark blue line is the mean value. My band is named: vert_displacement_VV. Then I do get (not my own) the last two columns with _mean and _sigma.

When I move the cursor to the pixels of my interest, and compare the values from those extracted using the line drawing tool (in .txt), there’s no difference.

Please, enlighten me about this one.

Vertical displacement mean, is the average of the disp. of all the corresponding dates of the selected point, while sigma, refers to the standard deviation of the assessed disp.,

I see. Thank you for this information. I will revisit each pair I have.

I also would like to ask the following:

Say I have an area that doesn’t move vertically up nor down, meaning zero surface displacement at any time instant as supported by field measurements. Is it possible that when I do DInSAR, I will get non-zero displacements?

This depends on many factors,
What kind of area is it? ,
What kind of objects cover this area? ,
Is the processing 100% right?
Are the atmospheric’s effect excluded 100%?,
Dose the topographic phase is still related to the Perpendicular Baseline (PB) ?
Is the unwrapped step done correctly?

I am covering a road line, about 280m long, that is about 600m away from my main AOI, which is a road also suspected to have longitudinal surface displacement due to a tunneling activity. These 2 roads are parallel with one another.

For the processing, I think I did it correctly.

  1. S1 TOPS Coregistration with ESD (includes S1 TOPS-Split and Apply-Orbit-File)
  2. Interferogram Formation
  3. S1 TOPS-Deburst
  4. Subset
  5. TopoPhase Removal
  6. Mutlilooking
  7. Goldstein Phase Filtering
  8. Phase Unwrapping (SNAPHU Export and Import)
  9. Phase to Displacement
  10. Range-Doppler Terrain Correction
  11. Extraction of pixel information using the line drawing tool to get Profile Plot

I am not sure about atmospheric effect exclusion, and relationship between topophase and PB.

I think in this case the better solution is to apply SBAS technique, to detecting the ground stability of this area using long-term data of two years S-1 (for example).

Could you tell me briefly why DInSAR may not give reliable results for this problem?

Below is the results I obtained by DInSAR for my main AOI.

We believe the tunneling activity started in early/late December but we got displacements prior to December. That is why I have considered a road far from my main AOI to check the results prior to the month of December. At first, I expected all displacements will converge but unfortunately, they are not after plotting the results.