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

InSAR naming convention image doesn't match name string #255

Open
jhkennedy opened this issue Oct 13, 2022 · 1 comment
Open

InSAR naming convention image doesn't match name string #255

jhkennedy opened this issue Oct 13, 2022 · 1 comment
Labels
bug Something isn't working

Comments

@jhkennedy
Copy link
Contributor

In the InSAR product guide, the naming convention image shows example pixel spacings of 80m and 160m:
image

but we don't actually offer 160m pixel spacing and there's only two characters for the value so it's not clear how 160 would fit into the scheme either.

@jhkennedy jhkennedy added the bug Something isn't working label Oct 13, 2022
@asjohnston-asf
Copy link
Member

asjohnston-asf commented Oct 13, 2022

The implementation is at https://github.com/ASFHyP3/hyp3-gamma/blob/develop/hyp3_gamma/insar/ifm_sentinel.py#L430 . The pixel spacing in the name is always 20 times the azimuth looks, and is potentially variable-length.

I agree the image should show 40 and 80 to reflect HyP3's current 10x2 and 20x4 range/azimuth look offerings, although the name would include _INT160_ should anyone ever run the code outside of HyP3 with 8 azimuth looks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants