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: frederik[at]remote.org [Submitted to the original trac issue database at 6.18pm, Saturday, 12th May 2007]
Current API chokes on extremely long ways. We have abotu 350 ways with more than 500 segments, 3 of them with more than 5000 segments.
As a quick remedy, I (Frederik) will split all these ways into pieces of max. 500 segments.
For the long term, we should either find a way to handle such ways gracefully OR disallow ways of more than 500 ways being created (just return an error message if someone tries).
The text was updated successfully, but these errors were encountered:
Author: frederik[at]remote.org [Added to the original trac issue at 10.05am, Monday, 14th May 2007]
Problem has been mediated by splitting very long ways. Some cleanup still being done. Among the ~250 ways affected there are also 19 "natural=water" ways, presumably lakes; splitting may be reverted for those pending discussion on mailing list. Priority of this ticket downgraded to minor as the problem is only quick-fixed, not really solved.
Reporter: frederik[at]remote.org
[Submitted to the original trac issue database at 6.18pm, Saturday, 12th May 2007]
Current API chokes on extremely long ways. We have abotu 350 ways with more than 500 segments, 3 of them with more than 5000 segments.
As a quick remedy, I (Frederik) will split all these ways into pieces of max. 500 segments.
For the long term, we should either find a way to handle such ways gracefully OR disallow ways of more than 500 ways being created (just return an error message if someone tries).
The text was updated successfully, but these errors were encountered: