Repository navigation
Fix/utm zone 60 boundary - #176
Open
timothyanderson096-ocdealcheck wants to merge 2 commits into
Open
timothyanderson096-ocdealcheck wants to merge 2 commits into
timothyanderson096-ocdealcheck wants to merge 2 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Problem
geo2grid() can select UTM zone 61 at +180 degrees longitude and immediately below it due to floating-point rounding. UTM has only zones 1–60. grid2geo() rejects the resulting invalid zone.
Scoped correction
Clamp only the automatically computed zone to 60 at the upper boundary. Preserve the conventional -180 -> zone 1 and +180 -> zone 60 assignments, explicit zone selection, longitude validation, and ISG behaviour. No change to the separate vincdir() fix in #174 or decimal-year support in #175.
Tests and evidence
Numerical tests do not prove physical positioning accuracy. Boundary representation is offered for maintainer review.
Prepared by Tim Anderson / OC Labs with AI-assisted testing.