[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:  defect             |      Status:  new                        
 Priority:  major              |   Milestone:                             
Component:  nominatim          |     Version:                             
 Keywords:  reverse geocoding  |  
-------------------------------+--------------------------------------------

Comment(by lonvia):

 Replying to [comment:4 cquest]:
 > Replying to [comment:3 lonvia]:
 >
 > > Sorry but it is not as simple as that because currently there are no
 distances to any address objects calculated. Doing so would add a pretty
 heavy performance penalty and is simply not worth the trouble.
 >
 > Well, the code at
 https://trac.openstreetmap.org/browser/applications/utils/nominatim/website/reverse.php
 shows an "ORDER BY ST_Distance" at line 102... so distance is already
 calculated or I'm not looking at the right code.

 You are not looking at the right code. This is the part where it finds the
 nearest object. The address parts are requested at line 133ff.

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