-
-
Notifications
You must be signed in to change notification settings - Fork 982
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
Ordnance Survey Coordinate System (OSGB) #11299
Comments
+1 for this, if you're packing printed maps for planning or backup it would be nice if the two matched so you don't need to convert all your waypoints which is tedious. |
Yes another +1 please. I've been looking for a plugin to do this without success. To support OSGB NGR natively would improve its useability massively since all UK location references use it. |
Another request. OSGB is still heavily used in the UK. I am on a group walking holiday right now and the walk starts are given as OSGB and What3words (boo!). Not Lat/long or OLC. |
Another +1 from me :-) |
Request suppot of the OSGB coordinate system as an alternative to Lat/Long. This is the standard system used in the UK.
This feature is supported in most standalone GPS units and Android mapping apps that I have seen.
In the UK most (paper) walking books and magazines list the waypoints on a route using the OS (Ordnance Survey) grid ref. This is quite short (eg "ST 123 678") and so is very easy to type in. This ref is accurate to 100m which is good enough for most purposes, but a longer form "ST 12345 67890" gives an accuracy of 1m.
Workaround: At the moment I have to type these waypoints into another mapping program, save the generated route as a GPX file and then load that into OSMAND. It would obviously be great if I could enter it into OSMAND direct.
The text was updated successfully, but these errors were encountered: