Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

S1 L2 processor - Enabling coherence when master and slave images come from the same sensor #4

Open
lopesml opened this issue Sep 21, 2020 · 0 comments

Comments

@lopesml
Copy link

lopesml commented Sep 21, 2020

Hello,

When a study site is only covered with Sentinel-1A, the revisit frequency of S1 is 12 days instead of 6. I posted about this on the Sen4CAP forum, and kraftek helped me change the parameters in the config database to allow a temporal offset of 12 days for coherence generation.
But the processor still requires that the master and slave images come from S1A and S1B, which is not logical.

Products must come from different sensors [found S1A_IW_SLC__1SDV_20190824T003729_20190824T003756_028704_033FD2_5A85.SAFE, S1A_IW_SLC__1SDV_20190812T003729_20190812T003756_028529_0339C7_2786.SAFE]

Is it possible to remove this exception?

Thanks in advance for your help!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant