Hi Chris:
You may wish to first consider the MS-FS2Kx/FSX/P3D "Area" sub-folder chain structure for CONUS, and explore whether there is a way (yet) to decompile
P3Dv5 format
APX*.BGL and
OBX*.BGL BGLComp placement BGLs, to see if you might be able to extract 3D object placement info into a data base.
http://www.prepar3d.com/SDKv5/sdk/world/terrain/terrain_overview.html#Base File Information
https://www.fsdeveloper.com/forum/threads/ade-v1-20-co-mingling-obx-and-apx-data.9342/post-61937
[
EDITED]
I do not have P3Dv5.x to test yet, but I would consider it likely that Arno's MCX can already decompile
P3Dv5 format BGLComp XML library object placement code, and thus it is possible this special tool may be able to generate a useful work product for your latest task ...and still others yet to come.
XML placement to SHP converter
https://www.fsdeveloper.com/wiki/index.php?title=ModelConverterX#XML_placement_to_SHP_converter.
I would surmise you may find numerous uses for
*.SHP format object positioning data.
IIRC, you may find that, one need not derive from RefPoints, calculated Geographic vertex coordinates to be used in creating contiguous "micro-exclude" Exclusion Rectangles for BGLComp XML library object placement code such as is done by ADE during import of BGLComp XML library object placement code.
Rather, one may instead be able to place a 'invisible suppression object' (such as the one by John Dutton developed for use with Instant Scenery cited in the info linked to above), at the same identical Geographic vertex coordinates as the object to be excluded and replaced.
MS-FS by default at run time, excludes BGLComp XML library object placed as Autogen if another object in a separate BGL with a higher priority is placed at the identical Geographic coordinates,
unless the Geographically co-incident placement of a 'suppression object' has a pre-pended XML code element for "
NoAutogenSuppression".
http://www.prepar3d.com/SDK/Environment Kit/BGL Compiler SDK/Compiling BGL.html#SceneryObject
Thus, you may merely need to distinguish those incorrectly placed default 3D scenery objects which must be replaced by an invisible suppression object (...to 'exclude' that default 3D object), and those 3D scenery objects which need to placed
de Novo ...in their Geographically
correct positions.
CAVEAT: I recommend that you
always use 13 Decimal place precision with all GIS coordinates for Latitude / Longitude, and min. 2 Decimal place precision with Headings.
[
END_EDIT]
Alternatively, I am not certain as to whether
Little NavMap tools may also generate an intermediate work output file which contains 3D library object placement info:
I'm posting this plea for any help folks can offer in decoding the MSFS format BGLs in order to extract information for use by other programs. This is so that i can make an attempt at getting my freeware utility "MakeRunways" working for MSFS. There have been many requests for this -- primarily...
www.fsdeveloper.com
Extracting Autogen placement of 3D scenery objects would involve work with the Default.XML file.
GaryGB