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

Maidenhead Locator System coordinates #17325

Open
fcatt opened this issue Jun 1, 2023 · 2 comments · May be fixed by #18436
Open

Maidenhead Locator System coordinates #17325

fcatt opened this issue Jun 1, 2023 · 2 comments · May be fixed by #18436
Labels
Nice to Have Should be fixed but there is no priority or no possibility to fix it within current horizon planning

Comments

@fcatt
Copy link

fcatt commented Jun 1, 2023

🚀 feature request

Description

Maidenhead Locator System is used by radioamateurs to indicate geographical coordinates in a concise way, even in bad transmission conditions. This system is greatly adopted by the community all over the World.
The coding uses alternating pairs of letters and digits to encode longitude and latitude. With 6 characters the precisions is ≈ 10 km, for more precise location (extended locator), it il possible to add 2 additional digits.
See en.wikipedia.org/wiki/Maidenhead_Locator_System

Describe the solution you'd like

In the coordinates dropdown panel from the map context menu, displaying coordinates in the Maidenhead Locator System format alongside others coordinates formats.

Describe alternatives you've considered

There are two standalone Android apps on the Playstore (no F-Droid or direct APK download) from the same developper and unknown licence: com.us1pm.gridsquarelocator (current/last known device location only, no map) and com.us1pm.gridzone (uses a Google Maps background).

@vshcherb vshcherb added the Nice to Have Should be fixed but there is no priority or no possibility to fix it within current horizon planning label Jun 2, 2023
@vshcherb
Copy link
Member

vshcherb commented Jun 2, 2023

@onitake onitake linked a pull request Oct 25, 2023 that will close this issue
@onitake
Copy link

onitake commented Oct 25, 2023

I tried to implement this in #18436 but couldn't manage to build OsmAnd locally, so it's completely untested.

@vshcherb vshcherb added this to the future-android milestone Oct 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Nice to Have Should be fixed but there is no priority or no possibility to fix it within current horizon planning
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants