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)

You're missing the fact that we do not show that blanket airspace on the map. It's in virtual radar, it's in the flight details window if you plan a route through it, and it will show an in-flight warning if you approach it.

Jo, you state the performance issues resulting from the inclusion of large country-wide pieces of airspace in our calculations are our problem. You are correct, you just don't like how we have currently handled the problem, which is to omit the largest (most problematic) pieces of airspace from our data deliberately to keep a good general experience for the vast majority of our customers. I agree with you that our software would be better if these pieces were included, and I have planned some time in the future to see if there's any way we can mitigate the performance issues.

Do not underestimate the difference it can make including two 1,000 vertex polygons (that's the class C and class E) for Germany in our airspace hit-testing, which runs every time you change your route and every few seconds in flight. Anyone flying in the vicinity of Germany would be subject to this, which is many thousands of customers.

Tim, that's almost the solution I suggested in a previous post. If you now could just add the airspace to the list shown when you do a "what's here" I'd be a happy camper.

Greetings, -- Chris.

Just as an aside to Tim:

You might have already done this, but optimizing your hit testing algorithm might gain you some performance improvements. You do have an advantage about normal hit testing. Namely, you can assume that your point in question moves on a continuous line at a certain maximum speed. So a tiered algorithm -- giving you rough estimates blindingly fast whereas taking a bit longer if you want to know accurately -- might be beneficial. One might imploy a ranked list of airspaces that are most likely to change their status.

-- Chris.