nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Implement measures to prevent shrinkage to seeds in the event of a problem.

-_Ashley-B-Potter_-

Please implement measures to prevent shrinkage to seeds in the event of an issue. If there is a boundary line concern, why does the "shrink to seeds" process continue? We often encounter problems where the system locks up or times out, necessitating the creation of a new version. If the system can recognize an issue during the "reconstruct from seeds" process, shouldn’t it also do the same for the "shrink to seeds" operation?

Find more posts tagged with

Needs Clarification

Status: Needs Clarification

Comments

AmirBar-Maor

@-_Ashley-B-Potter_-

Could you please be more specific about the type of issue. Is this a data quality issue, server timing out when processing too much data, etc.

If the system 'locks up' this is a bug. Surely you don't want Shrink to Seed to do the same.

-_Ashley-B-Potter_-

@AmirBar-Maor If a parcel is expected to undergo shrinkage, it must possess the capability for reconstruction. Should it lack this capacity for reconstruction, then initial shrinkage should be precluded. The failure to reconstruct indicates an underlying issue; therefore, shrinkage should not occur. This principle applies equally to all paramotors.

AmirBar-Maor

@-_Ashley-B-Potter_-

Thanks for the explanation.

The purpose of "Shrink to Seed" is to be able to preserve the parcel attributes, modify the line boundaries, and then use 'Reconstruct from Seeds' to create it again.

If you manipulate the boundary lines such that they do not close, the parcel cannot be reconstructed (but you can always use undo).

It would help if you could please include some screenshots to make sure we understand your situation correctly.