search

ASFHyP3 / hyp3-docs

Documentation for HyP3 products and services
https://hyp3-docs.asf.alaska.edu/
BSD 3-Clause "New" or "Revised" License
12 stars 10 forks source link

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

Open jhkennedy opened 2 years ago

jhkennedy commented 2 years ago

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.

asjohnston-asf commented 2 years ago

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.