SARPROZ ©

Hi Estelle,
unfortunately the Matlab version you are using does not allow us debugging errors.
My feeling is that you should kill everything, try again and it may work. If not, we need to look at that together via remote connection.
Best
dan

This is not a coregistration error, it’s a java problem
are you sure you are starting matlab from the pcodes directory?

EXT folder, there is a directory for each image
inside those directories you can find a text file yyyymmdd.meta (careful, there is also a .meta.mat file).
You can derive R0 from the Range Start Time that you find there.
otherwise, type “fast” in matlab (without quotes) hit enter and then:
R0=leggi_img(handles.SiteParam.DirSite,Master,{‘R’})

At the moment you can use a polygon at a time and generate 2 masks. Then, either you merge them in matlab or you can use the scatter plots and say “mask1 or mask2”. if you send us the kml, we’ll improve the code for importing MultiGeometry objects

The coregistration refinement is doing 1 single operation:
it is taking the external DEM and it is using it to resample the image by correcting topographic distortions.
In other words, the sw is not going to re-process the cross-correlation between patches, this was already done during the initial co-registration (and this is the reason why it…[Read more]

To check if the process was well concluded,
you just need to plot the external DEM in SAR coordinates with the “view parameters” function.
Also, to check your original DEM, you should plot it with “DEM visualization”.
But surely the process failed, if you look in the log file, you got a considerable amount of errors.
Probably your DEM is in UTM…[Read more]

A first question would be: did you select points representative of the area where they are located or did you choose outliers?
Secondly, the software decomposes asce/desce velocities only on AD pairs. AD pairs are points located closely in A/D datasets. The sw selects them based on your inputs (AD processing) and based on the corrected shifts…[Read more]

Can you please post an example?

Hi Cecilia,
to find out where is the sign problem, I’d suggest you to find a case where the Asce and Desce velocities have opposite sign.
Where A is + and D is -, the point must move to the W. If the plotted result is positive, it means that the E-W component was assumed positive to the W. If you can confirm it, we will change sign and change the…[Read more]

Hi leewoneung,
I am sure that the guys in Beijing will be able to check the matter with you.
good work

This is a similar discussion:
https://www.sarproz.com/groups/sarproz-group/forum/topic/import-sentinel-1a-data/

and in this link one can see the correct folder tree:
https://www.dropbox.com/s/k4odh9ye4k422in/Screenshot%202017-09-29%2019.12.36.png?dl=0

Hi Dimitris,
1. please take the time to read the messages from the software. You can learn a lot from them. They are included in the log file you attached.
2. one of the messages says: “If you need assistance, please include the file lasterror.mat “. without that file we cannot help.
3. here you have some material to learn how to use the software…[Read more]

Hi Joana,
such message is a warning, not an error. The log also says that the file you cannot modify is a file contained in the original SLC data, and this is not a problem, since the software is not going to overwrite those files.
Your problem is that your SLC data are partial or corrupted. The log says:
Error in s1_slc2file(): can not find…[Read more]

Hi Antonio,

If you restart the software,
you should get a different message, did you try it?
Something else to try:
(1) open a terminal (2) type ‘hostname’ (3) ping the returned name (eg: ping mycomputername)
(4) if no packets are received, add the name returned by ‘hostname’ to the file /etc/hosts

When sarproz process the coregistration,
the estimated offsets are saved in _coreg_offL and _coreg_offS files in the EXT folder.
These files could be loaded into sarproz (by selecting “choose a real file” from the menu that you can find in most modules)
And you could analyze pixel offsets.
However, at the moment these offsets contain also the…[Read more]

InSAR is by definition relative to a reference point. So, everything is calculated by subtracting the value corresponding to the reference point.
Residual height is the height relative to a reference DEM. Height = external_DEM_height + residual_height.
The deviation of the height estimation depends on many things, as number of images and baselines…[Read more]

You are on the mountains and you are geocoding your data, not orthorectifying it.
You should orthorectify it instead.

1. check that you have a DEM correctly loaded. to check it, you can click “dem visualization” in the frame “preliminary geocoding” in “site processing”. if you get a green flat picture, probably it failed downloading SRTM data (you should have got messages about that). In such a case delete the corresponding SRTM files (SRTM directory in the…[Read more]

Hi Cecilia,
yes, on the manual you find some explanation, here in particular http://sarproz.com/manual/geocod.html
what you have written is correct if no correlation with temperature was estimated. If on the contrary you did remove a temperature-correlated trend, then you have to tick on the corresponding box to see it, otherwise it is removed…[Read more]