This is because there was no exclude. Not sure how that should be handled.
Bill
The way this should be handled is the original designer needs to fix his airport bgl.
Many different convert programs were released before SP1 was available. Most airport bgls need updating (taxiway signs) if it was designed prior to SP1.
When a airport designer places data in a airport XML they must understand that a deleteall= or an exclusion must exsit based on what is added to the XML.
MS gave us the ability to block out or exclude data so as duplictes will not occur. Since the beginning of FS9, some designers have continued to disregard the way FS9/FSX requires blocking/excluding airport data placed at a higher priority.
I see the same thing happening now with airports being uploaded to variuos web sites. One of the nice features of ADE is that it can very quickly tell us if a Airport is contructed properly or not. The end result is a designer needs to learn how to apply the proper rules to a Airport bgl if they want it to work properly.