[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  |  
-------------------------------+--------------------------------------------
 Hi,

 With some ways which go through multiple cities, reverse geocoding answers
 the wrong city, as the address given contains the city at the nearest
 object's centroid, and not the city of the position asked.

 For instance, for this point :
 http://www.openstreetmap.org/?mlat=48.503321&mlon=1.702448&zoom=14&layers=M
 reverse nominatim answers :
 http://nominatim.openstreetmap.org/reverse?lat=48.503321&lon=1.702448

 The city of the point is not Bleury-Saint-Symphorien, it is clearly
 Ymeray; we get this city as answer as the nearest object is "L'Océane"
 (http://www.openstreetmap.org/browse/way/128525165) and its centroid is in
 Bleury-Saint-Symphorien.

 Reverse geocoding should not "blindly" use the computed address of the
 nearest object, but should instead (try to) search for the point's current
 city, region, etc. to give a correct address.


 I don't know enough how nominatim works, but wouldn't the SQL query in
 [https://trac.openstreetmap.org/browser/applications/utils/nominatim/website/reverse.php
 reverse.php] lines 95-102 return the current city in the objects (maybe by
 removing rank considerations) ?

 Thanks !

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