This is one reason I want the max checkout to be reduced to
100 features. You really shouldn't be doing more than say 10
islands at a time if you want to get it right.
for the Akl Isl the first time I tried the other day I checked
out the entire northern end of the island around to where you'd
done, but that was 130 islands or so to merge and it proved quickly
to be more than I could chew. I then did 1 box down south a bit
which had about 14 islands and it was a much more managable chunk
to work on.
At the same time though, consider that the native_poly layer for
the AKl Isl had 83 features, but that consisted of over 33,000
nodes and a large geographic area, while cliff_edge for the Akl
Isl had 1100 features but only 8,000 or so nodes. In any event
having to split the cliff_edge into 11-12 chunks and merging instead
of just doing them all at once would have been a big and unceccesary
PITA & waste of time. For things like trees, building points, and
descriptive text, with 500,000 features for the mainland but fewer
merging worries, blanket limiting to 100 features would take years
to finish. I've got no better solution to propose, just thinking
about how the problem is different in different layer contexts.
how would the 100 fea max work? if you tried a work slice block
with more than 100 it would refuse and tell you to zoom in more
then try again?
for the Akl Isl the first time I tried the other day I checked out the entire northern end of the island around to where you'd done, but that was 130 islands or so to merge and it proved quickly to be more than I could chew. I then did 1 box down south a bit which had about 14 islands and it was a much more managable chunk to work on.
At the same time though, consider that the native_poly layer for the AKl Isl had 83 features, but that consisted of over 33,000 nodes and a large geographic area, while cliff_edge for the Akl Isl had 1100 features but only 8,000 or so nodes. In any event having to split the cliff_edge into 11-12 chunks and merging instead of just doing them all at once would have been a big and unceccesary PITA & waste of time. For things like trees, building points, and descriptive text, with 500,000 features for the mainland but fewer merging worries, blanket limiting to 100 features would take years to finish. I've got no better solution to propose, just thinking about how the problem is different in different layer contexts.
how would the 100 fea max work? if you tried a work slice block with more than 100 it would refuse and tell you to zoom in more then try again?