There was a fatal error when we imported this data to PolSARPro. The error message was that there was wrong polar-type argument in config.txt. But the dual polarazation of Sentinel-1 is right. Moreover, there is no error in the precessing. We cannot find the reason.
After contacting the authors of the paper, PolarType in config.txt should be ‘full’ instead of ‘dual’. Moreover, C11, C22, C12real, C12imag, and config.txt should be within ‘C2’ subdirectory. Then the data can be imported to PolSARpro.
When exporting partially polarimetric S-1 data into PolSARpro format, config.txt gives PolarType = dual, when it should be pp1, pp2, or pp3 depending on the product.
I see. Thank you for providing the published version. It appears the authors made some adjustments based on review comments.
Section 3.1. of this paper does a great job at explaining exactly what is required for getting the required binary outputs for PolSARpro. Initially, and as this paper subtly shows not to do, I was using ESD after back-geocoding, a step I thought was required based on several conversations and videos I’ve watched (people always say it’s a “two step” process). At least for me, for some reason, ESD doesn’t play nice when the goal is exporting to PolSARpro format. I omitted it and it went smoothly afterwards. I thought I would mention this in case someone else has the same issue.
Perhaps someone out there knowns why ESD might prevent the export of PolSARpro binary files???
@hiny Are there any other small quirks you may have encountered when importing the C2 PolSARPro matrices exported from SNAP? Every time I try to import those matrices as either Single Data Set or Multi Data Sets, I get:
