SARPROZ ©

Let’s make an example:
you have processed your dataset, and you got the following outputs (after APS and sparse points processing):
– Integrated Residuals APS
– height and velocity for each PS
So, you go to sparse point geocoding and the sw opens up the “sparse points processing” window asking you to input the processing options. Then you have…[Read more]

can you include a picture of the APS processing module, so we see which options you picked up?
tell us also which images graph you are using for the estimate

Hi Shimin

first of all, thanks for the question, I discovered an obsolete piece of code.
DBF is in fact an old option that was supposed to be replaced by simple CSV files.
However, I discovered now that the CSV is produced only if you check the “time series” option.
If you geocode the DBF without checking the “time series” option, a DBF file is…[Read more]

Hi Shimin

first of all, thanks for the question, I discovered an obsolete piece of code.
DBF is in fact an old option that was supposed to be replaced by simple CSV files.
However, I discovered now that the CSV is produced only if you check the “time series” option.
If you geocode the DBF without checking the “time series” option, a DBF file is…[Read more]

Hi Farnoosh

Residual Height = Height – External DEM

Removing an external DEM should reduce the unknown height (with “unknown height” I mean the source of the topographic component of the interferometric phase). Removing an external DEM is particularly useful in mountainous areas (the external DEM can decrease significantly the range of the…[Read more]

for this very moment I suggest you to apply a conversion with some other sw for manipulating geotiff files
in the future we’ll modify our code

As I said, you have 2 options:
a. get SLC data (not RAW)
b. focus them with roi-pac (or gamma)

any other way is possible but currently not supported

In the GCP selection module there is a flag: ‘OVW’ which stays for “overwrite”.
If you do not flag it, it will load the previous “mean kml” map.
Since you are not the first one asking about it, I switched it to checked as default…
You’ll get it in the next version, for the moment just check it manually.
dp

Question for you and for all geotiff users:
is anybody needing an RGB DEM?
Or can I switch the system to automatically (and always) output geotiff DEM files in “black and white”?
After getting a feedback on this, I just need to change 1 line…
thx
dp

hi Yuyu,

as you can read in the sw specifications, sarproz accept SLC data as inputs, that is, focused data.
Level 1.0 is raw data, and it cannot be imported.
You can either order again your data, asking for level 1.1 (SLC or focused) or use an other software to focus it (as roi-pac)
d

Hi Milan,

the key question is: in which format is your DEM?
if it’s geotiff, nothing to do (unless you find the way to re-write the geotiff).
The sw reads the fill-in boxes only if you are loading a matrix in gamma-format (read the manual).
In that case, changing the lat-lon coordinates has the wished effect.

To understand the error message you…[Read more]

Hi PY,

my suggestion would be first of all to look at interferograms.
case A. you have no coherence. Then the question is: is it on the mountains?
case A1. yes it’s on the mountains. Then download the last sw version and use the DEM-dependent coregistration refinement. This module requires a well aligned DEM. And it still needs some optimization…[Read more]

download the last pcodes (through the “manage version” module), I included a version check and an automatic choice between flip and flipdim

this is a new matlab function: flip.
if you get an error, it means u do not have it, that is, u have an older matlab
I’ll insert a simple version check.
U can quickly solve it by copying and renaming the function “flipdim” to “flip”

IMPORTANT NOTE:
to upload mat and log files, please zip them.
Without them I cannot track the error
Anyway, I guess that you did not download the last sw version, did you?
To do so, use the “manage version” module.
I think that that error was a temporarily caused by a sw update and it was already fixed…
d

Hi Ana,
the size you have chosen is even smaller than the (default) reference window used for the coregistration (64 pixels as you can see in the coregistration parameters).
Maybe if you make those numbers match it will work (I never tested the smaller possible area to coregister).
Usually, even for test or educational purposes, we take bigger…[Read more]

Hi Ana,
from the pictures you are attaching here I cannot see your problem.
Did you generate the kmz file of the Reflectivity Map? Only with that kmz you can see if your image has been geocoded well.
Please consider one factor more: for precise geocoding, you (the software) need to consider also the external DEM.
if you geocode the reflectivity…[Read more]

Hi Ana

1) if you plot the GCP in geographic and in SAR coordinates, the 2 pictures will not be matching, because SAR images are plotted with the range in the vertical direction and azimuth in the horizontal one. If you want to plot the SAR image in geographic coordinates, you can press the “Mean Kml” button (in the GCP selection module): you will…[Read more]

Just a couple of comments to close this topic

Ivana: thanks to your case I inserted a couple of minor corrections to provide a better match between the SAR and geographic coordinates in the Master area selection, SLC module. Pcodes are online, compiled version for windows is uploading, and the linux compiled version will be available in the next…[Read more]

The height is considered. However, what is used is the height coming with the SAR image, which is usually 1 value for the whole image. We can work at improving it. But we would need to get 2 sample images in which the shift is present and significant.
Ivana, could you share 2 images out of your case?