Airports with updated ICAO codes

Thanks Molleh for the feedback and this detailled investigation. Interesting to see that airport list is not only build from the BGL that contains airport records. I will be interested if you could privately send me [hsors(at)hotmail(dot)com] the original 2 files ADEX_FTX_NCA_O68_Mariposa_Yosemite.BGL and ADE_FTX_NCA_O68_elevation_adjustment.BGL file so that I analyze them more in detail.
I will also be interested to know, from your experience, what are the consequences of this duplicate situation on the simulation while flying around the airport (apart there is 2 entries in the list)
By the way I hope OrbX will publish some updated files in the future including current ICAO codes
Know that when I built the initial US updates, about 15-20 such changes were included, so that's still a very few (although there's some others outside the US). Since then, I only had to change one or two (previous 6 months)

Hello Herve,  

I have a similar problem related to O17/KGOO involving an ORBX NorCal regional scenery in P3DV4.  The explanation provided by member molleh seemed be a solution, but I don’t trust my limited experience to download the editing tools he described and attempt a fix and screwing things up.  Is there a less complex method using one or two of your tools to make the necessary file corrections.  

As as things stand now having two airport entities at the same geolocation result in their stacked appearance  and unsuitable for landing/takeoffs.

BobSuslin

Hello again Herve, sounds simple enough that even I can do it. I have downloaded AIE and will make edits that you have clearly explained.


I interpret the effect of your instructions as reverting the updated ICAO code to its original "stock" code ID is to avoid the conflict with ORBX.   However, Mollehs' fix was to actually change the names in both ORBX files so they comport with the updated ICAO nav data.  Thus,  the nav database and ORBX scenery are in sync for as long as  either the ICAO remains the same or ORBX has a scenery update. . Your comment?

Bob

I understand your hesitation to go further .

Thanks much for your help

Bob

Here is the method I used based largely on Molleh's post at the top of the thread. This method is similar, however doesn't require ProKey. I posted this in the Orbx forum.


This is going to carry the weight of what would be a tutorial. It's just not going to have screenshots and cleanliness.

First off, again, I did not touch the Scenery\0102\scenery\APX15180.bgl file. What did touch that file was the navdata update program, be it in my case Aero.Sors, or in the other case FS Aerodata. Those programs modify the core files to bring the ICAO's, runway numbers, taxiways, etc. current.

If I were to use the program Little Nav Map for example, and typed in O17 for Nevada County, it would show me that the files it is referencing for O17 were ADEX_FTX_NCA_O17.bgl and ADE_FTX_NCA_O17_elevation_adjustment.BGL in their respective folders. Yet if I searched KGOO, it would show me the file it's referencing is APX15180.bgl. This is post navdata update mind you. So, the simulator thinks that there is both a O17 and a KGOO causing a mismatch. The way to eliminate this mismatch is to update the ICAO's in the aforementioned Orbx files.

Now updating ADEX_FTX_NCA_O17.bgl is easy. I use a program called Airport Inspector and Editor by Herve Sors www.aero.sors.fr/navaids.html. In that program, you load the .bgl and open the airport/rwy editor and change the ICAO; in this case from O17 to KGOO. That file is now updated, and is done. Airport Inspector and Editor creates a backup for you prior to the save.

The ADE_FTX_NCA_O17_elevation_adjustment.BGL gets a little more tricky as Airport Inspector and Editor will not open it. ADE will let you open it, but will not allow you to modify it. So, we go to .xml. For that, I use a program called Bgl2Xml by ScruffyDuck www.scruffyduck.org/bgl2xml/4584282773. In that program, I load the file in, and create an output. You can choose any name you want, or use the default, but you will have to rename the file at some point. This generates an .xml of the .bgl file.
I then open the newly created .xml file with a .xml editor. I use the freeware Microsoft XML Notepad. When open, under airport, there is a section for ident. Go in there and change the ident from O17 to KGOO. Save and close.

Open, not import, the modified .xml file now in ADE. Compile the file as you would any other scenery project. Locate your newly modified .bgl and rename as necessary. Place the new elevation adjustment .bgl in world/scenery folder and overwrite the existing. Obviously you would have backed up your originals before hand.

If you used Little Nav Map, then reload the scenery directory, and you should now find zero instances of O17, yet will see all three files referenced when you search KGOO. This is purely optional. More importantly in the sim, you should now see no instances of O17 and only see KGOO.

Load up, and enjoy your newly corrected scenery.

Of note, this can obviously cause problems the other direction if someone has never updated their core data. However, if someone is looking for help with this issue, it is likely they have. It's possible that the reason Orbx has elected not to update their own files is because they will then differ from the core files in the unmodified data set. I will say, it is a lot easier to fix a core file than it is to correct the Orbx files though, but I digress.

Nick

Perhaps in the future, Herve will add support for changing ICAO in this file using tool AIE
Then it will be even easier

I also sent you a personal message with a link to the samples (_elevation_adjustment.BGL)