Zhang Yunjun

In a nutshell, it should work similarly to the `tsview.py --zero-first` option, by changing the reference date to the first date on the fly. A more detailed description of the...

Thank you @cirrusasf, this feature sounds reasonable and useful. One solution could be: for each geo-coordinate related option, add an accompanying option to specify a different unit from the input...

@jhkennedy could you expand more on the 3rd topic? The code does not rely on the `MINTPY_HOME` environment variable, I made sure of that a while ago. So it should...

Thank you @jhkennedy for the detailed explanation! Registering the entrypoints in setup.py sounds good to me. Regarding the refactoring, it seems a lot of changes. I will think about this...

Awesome. Please feel free to submit your PR and we could do more testing on the entrypoints setup.

KML takes south, north, east, west in degrees, so you could use [ut.to_latlon()](https://github.com/insarlab/MintPy/blob/main/mintpy/utils/utils0.py#L291) to do the conversion at [save_kmz.py#L338](https://github.com/insarlab/MintPy/blob/main/mintpy/save_kmz.py#L338). A similar approach can be done for save_kmz_timeseries.py as well.

Note that the `UTM_ZONE` and `EPSG` code are saved in the metadata as well, for hyp3 products. So one could extract them to make this conversion generic.

One possible issue could be that: in `save_kmz_timseries.py`, the coordinate of every pixel is converted, while in `save_kmz.py`, only the 4 corners are used in the conversion to define the...

> Share something I found recently. these images should be transfer from WGS84 UTM to WGS84 lat/lon first. but when a Image cross the Equator, the transform process could be...

Thank you for bringing this up @forrestfwilliams. I am not very familiar with the various choices of software and data (SAR and optical) for offsets but am very curious to...