I am just trying out the Free Trial of SD.

Here in southern Germany I am unable to see the standard Airspace C starting at FL100.
I can see C starting at FL130 in the alpine area, but not the standard C in the flatlands.

Same goes with airspace E. Visible when the lower limit is off-standard (like 1000ft)
but not when standard (2500 ft).

What am I doing wrong? Thanks a lot!

(and yes, I have well planned a route high enough - currently FL150)

Hi Tim,
I don't see a problem of getting technical in this discussion. Both ckurz7000 and I want to help you to improve the user experience. Also, I have some background on programming and mathematical problems like efficient path finding and neighbor-detection in 3D-data.

To increase performance during flight, what about breaking down the airspaces into the FIRs?Germany Class C will be cut it into 3 pieces (EDMM, EDGG, EDWW). For Class E, it will be even more (e.g. Munich is divided in to South and North). Maybe this helps to improve performance.

Also, especially for Class C, im my eyes a perfectly precise drawing of the border is not necessary. It is probably possible to recude the amount of data points of the big airspaces to 25-50% without losing accuracy.

However, during planning, all airspaces should be listed in the context menu. At least, this should be possible to be activated by a switch.