|
I think the best thing to try, if it is possible for you, is to upgrade to a more current version of SARscape. The SARscape developers have made many improvements to the SBAS processing in the past several releases. It seems likely that one of these improvements may resolve this problem. Also, there is a new release coming in the next few months (probably), that will involve a complete rewrite of SBAS. So when that is available, I would highly recommend trying that version to see if it resolves this issue.
If that is not possible, I'm afraid that it is not at all clear what might have caused the error message you are getting. It could be a wide variety of things. A developer would probably need to take a look at your data, and try processing it in the new version to figure out what is going wrong. And if a fix is required, that would most likely be provided for the current or next release. That is one of the advantages of having a current maintenance contract.
I'm sorry that I can't be more help.
Best,
Peg
|