Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

utils0.latlon2utm(): ensure a single output UTM zone #1177

Merged
merged 1 commit into from
Apr 16, 2024

Conversation

yunjunz
Copy link
Member

@yunjunz yunjunz commented Apr 13, 2024

Description of proposed changes

  • utils.utils0.latlon2utm(): add meta in as required argument to invoke force_zone_number while calling utm.from_latlon(), to ensure all coordiantes are converted into the same single UTM zone, as designated in the UTM_ZONE metadata, even if they cross a UTM boundary.

  • adjust the latlon2utm() usage in all scripts:

    • objects.coord.py
    • utils.plot.py

Reminders

+ utils.utils0.latlon2utm(): add `meta` in as required argument to invoke `force_zone_number` while calling `utm.from_latlon()`, to ensure all coordiantes are converted into the same single UTM zone, as designated in the UTM_ZONE metadata, even if they cross a UTM boundary.

+ adjust the `latlon2utm()` usage in all scripts:
   - objects.coord.py
   - utils.plot.py
Copy link
Collaborator

@forrestfwilliams forrestfwilliams left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me!

@yunjunz yunjunz merged commit 32645dd into insarlab:main Apr 16, 2024
7 checks passed
@yunjunz yunjunz deleted the latlon2utm branch April 16, 2024 15:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

lalo2yx behaves incorrectly when set of lat/lons cross UTM zone boundary
2 participants