Meters Translation Correction and Pixel to Meters Calculations

[qnguyen345]

In the original code, the generated lat,lon shapely polygons did not align properly with the satellite image. This is checked when I converted these lat,lon polygons to kml and imported those kml onto Google Earth and vertified that the polygons were misaligned for the same satellite image scan (as shown in the first image below).

The new code accounts for the correct meter translation by using pyproj projection. Also, instead of having an approximate meter per pixel conversion, calculate its value from a meter per pixel formula. The formula is located here for reference: https://gis.stackexchange.com/questions/7430/what-ratio-scales-do-google-maps-zoom-levels-correspond-to

The first image is the lat,lon polygons generated from the original code and the second is from the updated code.

[kperry2215]

This looks great @qnguyen345 ! As a last request, can you check if any of our jupyter notebooks use the associated updated functions and run them if so, just so our documentation is up-to-date?

[qnguyen345]

@kperry2215 There were two that used the updated functions, Austin_hail_damage_example and Sol-Searcher_example. They have been updated in the new commit.