[Geocoding] [OpenStreetMap] #4990: Reverse geocode wrong state on zoom 18

[OpenStreetMap]

#4990: Reverse geocode wrong state on zoom 18
-----------------------------+-----------------------------
  Reporter:  emilio.mejia@…  |      Owner:  geocoding@…
      Type:  defect          |     Status:  closed
  Priority:  minor           |  Milestone:  Wishlist
 Component:  nominatim       |    Version:  2.0
Resolution:  wontfix         |   Keywords:  Reverse geocode
-----------------------------+-----------------------------
Changes (by lonvia):

 * status:  new => closed
 * resolution:   => wontfix


Comment:

 This might happen because reverse actually returns the address of the
 nearest object and not the address of the geographic point you asked for.
 As the address of each object is computed independently, this might lead
 to different results when places are mapped as nodes only and Nominatim
 has to guess about which object belongs where.

 In your example the nearest object at zoom 18 is a state which was
 computed as being in Heredia because that is the closest state place node,
 while at zoom 12 the closest object is the city of Florencia which got put
 in state Alajuela because of the is in. As it happens, this particular
 case can be easily fixed by adding
 [http://wiki.openstreetmap.org/wiki/Relation:boundary admin boundary
 relations] for the states. It looks like the boundary ways are already
 there, e.g. [http://www.openstreetmap.org/browse/way/31715586 this way].

-- 
Ticket URL: <https://trac.openstreetmap.org/ticket/4990#comment:1>
OpenStreetMap <http://www.openstreetmap.org/>
OpenStreetMap is a free editable map of the whole world