You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: david[at]frankieandshadow.com [Submitted to the original trac issue database at 5.10pm, Saturday, 2nd December 2006]
Search for "Newcastle" or "Newcastle-upon-Tyne" and you end up in Australia. Needs to be some means of coping with multiple search results (which is presumably what is happening). See my earlier ticket (281) about this in relation to the OSM site search box - same applies here.
The text was updated successfully, but these errors were encountered:
Author: crschmidt[at]crschmidt.net [Added to the original trac issue at 8.18pm, Saturday, 2nd December 2006]
This doesn't surprise me too much. This is the fault of the geocoder being used at the backend. Updating ticket summary to represent the real problem: that there is no way of choosing between different results for the location search.
Reporter: david[at]frankieandshadow.com
[Submitted to the original trac issue database at 5.10pm, Saturday, 2nd December 2006]
Search for "Newcastle" or "Newcastle-upon-Tyne" and you end up in Australia. Needs to be some means of coping with multiple search results (which is presumably what is happening). See my earlier ticket (281) about this in relation to the OSM site search box - same applies here.
The text was updated successfully, but these errors were encountered: