We will need to perform a review to make sure there are no others which need to be added, which we will do after the new Germany chart has been published and we are sure there are no downsides to our new inclusion of that airspace.

Hi Tim,
I've just downloaded the update of the German map data. Airspace C is now visible in the VR view.
Thanks for changing this, it's working really well. I also get the warning when coming back from the alps area flying towards Munich in FL120.
The "Whats here"-Menu does not show the airpsace class C, I assume this will change with the next update of the software.

Are there any other Class A-D airspaces still missing (e.g. in other countries)?

It seems we agree, then. I must have got hung up on the part where you wrote, "We will not be changing the What's Here menu". Sorry to belabour the point more than necessary.

-- Chris.

No, my reasoning is different. I argue not to show it in "what's here" if, and only if, the user opted not to show it. You, as I understand, don't show it because you have made an executive decision as provider of the software.

In my scheme, if the user decides to show airspaces above FL100, it would show up even if it still isn't depicted on the map. In your logic, as I understand it, it still wouldn't show up. So if the user asked SD to show all airspaces up to and including FL100, you don't comply and rather present incomplete information. This can result in very undesirable consequences when in flight.

-- Chris.

Your statements are contradictory. The whole point of dynamic airspace is to filter out airspaces, so if you've set SkyDemon to not show airspace over 4000' (unless you actually plan a route there) for example you have told SkyDemon to filter it out, and it is quite correct not to show it in the What's Here menu since it's not shown on the map.

It's ok to list only features in the"whar's here" menu which the user didn't filter out himself. Therefore there shouldn't be that many more items to list.

Again, I consider it quite problematic if I can't get complete information about airspaces present at a particular point.

-- Chris.

There is already a switch for this. It's called the dynamic airspace feature, or "hide features above", and hopefully you already use it. If you regularly fly at FL100 then you will have changed this option appropriately, and therefore airspace you have said you're interested in will be displayed.

We will not be changing the What's Here menu to display stuff that isn't actually displayed on the map. It would often result in the list of stuff being many, many items longer than it currently is (we couldn't just stop at airspace; we'd need to include other aeronautical stuff the user had turned off like IFR waypoints, glider airfields, etc).

I've managed to make some small optimisations in the way we hit-test large pieces of airspace and will be publishing an updated Germany chart containing the class C in the next few days, so you'll be able to see it then. An update to the client software such that the airspace appears in the What's Here menu (assuming you have airspace that high turned on) will need to wait until the next release, obviously.

That's interresting information. As I used "What's here" in order to have a look at what Airspace actually was there (between ground & upper level of SD). Seems I had it wrong (might be usefull to make that clearer in the documentation as well as it seems that I missed it). Might a solution not to have different behaviour between planning & in-flight ?
I think that for planning it would be usefull to know all airspaces that is at a certain point.
During flight I understand that it might only be usefull to have info on the airspace in the vincinity of where you are (I mean in hight).
This would solve the performance issue mentionned before.

Tim,
the issue Chris is complaining about is exactly what I refered to as item 2 a few posts earlier:
2. Disable dynamic removal for the "Whats Here" feature.
Right now, there is no easy way to get the vertical airspace information for any given point. A user always must plan a route along that specific point and then vary the altitude until he knows whats going on.

When I plan a route and - for example - I have the choise to pass a certain restricted area in the north or in the south, I select a point in the north and check the vertical airspace layers. Then I do the same for the south and decide which way I fly and at which altitude.

Dynamic airspace removal on the map is a great feature, I said that already. However, the "Whats here" is basically a right-click menu. What will happen if dynamic removal will be deactivated? Probably 2-4 extra items will be listed. Nothing a user can't handle.

Again, just make a switch for it if you don't want to alter it for everybody: Disable dynamic removal for the whats here menu
Thats basically all we ask for.

Jo