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: ToB [Submitted to the original trac issue database at 3.59pm, Monday, 31st December 2012]
For instance, [[http://nominatim.openstreetmap.org/search.php?q=Airport+BER%2C+Berlin|Airport BER, Berlin]] should find [[http://www.openstreetmap.org/browse/relation/2411891]] but it only finds [[http://www.openstreetmap.org/browse/relation/2411892]]
The text was updated successfully, but these errors were encountered:
Author: lonvia [Added to the original trac issue at 8.12pm, Thursday, 3rd January 2013]
It doesn't really look like 2411891 will become an airport any timein the near feature, so Nominatim is right there.
Nonetheless, IATA tags are indeed a problem as they are often far too low in the search result list. At least something like 'BER airport' should come up with the correct result. There is another bug report #3959 about that issue, so closing this one as a duplicate.
Reporter: ToB
[Submitted to the original trac issue database at 3.59pm, Monday, 31st December 2012]
For instance, [[http://nominatim.openstreetmap.org/search.php?q=Airport+BER%2C+Berlin|Airport BER, Berlin]] should find [[http://www.openstreetmap.org/browse/relation/2411891]] but it only finds [[http://www.openstreetmap.org/browse/relation/2411892]]
The text was updated successfully, but these errors were encountered: