[openstreetmap/openstreetmap-website] Bandwidth limit has become trivial to hit (Issue #7054)

Minh Nguyễn notifications at github.com
Sun May 3 16:48:47 UTC 2026


1ec5 left a comment (openstreetmap/openstreetmap-website#7054)

If I’m not mistaken, /map includes any relation that has a member within the requested bounding box, but the relation is still incomplete. You aren’t rerequesting highways all across Switzerland just because the E60 runs through there. That’s still a lot of member IDs though.

The most recent time I hit openstreetmap-cgimap’s bandwidth limit was a couple months ago attempting to move a GNIS-imported POI about 30 kilometers in iD, panning by screenfuls pretty rapidly [along a major highway route](https://www.openstreetmap.org/way/961140460) in an area with very dense building coverage. (I used to have an amazing workaround to avoid any panning at all, but it no longer works.) The rate limiting began about 20 kilometers into it. I ended up having to wait a bit between each screenful. It didn’t occur to me that the highway route might’ve been the issue (along with several intercity bus routes that follow the highway route).

It’s a lot easier to hit the limit in OpenHistoricalMap, which uses relations much more heavily. Fantastically dense and complex boundary relation coverage (like in San José, more than a thousand times of what’s in OSM) forced us to increase openstreetmap-cgimap’s limits in OpenHistoricalMap/issues#860. That mitigated the rate limit for now, but it’s still a poor experience for anyone editing on a less powerful computer.

If the (incomplete) relations are driving rate limits in OSM, then I’m picturing a bandwidth optimization in the form of an option on /map that fetches all the map data in the bounding box, including the IDs of parent relations, but not the relations themselves. Then an editor could decide to multifetch the relations by ID in a separate request as necessary. The downside would be additional requests and probably more work on the server side.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/7054#issuecomment-4366668307
You are receiving this because you are subscribed to this thread.

Message ID: <openstreetmap/openstreetmap-website/issues/7054/4366668307 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20260503/395c12b5/attachment.htm>


More information about the rails-dev mailing list