We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Since days I cannot search within OSM, it gives no results. I tried Nominatim search site and it works: https://nominatim.openstreetmap.org/ui/search.html And https://www.openstreetmap.org/#map=13/47.2939/17.5988 also works
But not when I am editing in OSM and I need to find a location. There is no error message.
2.0.3
Firefox 116.0.1
Windows 11 with latest updates
Search a location.
https://rapideditor.org/edit#background=FOMI_2007_2010&datasets=fbRoads,msBuildings&disable_features=landuse,boundaries,pistes,aerialways,past_future,others&map=16.60/47.30270/17.59411
No response
The text was updated successfully, but these errors were encountered:
Closing as a dupe of #1007
Sorry, something went wrong.
No branches or pull requests
Description
Since days I cannot search within OSM, it gives no results.
I tried Nominatim search site and it works: https://nominatim.openstreetmap.org/ui/search.html
And https://www.openstreetmap.org/#map=13/47.2939/17.5988 also works
But not when I am editing in OSM and I need to find a location.
There is no error message.
Version
2.0.3
What browser are you seeing the problem on? What version are you running?
Firefox 116.0.1
The OS you're using
Windows 11 with latest updates
Steps to reproduce
Search a location.
The browser URL at the time you encountered the bug
https://rapideditor.org/edit#background=FOMI_2007_2010&datasets=fbRoads,msBuildings&disable_features=landuse,boundaries,pistes,aerialways,past_future,others&map=16.60/47.30270/17.59411
The auto-detected useragent string for your browser (leave blank if you're manually filling this form out)
No response
The text was updated successfully, but these errors were encountered: