Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

Parse more lat/lon formats #574

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 3 comments
Closed

Parse more lat/lon formats #574

openstreetmap-trac opened this issue Jul 23, 2021 · 3 comments

Comments

@openstreetmap-trac
Copy link

Reporter: ColinMarquardt
[Submitted to the original trac issue database at 11.20pm, Friday, 26th October 2007]

It would be nice if the Search field on the OSM main page would allow some more formats for specifying lat/lon. E.g., I'm missing

51.9 -8.47 (I need to put a comma to separate them in OSM)
-195833.26" 232541.52"

Both are supported in Google Maps.

TIA
Colin

@openstreetmap-trac
Copy link
Author

Author: GoemonGPS
[Added to the original trac issue at 12.53pm, Thursday, 5th January 2012]

I miss this feature as well! In another ticket ([http://trac.openstreetmap.org/ticket/1805 #1805]) the issue was solved for plain coordinates.

Coordinate formats I'd like to have parsed are:

Normal GPS Coordinates (WGS84 Datum)[[BR]]
Decimal 12.3456 12.345 [[BR]]
DDD MM.MMM N 12 04.567 E 012 34.567[[BR]]
DDD MM SS.SSS N 12 3' 45.678" E 12 34' 05.678"

with support of + and - for the NSEW and common separators like space, comma, semicolon.

UTM (WGS84 Datum)[[BR]]
33U E 345678 N 5671234

@openstreetmap-trac
Copy link
Author

Author: iandees
[Added to the original trac issue at 10.35pm, Monday, 9th September 2013]

This could be done in .js before it hits the server (matching a couple regexes), or in the the /geocoder/search_geonames endpoint in the railsport.

@openstreetmap-trac
Copy link
Author

Author: lonvia
[Added to the original trac issue at 2.47pm, Saturday, 10th February 2018]

Fixed by osm-search/Nominatim#909

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant