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

Add maidenhead precision logic to Position #89

Open
2 tasks
CBielstein opened this issue Jan 1, 2022 · 0 comments
Open
2 tasks

Add maidenhead precision logic to Position #89

CBielstein opened this issue Jan 1, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@CBielstein
Copy link
Owner

Description

Position class currently does not have an automatic encoding of gridsquare to be the correct specificity. This can be a problem if a 4-char gridsquare is decoded and then attempted to encode later. This would add additional precision (which may not be very accurate) to the location.

Another example is decoding from a lat/long coordinate with ambiguity.

Consider using the ambiguity value in encodes and decodes.

Acceptance Criteria

  • Maidenhead gridsquare decode and encode results in the same precision of gridsquare
  • Maidenhead encode does not result in a more precise location than geocoord with ambiguity
@CBielstein CBielstein added the enhancement New feature or request label Jan 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant