We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Wikipedia gives the following examples for MGRS values:
https://en.wikipedia.org/wiki/Military_Grid_Reference_System
4Q .....................GZD only, precision level 6° × 8° (in most cases) 4QFJ ...................GZD and 100 km Grid Square ID, precision level 100 km 4QFJ 1 6 ...............precision level 10 km 4QFJ 12 67 .............precision level 1 km 4QFJ 123 678 ...........precision level 100 m 4QFJ 1234 6789 .........precision level 10 m 4QFJ 12345 67890 .......precision level 1 m
But parsing fails because the parse function in mgrs.js checks if the first two values are of type number.
geodesy/mgrs.js
Lines 149 to 158 in 8f4ef33
The text was updated successfully, but these errors were encountered:
Thank you for raising this issue.
I have corrected the MGRS parsing to accept single-digit zones.
Sorry, something went wrong.
No branches or pull requests
Wikipedia gives the following examples for MGRS values:
https://en.wikipedia.org/wiki/Military_Grid_Reference_System
4Q .....................GZD only, precision level 6° × 8° (in most cases)
4QFJ ...................GZD and 100 km Grid Square ID, precision level 100 km
4QFJ 1 6 ...............precision level 10 km
4QFJ 12 67 .............precision level 1 km
4QFJ 123 678 ...........precision level 100 m
4QFJ 1234 6789 .........precision level 10 m
4QFJ 12345 67890 .......precision level 1 m
But parsing fails because the parse function in mgrs.js checks if the first two values are of type number.
geodesy/mgrs.js
Lines 149 to 158 in 8f4ef33
The text was updated successfully, but these errors were encountered: