![]() |
May we collect and use your data?
Learn more about the Third Party Services we use and our Privacy Statement.May we collect and use your data to tailor your experience?
Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.
Thank you for the suggestion and thanks to those who voted.
We will engage in consultations with a wider array of stakeholders to gauge their interest and gather additional perspectives on the proposed feature.
Should we observe a substantial level of enthusiasm and demand, we will be inclined to advance the status of this suggestion to "Under Consideration." This stage will involve a more detailed analysis, including a feasibility study, resource allocation assessment, and preliminary planning to understand how this feature could be seamlessly integrated into the software.
Alongside this, would be good if the bug associated with "Shaft additional storage: simplification (m2)" when restoring pruned links could be fixed.
E.g. lets say there is a node with two US links. Initially, the 'simplification storage' is 0m2. When you prune US link A, the storage goes to 10m2. Then when you prune US link B the storage goes up by another 10 to 20m2. However, when you restore the pruned links, there is a bug in the software. Restoring pruned links does not 'subtract' the storage value. Instead, it resets the value to what it was immediately before that particular link was pruned. So e.g. if you restore US link B first, the storage goes back to 10m2. Then if you restore US link A the storage geos back to 0m - so this all works fine. But if you restore US link A first, the storage value becomes 0m2 (since this is what it was before link A was pruned). Then if you resotore link B second, the storage value becomes 10m2 (since this is what it was before link B was pruned). So we end up with a non-zero storage value despite there no longer being any pruned links.