Rewrite map algorithm

[ChristianHuehn]

Feature request

Description

We have a lot of trouble with our map generation algorithm on the frontend. It hides a couple of buildings and it's performance is mediocre. Therefor we want to rewrite it reduce it's complexity and the bugs on the way.

Acceptance criteria

• Evaluate if threejs or angular-three should be used
• Checkout if d3 nested hierachy is of better use for us
• Rewrite the algorithm

Assumptions & Exclusions

Development notes (optional Task Breakdown)

• [ ]
• [ ]
• [ ]

Open questions

[BridgeAR]

Former approach #3077 (this did not work and it turned out that a new heuristic to implement this better could be used instead. It would check on the current layer how the sizes deviate from each other and redistribute the overall available space to do a new size distribution until the difference falls below ε that is defined as the upper bound threshold for deviations.

The issue is pretty much a duplicate of #3044.

For anyone tackling this, please reach out to @RomanenkoVladimir and me.