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: imz
[Submitted to the original trac issue database at 4.02pm, Monday, 26th November 2012]
For example, I searched for " " ("street Zoological") at osm.org, but couldn't find anything in Moscow.
For most Russian street names, it's the most natural word order. (And hence, more preferred by some people when entering a formalized search query.)
But this street's name sounds better as " " ("Zoological street"), which indeed can be found: http://www.openstreetmap.org/?minlon=37.5783157348633&minlat=55.7643699645996&maxlon=37.5794830322266&maxlat=55.7651596069336 .
But it's true for many kinds of addresses: that both word orders would be admissible (, , , etc.)
So, it would be convenient if such a transposition would automatically cound as equivalent to an existing name in the search engine.
The text was updated successfully, but these errors were encountered: