Fair enough, I'd forgotten about the DEM files being manually downloaded. I'm still not convinced it's the best place, especially for files like PlanG3_FSX.sdf, but we can agree to disagree  :). At least now I know, I can exclude them from backups

Thanks

Taken from: http://www.nats-uk.ead-it.com/public/index.php%3Foption=com_content&task=blogcategory&id=99&Itemid=148.html

For aircraft leaving controlled airspace at MONTY (to the SW of the airport)

MONTY1S is for runway 05L departures
MONTY1Z is for runway 05R departures

Save this as a .snip file:

A|EGCC|53.3537443354726|-2.2749499976635|0
U||53.3842498575081|-2.22009658813477|0
I|XOBRO|53.4713890403509|-2.42166683077812|0
V|WAL|53.3919443562627|-3.13444465398788|0
I|MONTY|52.8927778825164|-3.17388877272606|0


I notice that Plan-G is storing the database files that it builds from FSX etc in My Documents. Picking out a couple of the largest files, I've got:

• \Plan-G Files\Data\PlanG3_FSX.sdf at 144 MB
• \Plan-G Files\DEM\b10g at 99 MB

I'm not sure that these kind of generated application data are really supposed to be kept in "My Documents". My understanding of Microsoft's guidelines are that it would probably be more appropriate for these to be stored somewhere like %LOCALAPPDATA%. Having them where they currently are means that whenever anyone backs up everything in My Documents (not an unreasonable thing to do), they'd be including over 240 MB of unimportant data that can be easily regenerated. Looking at other filenames in there, I can see how files such as "UserWpts3.sdf" perhaps should be in My Documents (assuming, judging by the filename, that this is where waypoints I create manually get stored - a user would want those backing up)

I love the airspace altitude filters, but I'm not certain that they're quite working properly...

At Leeds Bradford Airport (EGNM) there is controlled airspace up to 8500 (floors of SFC, 2500 and 3000). If I set the upper airspace altitude filter to 5000 (leaving the lower filter unchecked), all these control areas/zones disappear. I would have expected them to still be displayed since even though they extend above the filter, they still exist in part of the SFC - 5000 range I'm filtering on.

Similarly, if I set the lower airspace filter to 100 (and uncheck the upper filter), all the controlled airspace with a floor of SFC disappears, even though it extends upwards above 100 into the range I'm expecting to see.

Does that make sense?