This is my list of a hand written XML
After the compiler header is always the Excludes. This tells FSX to exclude anything first then place the scenery objects both Generic and Library Object Guid/model.mdl's next. There is a pecking order inside the XML that must be followed which you have already seen some of that with taxiways, Blastpads, ILS data, etc.
In that way you do not have to use a alpha/number file name (seperate exclude bgl's) in order for FSX to exclude something then allow a reinsert of something else.
Many scenery designers make multiple exclude files with just one exclude rectangle per bgl. What a waste of space and time. Even if I made a seperate exclude bgl, all the excludes can be in that one file rather then having a single exclude per bgl.
There is one FSX exclude issue that may be by design or a mistake.
If you exclude a Library Object you cannot place a Library Object Guid back into that exclude box. It will not show up!!! You can put anything else into the rectangle box but not a Library Object Guid.
There are many complaints on other web sites that Users are saying the Utility shipped with FSX SDK does not work correctly. In most cases this is what the designer is trying to do and it is not the Utility but what was excluded first.
If you look at the SAV xml I sent you I excluded at the top the Main Terminal Building which is a Library Object. At first I made the exclude rectangle to large when I moved the Terminal NORTH and WEST. When I added the animated Library Object JETWAY for Gate 9 it would not show up because its reference LAT/ LON was inside the exclude rectangle.
I went back and made the exclude rectangle 1/4 inch in size (see the decimal values of the exclude) so I had more room to play with for the LAT/LON of the JETWAY and then it showed up.
I also excluded only the reference Taxiway sign which unlocked all the signs from the Bias. I then copied all signs back into the XML which are now treated as stand alone scenery items and allows me to edit, change Lat/lon, labels, etc.
I then excluded all the antennas and associated checkerboard shacks that are part of the visuals for the ILS runways. I moved them to their proper LAT/LON and reset the imageComplexity= to a low slider value. For some reason FS has these visuals at a very high setting which has no effect on FPS.
The list then looks like this
<FSData compiler header
<ExclusionRectangle (many as needed)
<SceneryObject (both <Generic and <LibraryObject)
< Modeldata (if needed for type scenery design)
<Effects
<Triggers (for weather and fuel)
<Windsocks
<Attached Objects (such as beacons if visual Tower is placed above the Airport Record)
<Time Zone
<ExtrusionBridge
<VOR (plus DME and Visual model)
<NDB (non_TERMINAL because it nest outside the Airport Record +DME and Visual Model)
<Markers
and now the list for
<Airport Header (and all required data as listed in above post)
and then after the closing element which is <Airport/>
<Boundary (and all associated types, Arc's Lines, circles, etc.)
<Waypoint ( these are non_TERMINAL and used primary for Routes but also in Approach Records listed above)
<Route (both previous and next)
<Geopol (type and associated data)
and then the closing statement of
<FSData />
