search

ASFHyP3 / ASFHyP3.github.io

https://asfhyp3.github.io/
1 stars 0 forks source link

output spatial resolution selection #9

Open mdelgadoblasco opened 1 month ago

mdelgadoblasco commented 1 month ago

Could the user select the output spatial resolution thinner than 40m/80m ? Maybe selecting the multilook factor 5x1 instead of 10x2?

Thank you very much

jhkennedy commented 1 month ago

Hi @mdelgadoblasco you can select 5x1 look using the INSAR_ISCE_BURST job type: https://hyp3-docs.asf.alaska.edu/guides/burst_insar_product_guide/

mdelgadoblasco commented 1 month ago

But for the standard insar workflow it is not possible, right? Could that be added?

But also, in addition to the multilook factor, which would be the spatial resolution associated to that 5x1? 20m ? If this is not linked, could the user select which is the spatial resolution that is desired by the user to have?

Thanks again.

jhkennedy commented 1 month ago

@mdelgadoblasco correct, we do not offer 5x1 for INSAR_GAMMA. Now that we've moved to a credit system, we could offer it, but I don't know of a timeline for doing so. CC @krkristenson-asf

for 5x1, the output pixel spacing will be 20m, which closely matches the resolution of the multilooked images. Providing an option for different pixel spacings would not give you significantly better results than resampling the HyP3 products to your desired pixel spacing.

mdelgadoblasco commented 1 month ago

Hi @jhkennedy, You are right, this is why also I believe that the coherence windows used in azimuth and range shall be also modified to really see the difference.

Resampling a 40m images into 20m will not make such a difference without modifying also the underlying parameters used in the coherence computation step.

Can also the coherence windows be modified according to the final spatial resolution of the desired 20m? @krkristenson-asf That would be great. Please, let me know.