Some feedback after experimenting with Custom Data recently:

1. The name field position of a custom airspace polygon is drawn either inside or outside the associated polygon depending on zoom level. This becomes an issue where the boundaries of two custom airspaces are close, or identical to one another. By comparison, the name field of official airspace supplied by SD doesn't behave like this – the name appears to be always drawn inside the polygon, which is the preferable behaviour. See the pics in the zip link below for examples of both points - and also note that there's no collision/overlap detection between the drawn names of custom and official datasets in pic 10.

2. It could be useful if user defined and official airspace was more clearly differentiated – currently they're both drawn in the same style and colour.

I attempted to attach some images to this post, however the upload times out (both linking or embedding on Chrome or Firefox; file size is quite minimal also) so here's a link to a zip containing some screen shots - please see the image names in the zip for details:

Custom Airspace vs Official Airspace data name field position.zip

Hamish