You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the InSAR product guide, the naming convention image shows example pixel spacings of 80m and 160m:
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.
The text was updated successfully, but these errors were encountered:
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.
In the InSAR product guide, the naming convention image shows example pixel spacings of 80m and 160m:
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.
The text was updated successfully, but these errors were encountered: