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: Richard [Submitted to the original trac issue database at 2.44pm, Friday, 17th October 2008]
Long ways are generally a really bad thing - if there's a lot of data (like, 17,000 nodes) the server/connection/Flash Player will probably time out somewhere along the line, resulting in inconsistent data. That's to say nothing of the UI unresponsiveness and the issues that could potentially cause.
Potlatch should definitely not allow users to create them - there's an argument to say it shouldn't even load them, too (amf_controller could refuse to send back anything over 1,000 nodes, for example).
The text was updated successfully, but these errors were encountered:
Author: osm[at]gravitystorm.co.uk [Added to the original trac issue at 5.12pm, Tuesday, 21st April 2009]
Worth bearing in mind that there is now a limit on the length of ways, defined in the application.yml. Currently set to 2000 nodes. So it would be good to align any restrictions in Potlatch with that number.
Reporter: Richard
[Submitted to the original trac issue database at 2.44pm, Friday, 17th October 2008]
Long ways are generally a really bad thing - if there's a lot of data (like, 17,000 nodes) the server/connection/Flash Player will probably time out somewhere along the line, resulting in inconsistent data. That's to say nothing of the UI unresponsiveness and the issues that could potentially cause.
Potlatch should definitely not allow users to create them - there's an argument to say it shouldn't even load them, too (amf_controller could refuse to send back anything over 1,000 nodes, for example).
The text was updated successfully, but these errors were encountered: