You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: pnowak [Submitted to the original trac issue database at 11.56am, Sunday, 19th June 2011]
I have two coordinates, which are only a few hundred meters away from each other (in the same city), but the reverse geocoding request places them in two different cities (a few hundred kilometers away from each other) and even countries.
Author: lonvia [Added to the original trac issue at 3.18pm, Saturday, 14th July 2012]
Data problem. The boundary of Upper Austria was missing and that was the best guess Nominatim could take. A proper boundary has been added in the meantime.
Reporter: pnowak
[Submitted to the original trac issue database at 11.56am, Sunday, 19th June 2011]
I have two coordinates, which are only a few hundred meters away from each other (in the same city), but the reverse geocoding request places them in two different cities (a few hundred kilometers away from each other) and even countries.
Point one is correct calculated to be in Upper Austria, Linz (Austria) - http://open.mapquestapi.com/nominatim/v1/reverse?format=xml&lat=48.260269&lon=14.325599&zoom=18&addressdetails=1&accept-language=en
Point two (approximately 200 meters away) is calculated wrong to be in Graubnden, Switzerland - http://open.mapquestapi.com/nominatim/v1/reverse?format=xml&lat=48.260269&lon=14.324499&zoom=18&addressdetails=1&accept-language=en
A reverse geocoding request for point two should also return the city 'Linz', state 'Upper Austria' and Country 'Austria'.
The text was updated successfully, but these errors were encountered: