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)

Hey Tim,
don't get me wrong: Dynamic removal of airspaces is a great feature of SD. Thats one of the things SD handles much better than a paper map does. Have a look at the north-eastern France area, on the map thats a huge mess.  However, in my eyes the "Whats here" menu should include all airspace data. Also, the virtual radar should show all airspaces, as long as they are within the upper and lower margin.

When I am planning to fly a certain track, I use the "whats here" to see the vertical layers. So I want all layers from GND to a reasonable altitude. In my case thats approx. FL130, but many people fly even higher. After I've checked the vertical layer, I choose my altitude to fly through there.

I can understand that a Class E with 2500 AGL needs a lot of performance to be calculated on the fly so I can understand you don't want to have that in your data. However, class C should absolutely be included. Flying from G into E is usually not a problem, but flying from G/E to C without clerance will cause more problems.

So, lets nail it down to three requirements I would want to see in the next SD release:
1. Add all(!) airspaces that need clereance to fly into (A/B/C/D) up to your altitude of coverage (FL195 i guess?)
2. Disable dynamic removal for the "Whats Here" feature.
3. The virtual radar must show all airspaces within its altitude range. The altitude range can be dynamically adjusted, of course.

In case you're fearing performance issues or an "overinforming" of the user, add switches for this. I would like to hear your opinion on this.