Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

Prevent users working with long ways #1274

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 2 comments
Closed

Prevent users working with long ways #1274

openstreetmap-trac opened this issue Jul 23, 2021 · 2 comments

Comments

@openstreetmap-trac
Copy link

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).

@openstreetmap-trac
Copy link
Author

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.

http://trac.openstreetmap.org/browser/sites/rails_port/config/application.yml

@openstreetmap-trac
Copy link
Author

Author: iandees
[Added to the original trac issue at 7.36pm, Monday, 9th September 2013]

Cleaning aging tickets.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant