Maidenhead gridsquare locator logic appears to not be correct

[CBielstein]

Description

When testing latest changes (#93) against real packets, it appears that the full 6-char gridsquare locator is in accurate. I'm getting the following interpretations.

5017.57N/00404.80E_ (JO20AH) which maps 50.1757N, 004.0480E to JO20ah. However, the coordinates don't appear to be in the box in various online tools. One tool indicated such coordinates should be in JO20ae.

Similar with a decode on 5050.28NT00420.23E& to JO20EU.

Acceptance Criteria

• [ ] Investigate if 6-char gridsquare encoding is inaccurate or if these other websites (or my current understanding) is wrong
• [ ] Find the bug and fix it!
• [ ] Write tests to validate the fix

[CBielstein]

This is actually not a bug. I forgot APRS encoding of the packet isn't straight decimal. It's degrees minutes.hundredthsOfMinutes. As I was just copying out and moving the decimal, I got the manual verification incorrect. When using the algorithm to decode, the coordinates are correct as verified by the site cited in the original bug report.

Closed!