Description of the problem

KMZs produced when running the google_earth step are not properly geocoded if data are in UTM because save_kmz.py assumes that data are in WGS84 and creates an invalid bounding box.

#1210

Full script that generated the error

smallbaselineApp.py path/to/config --work-dir path/to/work_dir --dostep google_earth

Error example
The KMZ should appear in Google Earth like this:

But, if data are in UTM, it appears like this:

Adjusting Google Earth preferences to use UTM does not work because the kmz is not correctly geocoded.

System information

• Operating system: Linux
• Python environment: conda
• MintPy version: 1.6.0
• InSAR processor/product: hyp3
• Your custom / default template file (if the bug is related to a specific dataset):