search

hotosm / osm-tasking-manager2

Designed and built for Humanitarian OpenStreetMap Team collaborative emergency/disaster mapping, the OSM Tasking Manager 2.0 divides an area into individual squares that can be rapidly mapped by thousands of volunteers.
http://tasks.hotosm.org
Other
425 stars 156 forks source link

What's the optimum limit for number of polygons for each project? #751

Closed maning closed 8 years ago

maning commented 8 years ago

I'm dividing a large poly of census blocks into groups for different TM projects. What's the ballpark limit for number of polys for each project? I noticed that for large TM projects with arbitrary polys, loading the project page become slower.

pgiraud commented 8 years ago

You may have more experience than I do. However, in the V1 of the tasking manager I experienced performances issues with more than 2000 squares. But it's completely different since we were not using arbitrary polygons at that time.

OSMUS may have some experience as well. There's using arbitrary polygons for projects in their instance. For example http://tasks.openstreetmap.us/project/7.

It shows that not only the number of elements can be a problem. The complexity of each may also be an issue. In the above example, the ".json" file is 4.3MB. Once loaded it works pretty well though (at least on a recent computer).

pgiraud commented 8 years ago

@maning did this help? Can we close this issue since it's more a question that a real issue?

maning commented 8 years ago

Yes thank you. I reduced my polys to less than 1K. Closing.