Open brunetton opened 3 years ago
Agreed.
Actually, this is what currently works:
This is what does not work yet (but should): Entering (or confirming) a coordinate in the search field, like "63.16594, 10.11170" - then clicking "Search"! The behavour of case 2 above is weird that Qwant puts "63.16594 : 10.11170" into the Search field and then fails when a user confirms and clicks again on "Search!". In both cases Qwant currently responds with "Sorry, we could not find this place".
The solution and behaviour I'd expect is, that when a user searches (or confirms) a coordinate like "63.16594, 10.11170" (or "63.16594 : 10.11170"), Qwant Maps centers & zooms there, and does a geocoding displaying "Near ...".
Actually, in use case 3, clicking on the coordinate "63.16594 : 10.11170" (or rather "63.16594, 10.11170"), should copy it in paste buffer (same coordinates are already in the Search field, an a user can simply click on "Search!" to center & zoom again).
Any update on this? Extracting coordinates from a string to a lat/lon is a no-brainer. I would accept many delimiters: space, colon, semicolon, etc.
When entering GPS coordinates (ex:
50.6416,3.0597
) the map understand it and display the result as a point on map