Hi, Erik Johansson wrote:
It seems the excess detection process doesn't coop well with my mapping. So what do you suggest? Move slower or stop mapping?
Load the data on a smaller zoom level so you're making one bigger request instead of tons of small requests?
That's not that amusing when the large requests happen to include a high density area. Is it really that bad to make 2 requests/second in a rural area?
I was just explaining what I would do faced with this situation. If you were using JOSM you could control quite finely what area to download, thus skipping any high-density areas along the way.
The rate limiting on the map call is a good thing to have overall (without it, many people would be slowed down by a few idiots doing large-scale map scraping becuse they cannot be bothered to download a planet file). Of course Wyo's use is legitimate and *should* not be affected by rate limiting but it is probably not so easy to make the distinction.
Apart from taking save requests into account, as Wyo suggested, it is also conceivable to switch of rate limiting altogether for logged-in users (who, if they misbehave, can be indentified and contacted). I'm sure that patches improving the situation would be welcome. The relevant source code is at http://git.openstreetmap.org/cgimap.git, more specifically http://git.openstreetmap.org/cgimap.git/blob/HEAD:/src/rate_limiter.cpp.
Anything taking into account a potential "save" operation would have to be put into the main (rails) API though, as uploads are processed there.
Bye Frederik -- Frederik Ramm ## eMail [email protected] ## N49°00'09" E008°23'33" _______________________________________________ dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/dev
