Hi @yunjunz, @jhkennedy,

Raised from MintPy group conversation: https://groups.google.com/g/mintpy/c/ql2D1t8D-kw/m/yycRhtT3BQAJ

Using MintPy version 1.4.1, downloaded from conda.

Appears to be an issue with how the ASF hyp3 azimuth angle information is handled in MintPy.

I need to use asc_desc2horz_vert.py to resolve up-down, east-west motion for a large area, so I need to use the azimuth angle to get more accurate estimations. I followed the instructions in https://groups.google.com/g/mintpy/c/EcmuJU9jhX0/m/hmSoiv2XAQAJ and used the lv_phi and lv_theta files as the azAngleFile and incAngleFile in the configuration file.

If I calculate the motion without the geometry file, the results are:

asc_desc2horz_vert.py asc_velocity.h5 desc_velocity.h5

read  from file: asc_velocity.h5
calculate the constant LOS incidence / azimuth angles from metadata as:
LOS incidence angle: 37.6 deg
LOS azimuth   angle: 102.6 deg
read  from file: desc_velocity.h5
calculate the constant LOS incidence / azimuth angles from metadata as:
LOS incidence angle: 37.5 deg
LOS azimuth   angle: -102.6 deg

These values make sense and produce reasonable output results:

east-west data range: [-17.406893, 15.187981] mm/year
up-down data range: [-23.816603, 19.174559] mm/year

When running the same command but including the geometry files:

asc_desc2horz_vert.py asc_velocity.h5 desc_velocity.h5 -g asc_geometryGeo.h5 desc_geometryGeo.h5

The results are wrong:

east-west data range: [-739.0742, 695.91144] mm/year
up-down data range: [-232363660.0, 266020430.0] mm/year

Can this please be checked to see if there is an issue with dealing with the ASF hyp3 azimuth angle file in MintPy.

Thanks

Attached are plots of the azimuth files after the 'load_data' step.