[maghsoudi]

when I increase the region to the ‘max area’, the co-registration works without any error. But the problem is that this area is too big for the performing the ‘site processing’ steps and is very time consuming. It would be good if there was an option right at the end of the co-registration in which we could subset the area of interest (this option is before doing the co-registration at the moment).

[maghsoudi]

Hi Yuxiao,

I installed the latest version as of 06 June and repeated the procedure. Again, the same error message pops up as per attached.
Also, I would like to know what exactly is being performed in the “TOPS Post Processing for each image pair”. In my case, for 5 pairs I am receiving a warning message showing lack of coherency in my selected area and the pair is rolled back to SLC before Post Coregistration. I was curious to know what exactly is being missed in this rolling back.

Regards,
Yasser

Attachments:

You must be logged in to view attached files.

[maghsoudi]

By the way, when do you think the new update will be released?

[maghsoudi]

Thanks Yuxiao. I noticed the warnings. My area was about 4 by 4 km2 in the beginning. I increased the area to 5 by 5 km2 but I received the same warning message. I am not able to increase my area as it will contain a very large non-coherent area which again may cause problems to the co-registration process.

[maghsoudi]

Hi Yuxiao,

I am still receiving an error message while I am trying the co-registration for the sentinel-1 images. I attached the error code. I would be grateful if you could help me on that.

Yasser

Attachments:

You must be logged in to view attached files.

[maghsoudi]

Attached!

Attachments:

You must be logged in to view attached files.

[maghsoudi]

Hi Yuxiao,

Thanks for the ongoing updates for the sentinel-1. I previously applied the coregistration for a series of sentinel-1 images using the older version. However, using this new version an error message pops up just after doing the deramping. I attached the error message.

Regards,
Yasser

[maghsoudi]

Thanks Daniele. It is now much clearer indeed. Also, I would like whether other PS approaches such as StaMPS and DePSI can be implemented. The former, as you know, employs a spatial smoothness assumption whereas the latter uses a temporal smoothness assumption. But I could not find such parameters in sw.

[maghsoudi]

Thanks Daniele. I was able to load a custom graph. Can you please tell me what the values 0, 1 and -1 mean in each graph?

[maghsoudi]

In addition, shouldn’t the coregistration process be performed again after changing the graph as the image pairs have been changed?

[maghsoudi]

Hi Daniele,

Handling of the data is much easier in google earth thank Matlab (zooming in/out, panning…). Plus, the background image in my case is not the google earth high resolution image. It is low resolution image.
I used the sparse geocoding module but it uses the full image for the export and not the small area.

Regards,
Yasser

[maghsoudi]

Hi Daniele,

I could not find enough information on the APS information using the SARPROZ manual. Can you please introduce some references for a better practical/theoretical understanding of this module?

Thanks,
Yasser

[maghsoudi]

Thanks Daniele. It is now working perfectly with the new version. I will let you know about the results soon.

[maghsoudi]

Hi Daniele,

I downloaded and installed the most updated version but again I am receiving the same error message. Additionally, this time when I select the “view parameters” button to check my spatial/temporal baselines I receive this message:
“Reference to non-existent field ‘FlagSequence'”. The error messages are attached.

Thanks,
Yasser

Attachments:

You must be logged in to view attached files.

[Author]

Posts