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: Cobra [Submitted to the original trac issue database at 4.31pm, Saturday, 17th July 2010]
As OSM gets more and more detailed, that "too may items in this area" warning pops up more frequently, even in highest zoomlevels.
I didn't ever experience any problems on my side, neither with firefox nor with chrome/chromium (the latter tested with >6000 items), so it's rather annoying to click "load data" whenever I move the map a bit. It would be nice to have at least an option to switch off this warning or setting a higher threshold than just 100. An automatic alternative could be based on the user-agent submitted by the browser and a "known-good" list of browsers behaving fine.
The text was updated successfully, but these errors were encountered:
Author: Richard [Added to the original trac issue at 11.33pm, Friday, 20th April 2012]
Hey Holger - it doesn't take very long at all. If you can send a github pull request with the problem fixed properly, I'm sure it'll be solved in no time. Thanks for your help! :)
Reporter: Cobra
[Submitted to the original trac issue database at 4.31pm, Saturday, 17th July 2010]
As OSM gets more and more detailed, that "too may items in this area" warning pops up more frequently, even in highest zoomlevels.
I didn't ever experience any problems on my side, neither with firefox nor with chrome/chromium (the latter tested with >6000 items), so it's rather annoying to click "load data" whenever I move the map a bit. It would be nice to have at least an option to switch off this warning or setting a higher threshold than just 100. An automatic alternative could be based on the user-agent submitted by the browser and a "known-good" list of browsers behaving fine.
The text was updated successfully, but these errors were encountered: