Reverse geocoding gives city of nearest object, not city of current position
|Reported by:||AlphaTiger||Owned by:||geocoding@…|
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 :
reverse nominatim answers :
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 reverse.php lines 95-102 return the current city in the objects (maybe by removing rank considerations) ?