utils0.latlon2utm()
: ensure a single output UTM zone
#1177
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of proposed changes
utils.utils0.latlon2utm(): add
meta
in as required argument to invokeforce_zone_number
while callingutm.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:Reminders
lalo2yx
behaves incorrectly when set of lat/lons cross UTM zone boundary #1176