Tim Dawson (3/29/2016)
We include all airspace whose lower level is below FL195, with the current exception of "blanket" controlled airspace at higher altitudes covering entire countries, which (as I believe may have been mentioned earlier) we assume pilots flying at those altitudes are already aware of.It is a great approach of focussing on the customer if you say to the customer that he should be aware of the incompleteness of your data instead of just providing a complete set of data customers could trust on. FL195 seems like a reasonable boundary to cut the data, but this implies that the data below FL195 is complete, which it obviously isn't.
Tim Dawson (3/29/2016)
To my knowledge we are missing no airspace at lower levels in the entirety of Europe. This is a false statement, which can be easily disproved. For example, have a look on the airspace in the vicinity of the lovely town of Gundelfingen (EDMU). For this area, the airspace information in Skydemon is zero, nada, nothing. Not a single airspace information is given. Basically SD says airspace G goes from GND to UNL. In fact, airspace E from 2500ft AGL to FL100 is missing. And airspace C above FL100 also.
Guys, seriously, this is not acceptable! Just think of the following: Given the hypothetical case that the standard airspace structure is comletely provided in SD. How high is the chance that theres a customer complainig that he doesn't need the standard structure because "he knows it anyway"? How high is the chance that you guys would post a press release saying: "We remove the standard airspaces because the people were annoyed of it".
This whole discussion is ridicolous. Your data is faulty and you deny to change it. It would be nice to see at least an approach to solving this problem. What about discribing the standard airspace structure somewhere in the app?