SARPROZ ©

Hello,

You were right, there was a bit difference in the name of the file from the automatic one, that I don’t know how!, but yes the name was the issue!

Thank you for your helpful hints.

Best regards,
Mahtab

Hello again,

Yes, I know it is not an issue with the software. I thought maybe I am exporting wrongly.
Thank you for the hints, all answers are yes, same things, but the problem is still there. I need to investigate what is going on afterwards as you mentioned.

Thank you 🙂

Best regards,
Mahtab

Hi Mahtab,
unfortunately, as you can understand, this problem does not apply to Sarproz. Instead, it is related to something else, happening afterward. So, hereafter some hints, hope it helps, but then you find the problem yourself.
are you re-opening the exact same KMZ (not kml!) file? search for that, check location, size and date. Are you…[Read more]

Thank you again for your comments.

Hi,
to interpret the coherence value, one should give many more details: what model you are using, what parameters are estimated, what options you applied, which images graph, whether weights are used, whether the atmosphere is corrected or not, and so on and so fort, the list could be long. Without having those details, you cannot interpret well…[Read more]

Hi,
I am using windows. I’ve scanned through the files and haven’t noticed any obvious difference between the >1GB and <1GB.
I agree that is good to know if this is confirmed by others and hopefully there will be ways to go around it. Maybe a functionality from the Time Series Module to split the area in tiles (separate archives, maybe with a…[Read more]

Thank you for this info,
a few more details that can help:
1. are you using windows? this problem could be system-specific
2. do you see anything different between data/files > 1GB and data/files < 1GB? this can help understanding whether it's a problem related to big kmz files generation (affecting Sarproz at some points) or to big kmz file…[Read more]

Thanks. I did a few tests creating kmz of different sizes (by filtering the n. of points) and wanted to circle back the results here, as it may help others with the same issue. I found that files <1GB are working fine, while files over 1GB keep returning the above-mentioned error.
Regards

the file you are showing is not the root one
to make it clearer:
the KMZ file is a zipped file that contains:
* a KML file (let’s call it the root one)
* a folder
In the folder you can find many more kml files, numbered at different levels
The root kml file contains links to files in the folder, which are linked to other files in the folder in a…[Read more]

Thank you for the prompt answer. Yes, I was able to open the selected subsets kml individually. I have also followed your suggestion and read the kml as text. Based on the attached image, could you confirm is the links to the files are missing? I can of course provide more info or the file itself if needs to be checked. Would be interesting to…[Read more]

Hi Jianbu,
the file Sarproz creates is a KMZ, which is basically a zip file. If you can open it and if you can read files inside it’s a good start, it means the problem is not the size (I am not aware of file size limitations by the way).
then, you will find inside a kml file and a folder. you can extract the kml file and check if you can open it…[Read more]

So Can I please ask that which one is more close to real deformation? Then we can use that one to make figures:)

It works now. Thank for your response. It seems that I had missed some detail of manual..

There is a flag here https://sarproz.com/manual/insar_params.html
“update new images only” will do process only new/missing data
otherwise, all data will be processed…