Opened 16 years ago
Last modified 9 years ago
#4783 closed enhancement
Update Data fails if one of the bounds has grown beyond 50k items — at Version 1
| Reported by: | mk408 | Owned by: | team |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | Core | Version: | latest |
| Keywords: | splitting 50k update | Cc: | xeen |
Description (last modified by )
If a previous downloaded area (<bounds>) has, on the OSM server, grown to contain more than 50000 items, trying to update will fail due to the server returning an error that the requested download is too large.
A partial fix would be to continue with further requests, if there are any, and communicating the error to the user.
A complete fix would involve automatically splitting the area and retrying. Currently, I perform this manually by editing the .osm file.
Note:
See TracTickets
for help on using tickets.
What is the actual use case for this? I believe it’s very rare that an area grows beyond 50k items if it’s been downloaded recently. Of course, the error should be reported properly, but auto-splitting seems like a way to circumvent the server’s limits -- I doubt the 50k items are really a problem, it’s more likely it was implemented to prevent users from downloading way-too-large areas.