This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Nominatim using wrong relation for county outline #4693
Assignees
Comments
|
Author: lonvia The recent boundary cleanup in Virginia has caused a bit of confusion in Nominatim. The problem is that Nominatim does not update relations when a member way is changed and therefore ended up with the occasional mesh-up of old and new data. The counties above are now clean. Let me know if there are further problems. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Reporter: blahedo
[Submitted to the original trac issue database at 11.57am, Saturday, 17th November 2012]
Searches for Farmville, Virginia (spans Prince Edward and Cumberland counties) describe it as being in Appomattox County; viewing Appomattox County in the Nominatim database ([http://nominatim.openstreetmap.org/details.php?place_id=3665338557 3665338557]) displays the same map as that of Prince Edward County ([http://nominatim.openstreetmap.org/details.php?place_id=3665865857 3665865857], which is correct), but it does correctly report Appomattox County as being represented by multipolygon relation [http://www.openstreetmap.org/browse/relation/2534165 2534165], and clicking on the link to that relation shows the correct outline for Appomattox County. It doesn't appear to be bad data in the main OSM database (the relations and names are correct), so I guess it's a Nominatim bug of some sort.
The text was updated successfully, but these errors were encountered: