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: zyphlar [Submitted to the original trac issue database at 9.50pm, Friday, 26th July 2013]
I've noticed that for the following queries, the bounding boxes and/or place type are nonsensical/broken. I would attempt to fix myself but the source data for these locations seems to be more official than a newbie like myself should go around editing:
United States (the world, at zoomlevel 2?)
Phoenix, Arizona (an insignificant street corner; the Anthem suburb, or a single point at the city center?)
Tempe, Arizona (a university ranks highest, and a random intersection ranks second?)
Mesa, Arizona (a residential neighborhood, city hall, or a bunch of squiggles?)
It seems like some of these entries have good intent ("the city hall building is a city, right?") but are sorely lacking ("where did half the city borders go?"). If you have suggestions for me to fix these myself, I'll take them, I just didn't want to go in and disagree with [http://www.openstreetmap.org/browse/relation/254038 The US Census].
The text was updated successfully, but these errors were encountered:
Author: lonvia [Added to the original trac issue at 7.57pm, Sunday, 28th July 2013]
As you guessed right, these are all rather data problems in OSM and not bugs with Nominatim itself, so this is not the right forum to discuss those. Try the local mailing list ([http://lists.openstreetmap.org/listinfo/talk-us talk-us] in this case) where there are experienced mappers that can help you understand what is wrong and how to fix it.
For what it's worth, short comments for your examples:
United States: that's quite normal, the bounding box includes Alaska and Hawaii.
Phoenix, Arizona: the [http://www.openstreetmap.org/browse/relation/254038 city boundary] is badly broken and that is all that Nominatim could salvage.
Tempe, Arizona: the ranking is an actual guessing error by Nominatim (it considers the university more important)
Mesa, Arizona: again a [http://www.openstreetmap.org/browse/relation/110815 badly damaged city boundary]
Reporter: zyphlar
[Submitted to the original trac issue database at 9.50pm, Friday, 26th July 2013]
I've noticed that for the following queries, the bounding boxes and/or place type are nonsensical/broken. I would attempt to fix myself but the source data for these locations seems to be more official than a newbie like myself should go around editing:
It seems like some of these entries have good intent ("the city hall building is a city, right?") but are sorely lacking ("where did half the city borders go?"). If you have suggestions for me to fix these myself, I'll take them, I just didn't want to go in and disagree with [http://www.openstreetmap.org/browse/relation/254038 The US Census].
The text was updated successfully, but these errors were encountered: