[Geocoding] [OpenStreetMap] #4519: Reverse geocoding gives city of nearest object, not city of current position

[OpenStreetMap]

#4519: Reverse geocoding gives city of nearest object, not city of current
position
-------------------------------+--------------------------------------------
 Reporter:  AlphaTiger         |       Owner:  geocoding@…                
     Type:  enhancement        |      Status:  new                        
 Priority:  minor              |   Milestone:                             
Component:  nominatim          |     Version:                             
 Keywords:  reverse geocoding  |  
-------------------------------+--------------------------------------------
Changes (by lonvia):

  * priority:  major => minor
  * type:  defect => enhancement


Comment:

 Using the address of the nearest object for the reverse query was a
 deliberate design decision. Calculating the address involves a lot of
 voodoo because it has to work world-wide and with different tagging
 schemas. It would be too expensive to do at each reverse request.

 The other thing is that long ways become less and less frequent, the
 better a region gets mapped. Ways are split for taggings like maxspeed and
 for route relations and turn restrictions. The moment the way is split,
 the issue goes away by itself because each part can have a different
 address. So I wouldn't call it a major issue.

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