I have written some software that works on top of a very popular bgl to xml conversion program. I used the bgl to xml conversion program from another developer to extract each bgl to an xml file (navaids, airports, vor's, ndb's, isecs, etc) Then I wrote some software that extracted each element (vor, ndb, etc) and saved it to its own xml file. You may ask yourself, why spend the time? Well try using the xml contained in those bgl files, tons of comments in the xml, no order to which navaids are in which file etc. With the method I chose each and every navaid is in its own file. So far I have extracted Vor's, Ndb's, and Waypoints (Isecs) and routes. For a total for 40,000 plus navaids. All that is left is extracting the airports. Having this information is important for developers who are building software such as flight planning, radar applications etc. I will be organizing this data for my own uses in a file that contains all navaids for a particular lat and long pair, so for example all navaids in the range lat 44.0 to 44.9999999999 and lon 55.0 to 55.9999999999 would be in a file called 044055.xml so that an easy lookup of a pertinent lat/long will only load that navaids in that area. I will also be putting this information in the form of a dataset as well for ADO.NET uses. If you are interested in this package stay posted because all I have left to do is finish extracting the airports. The bgl to xml tool I used puts some '&' characters in the XML which causes some xml parsers to fail, so about 51 bgl files containing airports fail parsing, so I have to fix those files. I wrote three pieces of software to accomplish this objective. The first was a program to control the bgl to xml conversion application to tell it which bgl file to load and where to save it, and to prevent it from executing to many of the bgl to xml processes at one time. The program also forced the bgl to xml program to execute in the background without popping up a shell window each time it ran i.e. it ran (a new instance) 1500 plus times to extract all the ap*.bgl files for airports, just to give an example. Then I wrote a program to load and parse each xml file generated by the bgl to xml program, to parse out the xml data and save each nav aid to its own file. Last I wrote a program that takes each navaid in its own file and puts together the ones that fall within each whole number lat/long pair. I will be making all the navaids available soon. I expect the final count to be well over 50,000 plus navaids. This will be an awesome package for developers who want a list of navaids in SIMPLE xml, and NOT kml (yes that really is kml, used by goggle earth) http://gsxlive.net/adminforum/index.php?topic=115.0 The navaid collection will be available for download in the next week. And the tools I programmed if anyone is interested, I will make them available. I wrote the tools in managed code and have not obfuscated them, so please respect the intellectual property rights. Also coming in the next couple months a FSX server and client, that is NOT based on direct play.