SARPROZ ©

Hello Daniele,

I’m interested in getting this information too. I exported the Synthetic Amplitude via the Time Series Module and would like know whether its values are the normalized ones you mention to Ivana.

I enclose the created CSV file. As you see the values for the first date are always 0. Why? Is it the Synthetic Amplitude the correct…[Read more]

Hi Daniele,

Yes, you are right! I confused the terms. I know that what I’m seeing are amplitude values,

Thanks for the description and the info,
S

Hello Daniele,

I ask you again about the YYYYMMDD fields but this time in the .csv file created from the Small Area processing.

According to what I see it seems that they contain the single displacement for each date instead of the cumulative one (in the field corresponding to the master image eveything is 0, that’s why I think this is the…[Read more]

Yes, this question regards APS processing (and Sparse Points processing too), and yes, there is a particularly rapidly moving point (in comparison to the others), with which I didn’t mean that the rest or the points are stable, but moving slower instead. It is a landslide area where only few points (among them the Corner Reflectors) are identified…[Read more]

Ok, I’ve visualized it and it is wrong, all zero values. The command prompt tells me this:

” wrong saturation values!” Must be NaN < Min < Max < NaN”

I reselected the DEM, I manually re-wrote the GCP and projected again the DEM amplitude in SAR coordinates. Still seeing all zeros in SAR coordinates.

What should I do?

Thanks,
Santiago

Dan,

I’ve checked it with the DEM Visualization tool (screenshot attached), finding no NaNs, but according to the manual this displays the DEM in Geo coordinates, which file corresponds to the DEM in SAR coordinates?

Santiago

I enclose my log file,

I remember that when you warned me about NaN values in my DEMI checked it and I converted them to zero.
When I made that correction I restarted the process again from the external DEM selection to make sure it was updated.

Santiago

Lasterror.mat was not attached in the previous message,
S

Hi dan,

Then it is desirable to ckeck it even if estimating displacement only (from what you say I interpret that it is used to remove the topographic phase reding it from my DEM, which in this case is a high-resolution one).

I have tried to re-process my dataset again with this option checked, and apart from taking too long (~8 hrs) I can’t…[Read more]

Ciao Dan,

Here the names of two of the images:

S1A_IW_SLC__1SDV_20160104T052642_20160104T052709_009340_00D80F_1E18
S1A_IW_SLC__1SDV_20151223T052642_20151223T052709_009165_00D311_E59E

I know this is not the propper place to ask this, but have you experienced recently problems to download Sentinel-1 data?

Thanks,
Santiago

Then, the cumulative displacement shouldn’t be equal to the displacement for the last acquisition?

I give you a concrete example:

20120803 (First Acquisition): 0.00
20120819: 0.43
.
.
.
20150112 (Last Acquisition): -14.53 —-> This is the displacement of 20151212 respect to 20120803??
CUMULDISP: -15.54

Hello Daniele,

I have a doubt regarding the fields YYYYMMDD (created with the time series option) which seem to be showing displacement values. These values refer to a cumulative displacement (i.e. the cumulative displacement at date 20010721) or to the single displacement registered for that acquisition (in that case, respec to to whom or when?…[Read more]